Automatically Issue Credentials from External Forms
Someone fills out your enrollment form. Seconds later, their credential is issued. No manual entry. No context-switching.
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
External enrollment forms require manual re-entry into credential systems, creating delays and duplicate data entry errors.
- Credentials issued instantly on form submission
- No manual data re-entry
- Learner data flows directly from enrollment to credentials
- Complete audit trail from form to credential
Setup
Build it in a few focused steps.
- 1Connect your Accredible account to Notis.
- 2Create an automation: 'When someone submits my enrollment form, create a credential with their details.'
- 3Select 'Incoming webhook' as your trigger and Notis will provide a unique webhook URL.
- 4Copy that URL into your form service (Typeform, Jotform, Zapier, etc) as the submission destination.
- 5Test by submitting a form and verifying the credential appears in Accredible within 30 seconds.
Questions about this workflow
What form services are supported?
Any form that can send webhooks works with Notis: Typeform, Jotform, Google Forms (via Zapier), custom forms, etc.
Can I validate the form data before issuing?
Yes. Notis can check that required fields (name, email) are present before creating the credential.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Accredible certificates. A trigger fires from one place; an action lands in another.
Notion 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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Collection
Tool to create a new collection. use when you need a curated set of groups.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Create Evidence Item
Tool to create a new evidence item for a credential. use after confirming credential id.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Group
Tool to create a new group. use after gathering all group details.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
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.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Delete Group
Tool to delete a group. use after confirming no credentials remain and when you need to permanently remove the group.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
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.
Notion 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.