Make.com and webhooks

How CRISP uses Make.com for generation workflows, callbacks, and idempotency.

CRISP uses Make.com to orchestrate generation workflows. The app triggers Make scenarios via webhooks, and Make calls back into the app when work is complete.

Who this page is for

Operators building or updating Make scenarios
Developers/support troubleshooting generation and callback issues

How the flow works

CRISP triggers generation by sending a payload to Make.
Make generates content and writes results to Airtable.
Make calls back to CRISP endpoints to confirm completion and update progress.

Key constraints

Webhook payloads must remain stable for scenarios to keep working.
Callbacks must be idempotent to avoid double-counting usage.
Environment variables must be set correctly (webhook URLs, secrets).

Common failure scenarios

Wrong webhook URL or missing secret header
Airtable schema drift (field/table renamed)
Make scenario disabled or failing mid-run

Getting started: Getting started
Airtable integration: Airtable integration
Content system: Content system

Cloudinary and images

Image hosting requirements for CRISP, including Instagram publishing constraints.

Fast answers to common CRISP Content Engine questions and failure scenarios.