---
title: "Make"
description: "Start a Make scenario from Fillo through a signed webhook or the supported Zapier alternative."
group: "Deliver & operate"
order: 7
type: "integration"
parent: "integrations"
keywords:
  - "Make"
  - "scenario"
  - "webhook"
  - "automation"
updated: "2026-07-14"
---

Fillo doesn't ship a native Make app yet. A Make scenario can start from a Fillo webhook as long as the workflow verifies the signature safely — or you can use the supported Zapier app instead.

## Webhook path

1. Create a custom webhook trigger in Make and copy its HTTPS URL.
2. Add a webhook to the Fillo form under **Settings > Webhooks**.
3. Store the one-time Fillo signing secret in a protected Make connection or secret store.
4. Verify the hex HMAC-SHA256 over the exact raw request bytes before using any answer.
5. Deduplicate on `X-Fillo-Delivery-Id` in durable storage.
6. Return a 2xx response within ten seconds, then run slower actions after acknowledgement.
7. Submit a test and inspect both the scenario and Fillo delivery state.

Some no-code webhook modules parse JSON before later steps can access the original bytes. If your Make setup can't verify the raw body, receive the webhook in a small server endpoint you control, verify it there, then call the Make scenario with your own credential.

## Payload mapping

| Fillo value | Make use |
| --- | --- |
| `event` | Branch created, updated, or abandoned-draft flows |
| `response_id` | Upsert and deduplicate business records |
| `answers` | Stable raw values keyed by field ID |
| `formatted` | Human-readable option labels and summaries |
| `respondent.verified` | Distinguish server-verified identity from a claim |
| `files` | Protected file metadata and references |

## Limits and delivery

Signed Fillo webhooks are available on every plan. Make applies its own operation, scenario, queue, retention, and data-transfer limits. Fillo reports whether Make's webhook endpoint acknowledged the event, not whether every later module completed.

## Troubleshooting FAQ

### Why does verification fail?

Hash the exact raw bytes before JSON parsing. Re-stringifying an object changes the bytes, and that changes the signature.

### Why did the scenario run more than once?

Fillo retries non-2xx and timed-out requests. Commit the delivery ID before acknowledging and make later actions idempotent.

### Why is a held response missing?

Submission trust holds it back from all webhooks until an owner releases it.

## Related

- [Webhooks](/docs/webhooks): Use the exact headers, payload, and retry contract.
- [Webhook signature verification failed](/docs/troubleshooting/webhook-signature-failed): Fix raw-body and secret mismatches.
- [Zapier](/docs/integrations/zapier): Use the first-party Fillo workflow app instead.