While our platform offers many native integrations, you can connect to over 5,000 apps by routing your form data through Zapier.

By using our REST Connector as the trigger, you gain professional-level control over your data flow, including custom JSON payloads, conditional “Run Rules,” and even multi-step REST sequences before the data reaches your Zapier workflow.

Why use the REST Connector?

Using the REST Connector to talk to Zapier offers several advantages for technical teams:

• Filtered Execution: Use “Run Conditions” to only trigger a Zap if specific criteria are met (e.g., {{riskRating}} = 'High').
• Custom Payloads: Instead of sending every form field, use the Body setting to map only the specific data points Zapier needs.
• Header Authentication: Send custom Auth headers or organization IDs directly to your endpoint.

Common Use Cases

High-Priority Lead Routing (Conditional Logic)

Scenario: You have a “Contact Us” form, but you only want to alert your Sales team in Slack via Zapier if the “Company Size” is over 500 employees.

• The Setup: Configure a REST Connector with a Run Condition.
• The Logic: {{companySize}} > 500.
• The Result: Zapier only receives (and charges you for) high-value leads, keeping your Slack noise-free.

Formatting Data for CRM Injection

Scenario: Your CRM requires dates in a specific “Display” format rather than the standard ISO 8601 (UTC).

• The Setup: Enable the Replace Placeholders with Display Text checkbox in the Connector settings.
• The Result: Zapier receives “23-Oct-2026” instead of “2026-10-23T15:05:07Z,” saving you from adding a “Formatter by Zapier” step and consuming extra Zap tasks.

Dynamic Multi-Department Routing

Scenario: You want to send form data to different Zapier Webhooks based on the region selected in the form.

• The Setup: Use a Dynamic Request URL.
• The Logic: Set your Destination URL to https://hooks.zapier.com/hooks/catch/123456/{{regionID}}/.
• The Result: A single form can route data to different departmental Zaps dynamically based on user input.

How to Set It Up: Step-by-Step

Generate your Zapier Webhook URL

1. Log in to Zapier and create a new Zap.
2. Select Webhooks by Zapier as the Trigger event.
3. Choose Catch Hook and click Continue.
4. Copy the Webhook URL provided by Zapier.

Configure the REST Connector

1. In our platform, go to App Workshop > Forms and open the Connectors tab for your form.
2. Add a REST Connector.
3. Set the HTTP Action to POST.
4. Paste your Zapier URL into the Destination URL field.

Map Your Data (The “Body”)

To ensure Zapier understands your data perfectly, we recommend defining a custom JSON body:

1. Click the Body icon in the top-right of the connector settings.
2. Enter your JSON structure using field placeholders:

{
  "customer_name": "{{fullname}}",
  "email": "{{useremail}}",
  "priority": "{{urgencyLevel}}"
}

3. Click Save.

Test the Connection

1. Submit a test entry through your form.
2. Go back to Zapier and click Test trigger.
3. You should see your form data appear in Zapier instantly!

Pro-Tips for Zapier Integrations

The 10-Second Rule: Our platform expects a 200 OK response from Zapier within 10 seconds. Zapier’s “Catch Hook” responds almost instantly, making it highly reliable for this integration.

• Avoid Double Quote Issues: If your form fields contain quotes (e.g., a “Comments” field), our connector automatically escapes them in JSON. If you are building complex arrays, use the SUBSTITUTE() formula as mentioned in our core REST documentation to ensure the payload remains valid.
• Security: To ensure only our platform can trigger your Zap, keep the “Disable default query string parameters” option unchecked. This will send your Organization’s Private Token to Zapier, which you can then verify using a “Filter by Zapier” step.