Zapier Integration
Connect form submissions to 6,000+ apps using Zapier webhooks. No code required.
What is Zapier
Zapier is an automation platform that connects web apps together. When a form is submitted on FormBlade, Zapier can automatically send that data to Google Sheets, Slack, a CRM, an email service, or any of the 6,000+ apps it supports.
What you need
- A FormBlade account on the Pro plan or higher (webhooks are a Pro feature)
- A Zapier account (the free tier works for basic automations)
Setup steps
Go to zapier.com/app/zaps and click Create Zap (or + Create in the top-left). This starts a new automation workflow.
In the trigger step, search for Webhooks by Zapier and select it. Choose Catch Hook as the trigger event, then click Continue.
Zapier generates a unique webhook URL that looks like:
https://hooks.zapier.com/hooks/catch/123456/abcdef/
Copy this URL. You will paste it into FormBlade in the next step.
Log in to your FormBlade dashboard. Go to Webhooks in the sidebar, select the form you want to connect, and click + Add webhook. Choose Zapier as the type, paste the webhook URL, and click Create webhook.
In FormBlade, click Test next to the webhook you just created. This sends a sample payload to Zapier. Then go back to Zapier and click Test trigger. You should see the sample submission data appear. Click Continue.
Choose what should happen when a form is submitted. Search for the app you want to connect (Google Sheets, Gmail, Slack, HubSpot, etc.), configure the action using data from the trigger, and click Publish to activate your Zap.
Example use cases
- Add submissions to a Google Sheet — append a new row for every form submission, with each field mapped to a column
- Create a Trello card — turn each submission into a card on a board, with the message as the description
- Send a custom email via Gmail — compose and send a personalized email to the submitter or your team
- Add contacts to a CRM — create or update contacts in HubSpot, Salesforce, Pipedrive, or other CRMs
- Post to a private Slack channel — send a richly formatted message with submission details to a specific channel
Payload format
FormBlade sends a JSON payload containing the full submission data. The key fields are:
| Field | Description |
|---|---|
event | Event type (submission.created) |
form_id | Unique form identifier |
form_name | Form name as shown in the dashboard |
submission_id | Unique submission identifier |
data | Key-value pairs of all submitted form fields |
files | File metadata (if any files were uploaded) |
ip_address | Submitter IP address (if not anonymized) |
country | 2-letter country code |
device | Device type, browser, and OS |
In Zapier, each field from data is available as a separate variable you can map to action fields. For the full payload specification, see the Webhooks documentation.
Troubleshooting
Zap not triggering
- Check the webhook is active — in the FormBlade dashboard, verify the webhook shows a green "Active" status
- Confirm your plan — webhooks require the Pro plan or higher. Free plan forms cannot send webhooks
- Check spam filtering — submissions flagged as spam do not trigger webhooks. See Spam Protection for details
- Verify the Zap is on — make sure the Zap is published and turned on in Zapier (not paused or in draft mode)
Missing fields in Zapier
- Field names in Zapier come directly from the HTML
nameattributes in your form. Make sure every input has anameattribute - If you add new fields to your form after creating the Zap, you may need to re-test the trigger in Zapier so it picks up the new field names
Related
- Webhooks — full payload reference, HMAC signatures, retries
- Integrations — native integrations (Google Sheets, Slack, Discord, and more)
- Make (Integromat) — connect FormBlade to Make
- n8n — connect FormBlade to n8n