How to connect SourceLoop to Zapier and Make

Zapier and Make connect SourceLoop to the thousands of tools it has no native integration with. This guide covers both directions: sending SourceLoop events out to a Zap or scenario, and sending leads from those tools into SourceLoop with their journey attached.

What you can build

Use case	Direction
Add every lead to a Google Sheet with its channel and campaign	Out
Create contacts in a CRM SourceLoop doesn’t connect to, such as Close or Freshsales	Out
Enrich a lead with a data provider before it reaches your CRM	Out
Add new paying customers to a Notion or Airtable database	Out
Send leads from a tool SourceLoop doesn’t cover into SourceLoop	In
Score a lead with an AI step, then send it into SourceLoop	In

For a Slack or email message on each new lead, you don’t need Zapier. Use Slack and email alerts instead.

Before you start

• A SourceLoop workspace where you have an Admin or Editor role
• A Zapier or Make account

Direction 1: SourceLoop to Zapier or Make

Step 1: Get a catch URL

In Zapier:

1. Click Create Zap.
2. For the trigger, choose Webhooks by Zapier, then Catch Hook, and continue.
3. Copy the webhook URL Zapier gives you.

In Make:

1. Click Create a new scenario.
2. Add the Webhooks app and choose Custom webhook.
3. Add a webhook, name it, and copy the URL Make generates.

Step 2: Create an outgoing webhook in SourceLoop

1. In SourceLoop, open Activation, then Outgoing webhooks, and click New webhook.
2. Name it, for example “New leads to Zapier”.
3. Under When, pick what should trigger it, such as Conversion recorded, Lead marked good, Deal won, or Payment received.
4. Under Only if, add conditions to send only the events you need.
5. Paste the Zapier or Make URL under Endpoint.
6. Click Send test, then Create webhook.

Step 3: Catch the test in Zapier or Make

• Zapier: click Test trigger. Zapier shows the payload from the test send.
• Make: click Run once before sending the test, and Make captures the payload structure.

The fields you will map most are under data: contact_name, contact_email, contact_phone, company, conversion, value, channel, source, campaign, landing_page, and first_channel. See Outgoing webhooks for the full payload.

Step 4: Add your actions

From here it is ordinary Zapier or Make work. Two common examples:

• Google Sheets: add a “Create Spreadsheet Row” action and map one column per field, such as contact email, channel, campaign, and value.
• A CRM: add a “Create or update contact” action using the email as the match key, and map channel and campaign into custom fields.

Direction 2: Zapier or Make to SourceLoop

Step 1: Create an incoming webhook in SourceLoop

1. Open Setup, then Incoming Webhooks, and click Add webhook.
2. Give it a Name, such as “Leads from Zapier”, and an Event name, such as zapier_lead. The event name is how these leads appear in reports and how you can exclude them elsewhere.
3. Click Create webhook. Copy the URL and the Token shown with it.

See Incoming webhooks for the full reference.

Step 2: Add a POST step at the end of your workflow

In Zapier, add Webhooks by Zapier, then POST:

1. URL: your SourceLoop webhook URL
2. Payload Type: JSON
3. Data: at least an email or phone, for example email, name, phone, and company
4. Headers: add Sourceloop-Token with the token from Step 1

In Make, add HTTP, then Make a request:

1. URL: your SourceLoop webhook URL
2. Method: POST
3. Headers: Sourceloop-Token with your token
4. Body type: Raw, Content type: JSON, with at least an email or phone in the body

If the tool that started the workflow passes along the visitor’s sl_aid value, include it too. That lets SourceLoop attach the lead to the visitor’s full journey on your site.

Step 3: Check it arrived

Run the workflow, then open Contacts in SourceLoop. The lead appears within seconds. If it doesn’t, open Setup -> Incoming Webhooks and check Recent activity: every request is listed with whether it was accepted, and why if it wasn’t.

Pitfalls

• Loops. A workflow that receives a SourceLoop lead and sends it back into SourceLoop fires the outgoing webhook again. Give the returning leads their own event name and exclude it in the outgoing webhook’s conditions.
• Task usage. Filtering inside Zapier still uses a task for every event. Filter in SourceLoop’s Only if step instead.
• Missing journeys. Leads sent in without an sl_aid are still saved, but SourceLoop can only tie them to a journey if the same email or phone has been seen on your site before.

What’s next

• The full payload and signature: Outgoing webhooks
• Sending leads in from any tool: Incoming webhooks
• Native CRM sync instead of a Zap: HubSpot, Salesforce, or Pipedrive