n8n
Trigger an n8n workflow whenever a Clipform form is completed.
n8n is open-source workflow automation you can run on n8n Cloud or self-host. Start a workflow every time someone completes your Clipform - the same way on Cloud and self-hosted.
Use the Clipform node (recommended)
The Clipform Trigger community node gives you a one-click "On form response" trigger, authenticated with a Clipform API key.
1. Enable verified community nodes
The Clipform Trigger is a verified n8n node (look for the shield icon), so you add it straight from the Nodes panel - no npm install. Just make sure verified community nodes are enabled on your instance first (needs n8n 1.94 or later):
- n8n Cloud: turn them on in the Admin Panel.
- Self-hosted: set the verified-nodes environment variable (see n8n's verified community nodes guide).
2. Add your API key
- In Clipform, open Settings → API keys and create a key - it is shown once, so copy it then (full guide: API keys).
- In n8n, add a new Clipform API credential and paste the key. The credential's Test button calls
GET /v1/meto confirm the key works.
3. Add the trigger
In the Nodes panel, search Clipform, add the Clipform Trigger node, and
activate your workflow - it subscribes to
your workspace's form completions (and unsubscribes when you deactivate it). It
fires for every completed form in the workspace; to react to one form, add an
n8n IF or Filter node on form_id or form_tags.
Or use a generic webhook
If you would rather not use a community node, n8n's built-in Webhook node works too:
- Add a Webhook node (method POST) as the trigger and copy its Production URL.
- In Clipform, open Settings → Webhooks (under the Developers section - webhooks are workspace-level, not per-form) and paste the URL. It saves automatically - there's no Save button.
- In n8n click Listen for test event, then in Clipform click Send test so n8n learns your fields.
What gets sent
Each completion sends a form.completed event. The full shape is documented in the
Webhook Payload Format - it includes the form ID, response
ID, session details, and every answer keyed by node.