Webhooks: Connect Zapier, Make, and n8n

Open a form's Responses tab and click Webhooks. Add a name and a destination URL — in Zapier, use a "Catch Hook" trigger URL; in Make, a "Custom webhook" module URL; in n8n, a Webhook node's production URL. You can add as many webhooks per form as your plan allows.

Every webhook call is a JSON POST containing the form's title and slug, the event type (response.created, response.resent, or test), and the response's answers in two shapes: answers keyed by field id, and answersByLabel keyed by the question's visible label — use whichever is easier to map in your automation tool.

Click Test next to a webhook to send a sample payload with placeholder answers for every field — useful for mapping fields in Zapier/Make/n8n before any real responses come in. To resend a past response (for example after fixing a broken Zap), use the send icon next to that row in the responses table and choose which webhook to resend it to.

The Starter plan includes 1 webhook per workspace (across Zapier, Make, or n8n); Pro includes unlimited webhooks. See Billing, Plans, and Upgrading.

You don't have to open the Webhooks panel by hand — ask the AI assistant on the Responses tab (or the editor chat) to "add a webhook pointing to this URL" or "send a test payload to my Zapier webhook," and it creates, edits, tests, or deletes webhooks directly. See The Orbiform AI Assistant.

If you're building specifically in Zapier, Orbiform also has a native app with its own triggers (New Response, New Form), a Create Form action, and search steps (Find Form, Get Form Stats) — no webhook URL to copy around, just sign in once. See Connect Orbiform to Zapier.

If you want an AI assistant to read and manage your forms directly — rather than reacting to a one-way event — connect Orbiform to Claude as an MCP connector instead. See Connect Orbiform to Claude with MCP.