Outly AI + Make
Send Outly workspace events — hot leads, replies, meetings, campaign activity — straight into a scenario. This uses Make's own "Custom webhook" trigger module, delivered through the same signed, retried, logged infrastructure as Outly Webhooks. No Make password, API key, or OAuth grant is ever needed — the webhook URL is the only credential.
1. Start a new scenario in Make
In Make, create a new scenario and add a module — search for the "Webhooks" app.
2. Choose the Custom webhook trigger
Pick Custom webhook as the trigger, then click Add to create a new webhook (or select an existing one).
3. Copy the generated webhook URL
Make generates a unique URL on one of its regional hosts, like https://hook.eu1.make.com/abc123xyz or https://hook.us1.make.com/abc123xyz. Copy it — this is the only thing Outly needs from Make.
4. Add the connection in Outly
In Outly, go to Settings → Integrations → Make → Add Connection. Give it a name, paste the webhook URL, and choose which events should trigger this scenario.
5. Send a test event
Use Send Test Event on the connection's detail page. Outly reports whether the HTTP delivery to Make succeeded — it can only confirm the event reached Make's webhook, not that the rest of your scenario finished running.
6. Determine the data structure and finish your scenario
Back in Make, click Redetermine data structure (or run the module once) to pull in the sample payload Outly just sent. From there, map fields into your next module — the flat fields below (lead_name, ai_fit_score, etc.) are the easiest to map directly.
Available fields
Every event includes event_id (the top-level id field, use it as an idempotency key if your scenario runs an irreversible action), type, created_at, and workspace_id, plus a nested object AND flat top-level convenience fields for whatever the event carries — lead_id, lead_name, company_name, job_title, ai_fit_score, reply_classification, meeting_id, meeting_start, meeting_end, crm_provider, opportunity_value. A field the underlying event doesn't have a value for is sent as null, never omitted or fabricated, so Make's data structure stays consistent across events.
Example scenarios
Alert the team on a hot lead
lead.hot → Post to a Slack channel or send an SMS with lead_name, company_name, and ai_fit_score.
Add every new lead to a spreadsheet
lead.created → Add a row to Google Sheets with lead_name and lead_id.
Notify sales when a meeting is booked
meeting.booked → Create a Google Calendar event or send an email using meeting_start and meeting_end.
Log positive replies to a CRM outside Outly
reply.positive → Create or update a record in Airtable / a spreadsheet keyed by lead_id.
Track campaign completions
campaign.completed → Post a summary to a project-management tool like Trello or Asana.
Troubleshooting
- "Delivered to Make" but the scenario didn't run: check the scenario is turned on (active) in Make, and that its Custom webhook module still points at the same URL as the connection in Outly.
- Connection marked "Unhealthy": the webhook URL has failed 20 deliveries in a row — this usually means the webhook was deleted or regenerated in Make. Add a fresh Custom webhook module, copy its new URL, and update the connection.
- Not receiving events you expect: check the connection's subscribed events list, and confirm it's enabled, not disabled.