How to connect a Webflow form to Zapier or Make?
Webflow stores form submissions in its own dashboard, but most workflows need that data somewhere else — a Google Sheet, a CRM, an email marketing tool, or a Slack channel. Zapier and Make (formerly I
Webflow stores form submissions in its own dashboard, but most workflows need that data somewhere else — a Google Sheet, a CRM, an email marketing tool, or a Slack channel. Zapier and Make (formerly Integromat) are the two most popular automation platforms for bridging that gap.
Connecting to Zapier
Step 1: Create a Zap
- Log in to Zapier and click Create a Zap
- For the trigger app, search for Webflow and select it
- Choose the event New Form Submission
- Connect your Webflow account if you haven't already — Zapier will ask you to authorize access
Step 2: Configure the trigger
- Select your Webflow site and the specific site plan
- Select the form name you want to watch — Webflow lists all forms on your site
- Click Test trigger to pull in a sample submission
Zapier needs at least one existing submission to test with. If your form is new, submit a test entry first.
Step 3: Set up the action
- Choose your destination app — Google Sheets, Mailchimp, HubSpot, Slack, or any of Zapier's 6,000+ integrations
- Map the form fields from Webflow to the corresponding fields in your destination
- Test the action to confirm data flows correctly
- Publish the Zap
New form submissions will now trigger your automation in real time.
Connecting to Make
Step 1: Create a scenario
- Log in to Make and click Create a new scenario
- Click the + module and search for Webflow
- Select Watch Form Submissions as the trigger
Step 2: Configure the connection
- Add your Webflow API token — generate one from Project Settings > Integrations > API in Webflow
- Select your site and the specific form
- Set the limit (how many submissions to process per run) and scheduling interval
Step 3: Add action modules
- Click the + after the Webflow module to add your destination — Google Sheets, Airtable, Slack, email, etc.
- Map fields using the data pulled from the Webflow trigger
- Run a test to verify
- Toggle the scenario to ON
Make scenarios run on a schedule (every 5 minutes, 15 minutes, hourly, etc.) rather than instantly like Zapier.
Zapier vs Make for Webflow forms
| Zapier | Make | |
|---|---|---|
| Trigger speed | Near-instant | Polled (scheduled intervals) |
| Free tier | 100 tasks/month | 1,000 operations/month |
| Learning curve | Easier | More complex but more powerful |
| Multi-step workflows | Paid plans only | Available on free tier |
| Data transformation | Limited | Advanced built-in tools |
Choose Zapier for simplicity and instant triggers. Choose Make if you need complex data transformations or want more value on the free tier.
Tips for reliable integrations
- Always test with real data before going live. Submit a test form entry and verify it appears in your destination.
- Handle required fields — if your destination requires fields that Webflow doesn't always collect (like a last name), add fallback values in the mapping.
- Monitor for errors — both platforms have logs. Check them periodically, especially in the first few days after setup.
- Rate limits — Webflow's API has rate limits. If you receive a high volume of submissions, Make's batch processing may handle it better than Zapier's per-event model.