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

Create a custom webhook trigger in Make and copy its HTTPS URL.
Add a webhook to the Fillo form under Settings > Webhooks.
Store the one-time Fillo signing secret in a protected Make connection or secret store.
Verify the hex HMAC-SHA256 over the exact raw request bytes before using any answer.
Deduplicate on X-Fillo-Delivery-Id in durable storage.
Return a 2xx response within ten seconds, then run slower actions after acknowledgement.
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.