Integrations: GHL, webhooks, Slack & Discord

Settings → Integrations connects SetterStack to the rest of your stack.

01GoHighLevel (booking attribution)

SetterStack's booking links automatically carry attribution — which Instagram handle and which exact conversation sent the lead. A simple GHL workflow writes those onto the contact when they book, and GHL's booking webhook back to SetterStack marks the conversation Booked ✓ and notes the CRM record.

Result: you can trace every booked call to the DM conversation — and the flow — that produced it.

02Outbound webhooks (SetterStack → your tools)

``json { "event": "workflow.lead", "lead": { "name": "…", "handle": "their_ig_handle", "platform": "instagram", "phone": "+15551234567", "email": "lead@email.com", "consent": true, "qualification": { "goal": "…", "budget": "…", "timeline": "…" }, "tags": ["interested", "contact_consent"], "threadId": "…" } } ``

• The "Call a webhook" flow step POSTs the lead's info to any URL mid-flow — push qualified leads into your CRM, a Google Sheet via middleware, or Zapier/Make.
• The payload includes the lead's name, handle, phone, email, consent, all captured qualification fields, and tags — everything your GHL/Zapier automation needs to create or update the contact (upsert by phone/email) without the lead ever filling out a form:
• The DM is the form. Turn on AI Config → Qualify → Collect contact info and your AI will naturally ask a warm lead for the best phone or email for your team to follow up — once, after value, and only with their OK (never pushy, never on the first message). Whatever it captures is validated and rides this webhook straight into your CRM. If a lead volunteers their number or email on their own, it's captured either way.

03Inbound webhooks (your tools → SetterStack)

• Add the "Another tool sends a lead here" trigger to a flow and it gets a private webhook URL (with a secret token you can regenerate anytime).
• POST a lead to that URL — by conversation reference or just {"username": "their_handle"} — and the flow starts for them.
• Typical use: a GHL workflow enrolls a lead into a SetterStack DM sequence when they hit a pipeline stage.

Note: inbound triggers start flows, and normal messaging-window rules still apply to what those flows can send.

04Slack & Discord

Paste a channel webhook URL and hit Test. Then:

• Notify the team flow steps ping the channel.
• Needs-a-human alerts (escalations, human-hotline keywords) reach your team in real time, de-duplicated so a chatty lead doesn't flood the channel.
• System alerts (e.g. delivery failures) can ride the same channel — so silence really means "all good."

05Weekly results email

Every Monday morning, the workspace owner gets a short scorecard for the week: new leads, how many qualified, and calls booked — pulled straight from your real numbers. Quiet weeks with zero activity don't send anything.

06CSV export

Settings → Accounts exports your leads as CSV anytime — handle, stage, tags, qualification data. Your data is yours.