Webhooks¶
Webhooks let external systems start Scroll workflows automatically. A CRM, intake form, or internal app POSTs to a unique URL and Scroll kicks off a workflow run with the supplied data.
Manage them under the Webhooks view.
How it works¶
- Create a webhook for a specific workflow. Scroll generates a unique URL containing a secret token.
- An external system POSTs JSON to that URL with the workflow's input fields.
- Scroll starts the run with those inputs, applying PII redaction and the normal engine flow, including the approval gate.
The token in the URL is the credential, keep it secret. Each webhook tracks how many times it's been used.
Use cases¶
- A CRM pushes a new client → Scroll prepares their onboarding workflow.
- An internal system flags an upcoming expiry → Scroll prepares the renewal.
- A web form submission → Scroll starts a document-analysis workflow.
Works with any domain or document type, webhooks aren't tied to a specific workflow category.
Webhooks vs other inputs¶
| Mechanism | Who triggers | Best for |
|---|---|---|
| Webhooks | External systems (machine-to-machine) | CRMs/apps that push data to Scroll. |
| CRM connect | You, pulling from Zoho | Searching and pre-filling from your CRM. |
| Intake links | The client | Collecting details directly from clients. |