Webhooks StarterTeam

Webhooks make every submission a trigger: score a lead in n8n before it's even stored, reject spam with a rule you control, draft the reply email, open the Jira ticket, ping the on-call channel. Snapi calls your endpoint (or n8n, Make, Zapier — anything with a URL) at two moments — before a record is saved, where you can modify or veto it, and after, where the downstream automation begins. Configure both per form.

Webhook types

Each form supports two webhook timing modes:

• Pre-event — fires before the record is saved. Your endpoint can return modified data, or reject the submission by responding with { "abort": true }.
• Post-event — fires after the record is saved (fire-and-forget). The response is ignored; used for notifications, sync, and automation triggers.

Configuring a webhook

1. Optionally, open Settings → External APIs and add your n8n instance or any generic HTTP base URL as a reusable connection.
2. Open the form in the builder and go to its Webhooks tab.
3. For the Pre-Webhook and/or Post-Webhook, choose Manual URL or External API.
4. Enter the full webhook URL (manual mode), or select a connection and enter the endpoint path to append to its base URL (external mode).
5. Save.

Webhook URLs must use HTTPS and cannot point at private or local addresses.

Payload format

Snapi sends a POST request (or the method you configure) with Content-Type: application/json. When a new record is submitted, the pre-event webhook receives the form and the submitted data:

{
  "entity": {
    "id": "ent_abc123xyz",
    "name": "Contact",
    "slug": "contact"
  },
  "data": {
    "name": "Alice Johnson",
    "email": "alice@example.com",
    "message": "Interested in a demo"
  }
}

Post-event webhooks include an event field, which is one of:

• record.created — a record was created by a signed-in user or via the API; the payload includes the full saved record.
• record.updated — a record was updated; the payload includes the full record plus a changes object with old and new values.
• record.submitted — a public form submission; the payload is { "event": "record.submitted", "recordId": "...", "data": { ... } }.

Deleting a record does not fire a webhook.

Pre-event webhooks

For pre-event webhooks, your endpoint can modify the record before it is saved. Return a JSON object with a data key containing the modified fields:

// Enrich or validate — return modified data
{
  "data": {
    "name": "Alice Johnson",
    "email": "alice@example.com",
    "score": 82
  }
}

To reject the record, respond with a JSON body containing { "abort": true }. Snapi rejects the submission with a 409 Conflict error and includes your full response body in the error's details field.

When an existing record is updated, the pre-event payload is { "event": "record.updating", "record": { "id": "...", "data": { ... } }, "newData": { ... } } — respond the same way to modify or abort the update.

Securing your webhook endpoint

Snapi does not currently sign webhook payloads. To make sure requests hitting your endpoint really come from Snapi, include a secret token in the webhook URL and verify it on your server:

// Configure the webhook URL as:
//   https://your-server.com/webhook/snapi?token=YOUR_SECRET

// Express example — reject requests without the shared secret
app.post('/webhook/snapi', (req, res) => {
  if (req.query.token !== process.env.SNAPI_SHARED_SECRET) {
    return res.status(401).end();
  }
  // ...handle the payload
});

Retry policy

Webhooks are not retried:

• Post-event webhooks are fire-and-forget — if your endpoint is down or returns an error, the delivery is skipped and the failure is logged on the server. The saved record is unaffected.
• Pre-event webhooks that time out or error are treated as a pass — the record is saved unchanged.

If you need guaranteed processing, point the webhook at a highly available receiver (such as an n8n instance) and queue the work there.

n8n integration

Snapi has first-class support for n8n. In Settings → External APIs, add an n8n connection with your instance's base URL. When configuring a webhook on a form, select this connection and enter your workflow's webhook path — Snapi combines it with the base URL for you.

Use the Webhook trigger node in n8n with POST method. The body will contain the full Snapi payload.