Outly AI + Zapier
Send Outly workspace events — hot leads, replies, meetings, campaign activity — straight into a Zap. This uses Zapier's own "Webhooks by Zapier" Catch Hook trigger, delivered through the same signed, retried, logged infrastructure as Outly Webhooks. No Zapier password, API key, or OAuth grant is ever needed — the Catch Hook URL is the only credential.
1. Start a new Zap in Zapier
In Zapier, create a new Zap and search for the "Webhooks by Zapier" app as the trigger.
2. Choose the Catch Hook trigger event
Pick Catch Hook (not "Catch Raw Hook" — Outly sends standard parsed JSON, so the regular Catch Hook trigger is correct).
3. Copy the generated webhook URL
Zapier generates a unique URL like https://hooks.zapier.com/hooks/catch/123456/abcd1234/. Copy it — this is the only thing Outly needs from Zapier.
4. Add the connection in Outly
In Outly, go to Settings → Integrations → Zapier → Add Connection. Give it a name, paste the Catch Hook URL, and choose which events should trigger this Zap.
5. Send a test event
Use Send Test Event on the connection's detail page. Outly reports whether the HTTP delivery to Zapier succeeded — it can only confirm the event reached Zapier's Catch Hook, not that the rest of your Zap finished running (Zapier itself doesn't expose that back to the sender).
6. Pull in sample data and finish your Zap
Back in Zapier, click "Test trigger" to pull in the sample payload Outly just sent. From there, map fields into your next Zap step — 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 Zap 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 Zapier's field mapper always sees the same shape.
Example Zaps
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 → Append 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 Zapier" but the Zap didn't run: check the Zap is turned on in Zapier, and that the trigger step still points at the same Catch Hook URL as the connection in Outly.
- Connection marked "Unhealthy": the Catch Hook URL has failed 20 deliveries in a row — this usually means the Zap (and its URL) was deleted or regenerated in Zapier. Create a fresh Zap, copy its new Catch Hook URL, and update the connection.
- Not receiving events you expect: check the connection's subscribed events list, and confirm it's enabled, not disabled.