Turn a verified credential request into an Accredible award
Give approved credential requests a direct path to Accredible. Send the details Notis needs to the webhook and describe the award rule in plain language.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Bulk Create Credentials (V2)
Tool to bulk create credentials. use when batching up to 30 credentials in one call; supports multi-status (207) responses.
Why this helps
Approved award requests often wait in inboxes or forms while someone manually re-enters recipient and credential details.
- Reduce re-entry from approved requests
- Handle batches of up to 30 credentials in one call when appropriate
- Keep the run outcome visible
Setup
Build it in a few focused steps.
- 1Connect Accredible certificates once in the Notis portal.
- 2Create an automation named for verified credential requests.
- 3In one instruction, describe how to validate the request and which credential and recipient details to use.
- 4Pick a Notis webhook trigger and choose where run reports go.
- 5Test with one real request example and review the run report.
Questions about this workflow
Can one run issue multiple credentials?
The bulk create action supports batching up to 30 credentials in one call and can return multi-status responses.
What if the request lacks a required detail?
Tell Notis how to handle incomplete requests in your instruction, and ensure the webhook includes any details not available elsewhere.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Accredible certificates. A trigger fires from one place; an action lands in another.
Jira triggers
Accredible certificates actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Bulk Create Credentials (V2)
Tool to bulk create credentials. use when batching up to 30 credentials in one call; supports multi-status (207) responses.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Clone Group
Tool to clone an existing group. use after confirming the source group exists and you need a copy with optional overrides.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Create Collection
Tool to create a new collection. use when you need a curated set of groups.
New Project
Triggered when a new project is added in Jira
Create Evidence Item
Tool to create a new evidence item for a credential. use after confirming credential id.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Create Group
Tool to create a new group. use after gathering all group details.
Delete Credential
Tool to delete a credential. use after confirming you want to permanently remove an existing credential. executes delete on /credentials/{credential id} endpoint and returns status code.
Delete Group
Tool to delete a group. use after confirming no credentials remain and when you need to permanently remove the group.
Delete Reference
Tool to delete a specific reference by id. use after confirming both credential id and reference id. example: "delete reference 1234 from credential 'abc123'."
Connect any two apps with Notis in the middle.
Jira and Accredible certificates, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Accredible certificates.