Zapier and Make

Zapier and Make both give you a URL that starts a Zap or scenario when something is sent to it. Add that URL as a webhook in CueDM and every event you pick starts it. Webhooks are on every plan, so you don't need to write code or have an API key.

1. Start a Zap with a catch hook

   In Zapier, create a Zap. For the trigger, choose Webhooks by Zapier, then Catch Hook, and copy the URL it gives you. It starts with https://hooks.zapier.com/hooks/catch/.

2. Add the URL in CueDM

   In Settings → Integrations, choose Add webhook, paste the URL, name it (for example “Zapier → Google Sheets”) and tick the events the Zap is for. You can skip the signing secret: Zapier doesn't check it.

3. Send Zapier a sample

   Choose Send test in CueDM, then Test trigger in Zapier. The test only contains a message. To map real fields, trigger a real event first, for example by commenting your keyword from another account. The fields for each event are in the event reference.

4. Add your action

   Map fields such as data.contact.email or data.user.username into the app you're sending to, then publish the Zap.

1. Start a scenario with a custom webhook

   In Make, create a scenario and add Webhooks → Custom webhook. Choose Add, name it and copy the address. It looks like https://hook.eu2.make.com/….

2. Add the URL in CueDM

   Add it in Settings → Integrations with the events you want, as above.

3. Let Make learn the fields

   With the webhook module waiting for data, trigger a real event in CueDM. Make reads the structure from the first request, and the fields become available to the modules after it.

A few common setups:

• Emails to your list. contact.email_captured → Mailchimp, Kit, Klaviyo or your CRM. Map data.contact.email and tag it with data.contact.automationId to know which post the email came from.
• A log of every DM. dm.sent → Google Sheets, one row per DM with occurredAt, data.automation.name, data.user.username and data.text.
• An alert when a DM fails. dm.failed → Slack, with data.user.username and data.error, so someone can reply by hand.
• Bio page signups. bio.subscribed → your email tool, only when data.subscriber.marketingConsent is true. Add bio.unsubscribed to the same webhook to remove people who leave.

• Nothing arrives. Check the webhook is on and subscribed to the event, then open Deliveries in Settings. A 410 or 404 usually means the Zap was turned off or the catch hook was deleted.
• The webhook switched itself off. After repeated failures CueDM turns a webhook off. Turn the Zap or scenario back on, then turn the webhook back on in Settings. More on failures.
• A field is missing in Zapier. Zapier only knows the fields from the sample it received. Trigger a real event of that type, then choose Find new records in the trigger.

If you're building an app for other CueDM customers, such as an integration-platform app or a CRM connector, don't ask people to paste URLs. Ask for an API key, and subscribe and unsubscribe with POST and DELETE /api/v1/hooks. That's the REST hooks pattern Zapier and Make support natively. Use the sample endpoint to show fields before the first event fires.