Skip to main content
All Collections⚡ Zapier / Make.com Integrations
⚡ Integrations with Zapier + Make.com
⚡ Integrations with Zapier + Make.com
Yann Dine avatar
Written by Yann Dine
Updated yesterday

Let's cover how you can integrate Prosp with all your favourite tools using Zapier or Make.com.

First of all, if you're a developer looking for integrations, you can refer to:

  1. And the webhooks section in settings: https://prosp.ai/settings

If you aren't a developer, don't worry - I've got you covered too... 😊

There's two ways you can integrate with Prosp:

  1. Pushing data into Prosp

  2. Pushing data out of Prosp

You can do both with Zapier or Make.com...

Here are all 4 sections covered:

Pushing data into Prosp

This is when you want to:

  • Add a contact to a list / campaign / both from another source or platform (most common)

  • Send a message / voice note to a LinkedIn profile dynamically

  • Remove a lead from a campaign / workspace (useful if you are contacting someone on another platform and want to stop contacting them via Prosp if they reply elsewhere)

1) Pushing data into Prosp with Zapier

To add a contact to a workflow in Prosp, you would set up a module in Zapier after whichever trigger you decide. You should then add a webhook module:

Select POST for the action event

Then, configure the POST webhook like this (images below):

Payload Type: Json

For the Data, you need to map the following fields:

api_key: YOUR_API_KEY_FOUND_IN_PROSP

linkedin_url: the url of the lead you want to add, can be mapped from a previous field

list_id: from Prosp, find this having selected the relevant list in Prosp and extracting ID from url:

campaign_id: from Prosp, find this by selecting the relevant campaign in Prosp and extracting ID from url:

Then you're ready to go :)

2) Pushing data into Prosp with Make

To add a contact to a workflow in Prosp, you would set up an HTTP request module in Make.com after whichever trigger you decide. You should then add a webhook module:

Select "Make a request"

Then, configure the make a request module like this (images below):

Method: POST

Payload Type: Json

In the headers:

Name: Content-Type

Value: application/json

Body type: raw

Content type: JSON (application/json)

Request content:

{
"api_key": "YOUR_API_KEY",
"linkedin_url": "https://www.linkedin.com/in/andrew-c-509b7a71/",
"list_id": "3b362c9c-648f-4831-8698-2acb50d9b254",
"campaign_id": "cac69673-892f-4eec-8b51-42516cc03d04",
"data": [CUSTOM DATA HERE IF YOU WANT]
}

For the Data, you request content, you can find the vlaues here:

api_key: YOUR_API_KEY_FOUND_IN_PROSP

linkedin_url: the url of the lead you want to add, can be mapped from a previous field

list_id: from Prosp, find this having selected the relevant list in Prosp and extracting ID from url:

campaign_id: from Prosp, find this by selecting the relevant campaign in Prosp and extracting ID from url:

Pushing data out of Prosp

This is when you want to:

  • Add/update a contact in your CRM when they reply

  • Add them to an email sending tool during / after your Prosp flow

  • Notifying yourself or team members of activity by Slack / email

To do this, we use the webhooks in Prosp. All we need to do, is setup a webhook to be triggered by the relevant action in Prosp, and then setup a webhook received module in Zapier / Make.com to receive the data and send elsewhere.

1) Pushing data OUT of Prosp with Zapier

The first thing you need to do is setup your webhook in Prosp. You can do this in:

settings > webhooks > Create a webhook

then, you need to select an event to trigger the webhook, you can choose from:

  • LinkedIn Message Sent

  • LinkedIn Voice Sent

  • LinkedIn Message Replied

  • LinkedIn Connection Sent

  • LinkedIn Connection Accepted

  • LinkedIn Comment Replied

  • LinkedIn InMail Message Sent

  • LinkedIn Comment on Last Post

  • LinkedIn Like on Last Post

  • LinkedIn Profile Visit

  • Tag Added to Lead

With your event selected, you then need a callback URL. We are going to get this from Zapier.

Head to your Zap, and select a webhook as your trigger, then select Catch Hook as the trigger event

Press continue, and then continue again

Copy the webhook URL and paste it into the callback URL in Prosp

The order now is IMPORTANT:

  1. Click Test Webhook in Prosp

  2. Go back to Zapier and click Test Webhook

You will then see request content from the webhook in Zapier:

Then, you're good to go! You can build out the rest of your zap using the data from Prosp

This will now be triggered on the designated action from the webhook you selected as it happens in Prosp (please allow for a small delay)

2) Pushing data OUT of Prosp with Make.com

The first thing you need to do is setup your webhook in Prosp. You can do this in:

settings > webhooks > Create a webhook

then, you need to select an event to trigger the webhook, you can choose from:

  • LinkedIn Message Sent

  • LinkedIn Voice Sent

  • LinkedIn Message Replied

  • LinkedIn Connection Sent

  • LinkedIn Connection Accepted

  • LinkedIn Comment Replied

  • LinkedIn InMail Message Sent

  • LinkedIn Comment on Last Post

  • LinkedIn Like on Last Post

  • LinkedIn Profile Visit

  • Tag Added to Lead

With your event selected, you then need a callback URL. We are going to get this from Make.

Head to your scenario, and select a webhook as your trigger, then select Custom webhook as the trigger event

Then follow the instructions to create a webhook:

Then, copy the webhook url to your clipboard:

When copied, head back to the webhook you created in Prosp and paste the url into the Callback URL:

The order now is IMPORTANT:

  1. Go back to Make.com

  2. Right click the webhook module

  3. Click "Run this module only"

you will see it spinning like this:

4. Go back to Prosp and click "Test Webhook"

5. Now go back to Make.com and you will see the data has arrived:

Now you're ready to go! You can use the data from Prosp to complete your scenario:

This will now be triggered on the designated action from the webhook you selected as it happens in Prosp (please allow for a small delay)

Did this answer your question?