Resources · Make integration

Pipl.ai Make integrationAutomate Pipl.ai with Make.

Can your campaign leads in Pipl.ai stay in sync with the rest of your tools without copy and paste? The Pipl.ai Make integration gives you 5 action modules for leads and the blocklist. This guide connects your account, then walks you through a first scenario you can switch on.

Try the Pipl.ai integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Pipl.ai Make integration let you automate?

The Pipl.ai Make integration links your Pipl.ai account to Make so that other apps can push leads into a campaign, edit them, pull them out, or block an address. You build a scenario, the automation made of modules, where each module is one brick: here, every Pipl.ai brick is an action.

Clean suppression list. When someone asks to stop hearing from you in your CRM or help desk, a scenario runs Add Email address in Blocklist, then Remove leads from campaign, so the address is out of every sequence on the same run.

Leads that arrive by themselves. A form, a sheet or a CRM fires the scenario, and Add Lead to Campaign drops each new contact into the right campaign. When a detail changes later, Update Campaign Lead edits the record instead of creating a duplicate.

Anything else the API offers. Make an API Call reuses the same connection to reach an endpoint the four other modules do not cover.

Know the limits before you start. Pipl.ai has no trigger module in Make, so another app or the Make schedule has to start the scenario. Make also states that its own documentation for Pipl.ai is limited because little public information exists about the app, so test each module with a real record. The same app often has an n8n node too; the n8n vs Make page lays out the differences between the two tools, and the Make training covers the editor from scratch. If a run fails, Make troubleshooting lists the usual fixes.

Connect

How do you connect Pipl.ai to Make?

  1. 01

    Add a Pipl.ai module

    In your scenario, pick any Pipl.ai module, for example Add Lead to Campaign. Inside the module, click Create a connection. A connection is your Pipl.ai account linked to Make once, then reused by every Pipl.ai module you add later.

  2. 02

    Name the connection

    Give it a clear name if you like, such as the workspace or client it belongs to. This step is optional, yet it saves confusion once several accounts sit side by side in the same Make organization.

  3. 03

    Authorize and save

    Depending on what the window asks, either sign in to Pipl.ai and approve access for Make, or paste the key Pipl.ai gives you. Click Save. Make then fills the module with the choices it can read from your account.

First scenario

Your first scenario with Pipl.ai

GoalWhen a contact unsubscribes in another app, Make blocks the address in Pipl.ai and pulls it out of the campaign.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. The first module is the app where unsubscribes happen, such as your CRM or email tool, since Pipl.ai has no trigger.

  2. 02

    Add the blocklist step

    Click the + to the right of the first module, search for Pipl.ai and choose Add Email address in Blocklist. Create the connection, then map the email that arrives from the first module into it.

  3. 03

    Remove the lead

    Add Remove leads from campaign after it. Pick the campaign from the list Make shows once the connection exists, and map the same email again so both steps target one person.

  4. 04

    Test with Run once

    Click Run once with a test contact. Each module shows the bundles it received, one bundle being one item passing through, so you can check the address went where you expected.

  5. 05

    Schedule and switch on

    On the first module, open the clock to set the schedule; a new scenario checks every 15 minutes by default. Then switch the scenario on, and each run counts operations, one per module per bundle, on your plan.

Modules

What can the Pipl.ai modules do?

Pipl.ai gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Pipl.ai1

Add Email address in Blocklist

Action

In Make“This will add email or domain entries to the blocklist.”

This module keeps an address or a whole domain away from your Pipl.ai outreach by writing it into the blocklist, so no campaign contacts it again.

When to use it
a prospect replies asking to be left alone, or a client asks you to stop targeting their company domain, and you want that request honored without anyone opening Pipl.ai.
Watch out
blocking stops future sends, but pair it with Remove leads from campaign if the person is already enrolled.
Pipl.ai2

Add Lead to Campaign

Action

In Make“Add single lead to a campaign”

You get a new contact enrolled in a chosen Pipl.ai campaign the moment another app hands it over, one lead per bundle, with no import file to prepare.

When to use it
a demo form, a new row in a sheet or a deal stage in your CRM should put the person into a sequence straight away.
Watch out
if the contact may already exist in the campaign, route it to Update Campaign Lead instead, so you edit the record rather than guess.
Pipl.ai3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call”

Here you reach any endpoint of the Pipl.ai API from your scenario, reusing the connection you already created, which covers what the four named modules leave out.

When to use it
you need an action that has no ready module, and you have the Pipl.ai API reference open to know the path and the request body.
Watch out
you build the request yourself, so test it with Run once and read the response bundle before switching the scenario on.
Pipl.ai4

Remove leads from campaign

Action

In Make“Remove leads from campaigns. The specified lead emails will be removed from the campaign.”

With this action you pull one or more lead emails out of a campaign, so those people stop receiving its next steps while the campaign keeps running for everyone else.

When to use it
a lead books a meeting, becomes a customer or turns out to be the wrong contact, and the sequence should end for them.
Watch out
removal targets the email you map, so check it matches the address stored in Pipl.ai, and try it first on a test lead.
Pipl.ai5

Update Campaign Lead

Action

In Make“This will update the lead in the campaign.”

This one edits a lead that already sits in a campaign, so the details Pipl.ai uses stay aligned with your source of truth rather than frozen at import.

When to use it
a contact changes job title or company in your CRM, and the campaign should reflect it before the next message goes out.
Watch out
it only works on a lead already in the campaign; for a brand new contact, Add Lead to Campaign is the right module.
Need help

Need help automating Pipl.ai with Make?

A person reads every message.

FAQ

Pipl.ai and Make: frequent questions

01Is the Pipl.ai Make integration free?
Yes, on the Make side. Pipl.ai is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits per month. Your Pipl.ai subscription is a separate matter that this page does not cover.
02What do you need to connect Pipl.ai to Make?
A Pipl.ai account and a Make account. The documentation Make publishes lists no special prerequisite for this app. You add any Pipl.ai module, click Create a connection, optionally name it, then either authorize Make on the Pipl.ai page or paste the key Pipl.ai provides, and save. Make itself notes that its guide for Pipl.ai is limited, so a quick Run once with a test lead is the safest way to confirm the connection works.
03Does the Pipl.ai Make integration have a real-time trigger?
No. Pipl.ai has no trigger module in Make, only 5 actions. The scenario therefore starts from another app: an instant trigger fires as soon as that app calls Make, while a scheduled trigger is checked on the scenario schedule, every 15 minutes by default. You can also start the scenario from the schedule alone. Either way, the Pipl.ai modules run right after the first module hands them a bundle. Pick the source app that fits your process, a form tool or a CRM for example.
04What if a Pipl.ai module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Pipl.ai API with the connection you already have, so an action outside the four named modules is still within reach. You will need the Pipl.ai API reference to build the request. Keep in mind that Make describes its own Pipl.ai documentation as limited because public information about the app is scarce, so check each response with Run once before relying on it.
05Should you use Make or n8n for Pipl.ai?
It depends on the tool your team already runs. In Make, Pipl.ai comes with 5 action modules, including Make an API Call for the rest of its API, and no trigger. The same app often has an n8n node as well, so check what that node covers against the actions you need. The comparison page linked in the section above sets out how the two tools differ, without deciding for you.
Same platform

Other docs you might need on this stack.

Browse all integrations