Put Make scenarios to work around your calls.
Send phone-ready leads to a queue, then route saved outcomes to your other tools.
Receiving a lead does not start a call. Calling policy still applies.
- Lead event in Make
- Map a phone and stable source ID
- Lead added to a Redialler queue
What you need.
Scenario blueprint and webhook
- A Make account with permission to create a private scenario.
- A Redialler workspace API key and the target queue ID.
- A source that supplies a real phone number, a stable lead ID, and a separate event ID.
Set up Make.
Open Make setup in Redialler Settings and download the intake blueprint and JSON structure sample.
Import the blueprint into a private Make scenario. Create its Custom Webhook and the JSON data structure from the sample.
Set your Redialler origin, workspace key, and queue ID. Map phone, name,
external_id, andsource_event_idfrom the source.Check every intake result. Keep blocked leads in a source repair view. Configure bounded retries for network errors, HTTP 429, and HTTP 5xx.
For saved outcomes, create a separate Make Custom Webhook. Save it as a generic outbound connection in Redialler and map the event to your destination.
Confirm provider access and delivery in your account before rollout.
Data and permissions.
- The workspace key authorizes queue intake. Keep it in the private scenario's credentials.
- The intake blueprint sends mapped lead fields. Saved outcome events carry the outcome, contact name, company, phone number, duration, callback time, and call, queue, and source IDs.
- Saved outcome events exclude transcripts, recordings, and notes. Treat the Make webhook URL as a secret.
Current limits.
- Confirm blueprint import and scenario execution in your Make account before rollout.
- The blueprint's webhook response returns Redialler's status and body to the caller.
- The scenario stop threshold is not an HTTP retry policy. Configure retry handling separately.
- Receiving a lead does not start a call. Calling policy still applies.
Provider documentation
Questions about Make.
Does Make need a native Redialler app?
This setup uses a blueprint, HTTP intake, and webhooks. It does not require a published Make marketplace app.
How do I prevent duplicate leads?
Use a stable external_id for the source lead and a separate event or revision ID for Idempotency-Key. Exact request replays are retained for 72 hours. Check accepted, duplicate, and blocked results.
Can Make receive call outcomes?
Yes. An admin can create a generic outbound connection to a Make Custom Webhook. Use a verifying relay when the workflow must verify Redialler's raw-body signature.
Set up Make for your workspace.
Sign in to open this tool in Settings. An organisation admin connects it for your workspace.