Connect Zapier, Make or n8n
Start a Zap, a Make scenario or an n8n workflow when a document is sent, signed or completed: add the service's webhook URL in Settings, under Integrations. Needs Pro.
On this page
Sealsimple works with Zapier, Make and n8n through a webhook. The service gives you a URL, you add it in Sealsimple, and every document event you picked starts your automation. For example: add a row to a spreadsheet when a contract is completed, or post a message when someone signs. You need Pro, and you must be an owner or admin of the workspace.
Add the URL in Sealsimple
- Open Settings & branding in the account menu and go to Integrations.
- Press Add webhook and paste the URL as the Endpoint URL.
- Pick the Events you need, for example only Completed: everyone signed, and press Add webhook.
Zapier
- Create a Zap with the trigger Webhooks by Zapier and the event Catch Hook. Copy the webhook URL that Zapier shows.
- Add it in Sealsimple as described above.
- Press Send test event in Sealsimple, then test the trigger in Zapier. Zapier now knows the fields.
Make
- Start a scenario with the Webhooks app and its Custom webhook trigger. Add a webhook and copy its address.
- Add it in Sealsimple as described above.
- Press Send test event, so Make can work out the data structure.
n8n
- Add a Webhook node with the HTTP method
POST. - Add its production URL in Sealsimple. The test URL only works while n8n is listening for a test event.
- Activate the workflow.
What your automation gets
Each message has the event, such as document.completed, a document with its title, status and a url to it in Sealsimple, and for events about one person a recipient with name, email and role. Send document events to your system with webhooks lists all events and fields.
The signed PDF itself isn't part of the message. Your automation can store the details and the link, or fetch the PDF with the REST API (Pro).
Nothing arrives?
Open the webhook's Delivery log in Sealsimple: it shows every message and the service's answer. Check that your Zap, scenario or workflow is switched on, and that the URL in Sealsimple is the one the service shows now. If you made a new URL on the service's side, change it in Sealsimple with the pencil icon.