Resources · Make integration

Pipeliner CRM Make integrationAutomate Pipeliner CRM with Make.

Can Make react the moment a lead lands in Pipeliner CRM? Yes. The Pipeliner CRM Make integration gives you 43 modules, including 12 instant triggers. This guide is for sales and ops teams: connect your account, then build a first scenario that turns each new lead into a follow-up task.

Try the Pipeliner CRM integration on MakeSee the 43 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Pipeliner CRM Make integration let you automate?

The Pipeliner CRM Make integration links your CRM to Make, a no-code tool where you build a scenario: a chain of modules that runs when something happens. Pipeliner CRM tells Make as soon as an account, contact, lead, opportunity, appointment or task is created or changed, and Make can create, read, update, list or delete those same records.

Leads that never wait. Start with Watch New Lead and add Create a Task: every lead coming from a form or an import gets a follow-up task before anyone has to remember it.

A deal update that reaches the right people. Watch Updated Opportunity fires when a rep changes an opportunity. Make can then pass the change to a chat tool, a spreadsheet or an invoicing app, so finance hears about a deal without opening the CRM.

A cleaner database. List Contacts returns every contact as a separate bundle, and Update a Contact fixes each one in turn, handy after a messy import. Tables built in the Airtable Make integration are a common source for that kind of cleanup.

What Make will not do here: the official documentation for Pipeliner CRM is limited, with no connection guide and no troubleshooting notes. When a listed module falls short, Make an API Call reaches the rest of the Pipeliner API with the same connection. The Make troubleshooting guide helps when a run fails.

Pipeliner CRM may also have a node in n8n. The n8n vs Make comparison lays out how the two tools differ, without picking a winner for you.

Connect

How do you connect Pipeliner CRM to Make?

  1. 01

    Add a Pipeliner CRM module

    In your scenario, click the + and search for Pipeliner CRM. Pick any module, for example Watch New Lead, then click Create a connection. A connection is your Pipeliner account linked to Make once, and every Pipeliner module reuses it.

  2. 02

    Name the connection

    Make offers a name field for the connection. It is optional, but a clear label such as the team or the Pipeliner space it belongs to saves confusion later, when several people build scenarios on the same Make organization.

  3. 03

    Authorize and save

    Make then asks you either to approve access on a Pipeliner page or to paste a key that Pipeliner gives you. Follow what the window shows, then click Save. The module can now read your accounts, leads and opportunities.

First scenario

Your first scenario: a follow-up task for every new lead

GoalWhen a new lead is created in Pipeliner CRM, Make creates a follow-up task for it.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big + in the middle of the canvas. That circle becomes your first module, the one that starts everything.

  2. 02

    Add Watch New Lead

    Search for Pipeliner CRM, choose Watch New Lead and select your connection. This trigger is instant: Pipeliner calls Make through a webhook as soon as a lead is created.

  3. 03

    Add Create a Task

    Click the + on the right of the trigger and pick Create a Task. Fill its fields by mapping data from the lead, so the task mentions the lead it belongs to.

  4. 04

    Test with Run once

    Click Run once, then create a test lead in Pipeliner. Each module shows the bundle it received, meaning the item passed along, here one lead. Check that the task appears in Pipeliner.

  5. 05

    Switch the scenario on

    Save, then turn the scenario on. Because the trigger is instant, Make runs the scenario whenever Pipeliner reports a new lead instead of checking on the default 15-minute schedule.

Triggers

Which Pipeliner CRM triggers can start a scenario?

12 modules start a scenario when something happens in Pipeliner CRM. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Pipeliner CRM as soon as it happens.

Pipeliner CRM1Watch New Account

Watch New Account

Instant trigger

In Make“Triggers when a new account is created.”

You get a scenario that starts the moment a company account appears in Pipeliner CRM, so onboarding steps no longer depend on someone noticing it. Each new account arrives in Make as one bundle you can pass to the next module.

How it fires
instant, Pipeliner CRM calls Make through a webhook as soon as the account is created.
When to use it
a new customer company should get a folder, a welcome sequence or a row in a shared tracker.
Watch out
each new account is a separate run with its own operations, so busy days add up.
Pipeliner CRM2Watch New Appointment

Watch New Appointment

Instant trigger

In Make“Triggers when a new appointment is created.”

Booked meetings stop living only in the CRM calendar: this trigger hands every new Pipeliner appointment to Make, where you can copy it elsewhere or prepare the meeting. It is the entry point for anything that should happen once a rep schedules a call.

How it fires
instant, Pipeliner CRM notifies Make by webhook right when the appointment is created.
When to use it
a demo gets booked and the solutions engineer should hear about it without checking the CRM.
Watch out
a rescheduled meeting is a change, so it needs Watch Updated Appointment instead.
Pipeliner CRM3Watch New Contact

Watch New Contact

Instant trigger

In Make“Triggers when a new contact is created.”

Every person added to Pipeliner CRM can travel straight to your email tool, your support desk or a spreadsheet, with no copy and paste. This trigger passes the new contact to the rest of the scenario as a single bundle.

How it fires
instant, the CRM calls Make through a webhook the moment the contact is saved.
When to use it
marketing wants each new contact in its newsletter list, or support needs the same person in its help desk.
Watch out
if another scenario also creates contacts in Pipeliner, check that the two do not feed each other endlessly.
Pipeliner CRM4Watch New Lead

Watch New Lead

Instant trigger

In Make“Triggers when a new lead is created.”

Speed on fresh leads is the whole point here: the scenario starts as soon as a lead is created, so the follow-up begins while the prospect still remembers filling in your form. It is the trigger used in the first scenario above.

How it fires
instant, Pipeliner CRM sends the lead to Make by webhook right after it is created.
When to use it
assign a task, alert the rep in charge or enrich the lead with a data provider.
Watch out
a lead that is later edited will not fire this trigger again; Watch Updated Lead covers edits.
Pipeliner CRM5Watch New Opportunity

Watch New Opportunity

Instant trigger

In Make“Triggers when a new opportunity is created.”

A new deal in the pipeline can set a whole chain in motion: a quote draft, a notice to the manager, a line in the forecast sheet. This trigger delivers each opportunity to Make when it is opened in Pipeliner CRM.

How it fires
instant, Pipeliner CRM pushes the opportunity to Make through a webhook as soon as it exists.
When to use it
sales leadership wants to see every new deal in a chat channel, or finance tracks the pipeline in its own tool.
Watch out
stage changes on that deal come through Watch Updated Opportunity, not this one.
Pipeliner CRM6Watch New Task

Watch New Task

Instant trigger

In Make“Triggers when a new task is created.”

Tasks created in the CRM can land in the to-do tool your team really opens, so nothing assigned in Pipeliner gets forgotten. The trigger hands each new task to the next module as one bundle.

How it fires
instant, Make hears about the task through a webhook from Pipeliner CRM right after it is created.
When to use it
reps plan their day in a project tool or a calendar and want Pipeliner tasks there too.
Watch out
the first scenario on this page creates tasks; pairing it with this trigger in a scenario that writes back to Pipeliner can loop.
Pipeliner CRM7Watch Updated Account

Watch Updated Account

Instant trigger

In Make“Triggers when an account is updated.”

When someone edits a company record, the other tools that hold a copy of it can follow along instead of drifting out of date. This trigger sends the changed account to Make each time it is saved with new details.

How it fires
instant, Pipeliner CRM calls Make by webhook whenever the account is updated.
When to use it
your billing or support tool keeps company records that must match the CRM.
Watch out
a scenario that updates the same account in Pipeliner will trigger itself again, so add a filter before any write back.
Pipeliner CRM8Watch Updated Appointment

Watch Updated Appointment

Instant trigger

In Make“Triggers when an appointment is updated.”

Moved, renamed or edited meetings reach Make as soon as they change, so the copies in other calendars or reminders stay correct. This is the counterpart of Watch New Appointment for everything that happens after booking.

How it fires
instant, Pipeliner CRM notifies Make through a webhook each time an appointment is updated.
When to use it
a prospect reschedules and the reminder sent by another tool has to follow the new slot.
Watch out
every save counts as an update, so one meeting edited several times starts several runs, each costing operations.
Pipeliner CRM9Watch Updated Contact

Watch Updated Contact

Instant trigger

In Make“Triggers when a contact is updated.”

A new phone number or job title typed in Pipeliner CRM can flow to every other tool that knows this person. The trigger hands the edited contact to Make so the next module can copy the fresh details.

How it fires
instant, the CRM sends the contact to Make by webhook right after the change.
When to use it
your mailing tool or help desk should always show the same details as the CRM.
Watch out
each run uses at least one operation, which is one module handling one bundle and what Make counts on your plan; frequent edits add up.
Pipeliner CRM10Watch Updated Lead

Watch Updated Lead

Instant trigger

In Make“Triggers when a lead is updated.”

Lead edits become signals: a status change, a new owner or an added note can move the lead forward in other tools without anyone copying it over. Make receives the lead each time it is updated in Pipeliner CRM.

How it fires
instant, Pipeliner CRM calls Make through a webhook after each update.
When to use it
a lead gets qualified and marketing should stop nurturing it right away.
Watch out
the trigger fires on any edit, so add a Make filter after it that lets through only the change you care about.
Pipeliner CRM11Watch Updated Opportunity

Watch Updated Opportunity

Instant trigger

In Make“Triggers when an opportunity is updated.”

Deal progress stops being something people report by hand. Whenever an opportunity changes in Pipeliner CRM, this trigger gives Make the updated deal, ready to feed a forecast, a chat alert or an invoicing step.

How it fires
instant, Pipeliner CRM pushes the opportunity to Make by webhook as soon as it is saved.
When to use it
a deal moves to a late stage and finance or delivery should prepare.
Watch out
with no filter, a small edit such as a typo fix runs the scenario exactly like a stage change.
Pipeliner CRM12Watch Updated Task

Watch Updated Task

Instant trigger

In Make“Triggers when a task is updated.”

A task marked done or pushed back in Pipeliner CRM can update the matching item in your project tool or notify the manager. This trigger passes each edited task to Make the moment it changes.

How it fires
instant, the CRM notifies Make through a webhook after every task update.
When to use it
managers follow completed follow-ups in a report outside the CRM.
Watch out
if your scenario updates tasks in Pipeliner, it can wake this trigger again, so keep reads and writes apart.
Modules

What can Make do in Pipeliner CRM?

Pipeliner CRM gives you 31 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Pipeliner CRM1

Create a Contact

Action

In Make“Creates a new contact.”

People who show up in another tool, like a form, a webinar list or a support ticket, become Pipeliner contacts without retyping. You map their details from the earlier module into the new contact.

When to use it
a form submission should give sales a contact to call.
Watch out
this module always creates; search with List Contacts first if the person may already exist.
Pipeliner CRM2

Create a Lead

Action

In Make“Creates a new lead.”

Inbound interest lands in the pipeline as a proper lead, ready for qualification, instead of sitting in an inbox. Map what the module that caught the request collected into the new lead.

When to use it
ads, landing pages or chat widgets collect prospects outside Pipeliner.
Watch out
the created lead will fire Watch New Lead if another scenario listens to it.
Pipeliner CRM3

Create an Account

Action

In Make“Creates a new account.”

A company signing up in your product or your billing tool gets its account record in Pipeliner, so sales and success see the same customer. Map the company details from the previous step.

When to use it
a new paying customer should exist in the CRM without a manual entry.
Watch out
List Accounts before creating helps you avoid two records for one company.
Pipeliner CRM4

Create an Appointment

Action

In Make“Creates a new appointment.”

Meetings booked through a scheduling page or a calendar end up in Pipeliner CRM next to the deal they belong to. Make fills the appointment with the details passed on by the booking tool.

When to use it
prospects book demos in a tool the CRM does not read by itself.
Watch out
a booking that is later moved needs Update an Appointment, not a second creation.
Pipeliner CRM5

Create an Opportunity

Action

In Make“Creates a new opportunity.”

A signal that a deal is starting, such as a quote request or a trial upgrade, opens an opportunity in the pipeline on its own. The deal is there before a rep has to think of it.

When to use it
a pricing form or a sales chat marks serious buying intent.
Watch out
link it to the right account by mapping the account from an earlier Get or List module.
Pipeliner CRM6

Create a Task

Action

In Make“Creates a new task.”

Follow-ups get written down by the scenario, not by memory. This module adds a task in Pipeliner CRM, and it is the action used in the first scenario of this page.

When to use it
a new lead, a lost deal or an unanswered email should give a rep something clear to do.
Watch out
a scenario started by Watch New Task that also runs this module can keep feeding itself.
Pipeliner CRM7

Delete a Contact

Action

In Make“Deletes the selected contact.”

This module removes a contact from Pipeliner CRM, which helps you honor a removal request or clear out test records that came from other tools. Point it at the contact passed by an earlier module.

When to use it
someone asks to be erased and the request arrives through a form or a ticket.
Watch out
a deletion cannot be undone from Make, so test on a dummy contact with Run once first.
Pipeliner CRM8

Delete a Lead

Action

In Make“Deletes the selected lead.”

Spam and duplicate leads leave the pipeline without a manual sweep. Map the lead that a trigger or a search found, and Make deletes it from Pipeliner CRM.

When to use it
a lead fails a spam check in an earlier step of the scenario.
Watch out
put a filter between the check and this module; one loose condition can wipe real prospects.
Pipeliner CRM9

Delete an Account

Action

In Make“Deletes the selected account.”

Dropping an account record keeps the CRM free of companies you never want to see again, such as test organizations. The account to remove comes from a previous module.

When to use it
a trial company created only for a sandbox needs to go.
Watch out
the Make documentation for Pipeliner does not say what happens to records linked to the account, so try it on a test account before any real run.
Pipeliner CRM10

Delete an Appointment

Action

In Make“Deletes the selected appointment.”

When a meeting is cancelled in the booking tool, this module clears it from Pipeliner CRM too, so reps do not prepare for a call that will not happen.

When to use it
your scheduling app reports a cancellation and the CRM calendar should match.
Watch out
you need the right appointment to delete, so fetch it with List Appointments or Get an Appointment earlier in the scenario.
Pipeliner CRM11

Delete an Opportunity

Action

In Make“Deletes the selected opportunity.”

Opportunities opened by mistake or by a faulty automation vanish from the pipeline, which keeps the forecast honest. Make deletes the opportunity handed over by the previous step.

When to use it
an earlier scenario created duplicate deals and you need a cleanup pass.
Watch out
closing a lost deal is usually an Update an Opportunity; deleting removes the record itself.
Pipeliner CRM12

Delete a Task

Action

In Make“Deletes the selected task.”

Tasks that no longer make sense, for example follow-ups on a lead that turned out to be spam, disappear from reps' lists. Map the task from an earlier module and Make removes it from Pipeliner CRM.

When to use it
a lead is deleted and its open follow-ups should go with it.
Watch out
marking a task done is an update, not a deletion.
Pipeliner CRM13

Get a Contact

Action

In Make“Returns information about the selected contact.”

Need the full details of one person before the next step? Get a Contact reads a single contact from Pipeliner CRM and passes everything it returns to later modules.

When to use it
a trigger gave you only part of the picture, and the full contact record is needed to personalize a message.
Watch out
it reads one known contact; to find someone by criteria, List Contacts is the module.
Pipeliner CRM14

Get a Lead

Action

In Make“Returns information about the selected lead.”

Reading one lead in full lets the scenario decide what to do next based on the full record, not on a partial notice. The module returns the selected lead as one bundle.

When to use it
an update notice arrives and you want the latest version of the lead before routing it.
Watch out
the lead must be pointed to by an earlier module; this is not a search.
Pipeliner CRM15

Get an Account

Action

In Make“Returns information about the selected account.”

The company behind a contact or a deal often holds the detail you need to route the next step. Get an Account fetches that one record so the next module can use it.

When to use it
an opportunity comes in and the account data should shape who gets notified.
Watch out
each Get adds an operation per bundle, so skip it when the trigger already carries what you need.
Pipeliner CRM16

Get an Appointment

Action

In Make“Returns information about the selected appointment.”

Pulling one appointment from Pipeliner CRM gives the scenario the full meeting record, ready to send a reminder or prepare a brief.

When to use it
another tool refers to a meeting and you need its CRM version before acting.
Watch out
run it on a known appointment only; List Appointments is the way to find several.
Pipeliner CRM17

Get an Opportunity

Action

In Make“Returns information about the selected opportunity.”

The current state of a single deal, read straight from Pipeliner CRM, helps you build accurate messages or documents. You pass the opportunity from an earlier module and receive its details back.

When to use it
a quote or contract generator needs the current deal record before it drafts anything.
Watch out
map the opportunity carefully; a wrong mapping reads the wrong deal without any error.
Pipeliner CRM18

Get a Task

Action

In Make“Returns information about the selected task.”

One task, read in full, gives the scenario its latest version from the CRM. That is enough to send a precise reminder or copy it into another tool.

When to use it
a message in your team chat references a task and the bot should reply with its details.
Watch out
Get a Task only reads; changing the task takes Update a Task afterward.
Pipeliner CRM19

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Anything the other modules do not cover can still be reached: Make an API Call sends a request to any endpoint of the Pipeliner CRM API, using the same connection as the rest of your scenario.

When to use it
you need a record type or an operation missing from the 43 listed modules.
Watch out
the Make documentation for Pipeliner CRM is limited, so you will need the Pipeliner API reference to shape the request.
Pipeliner CRM20

Update a Contact

Action

In Make“Updates the selected contact.”

Contact details corrected in another tool, such as a new email from support, flow back into Pipeliner CRM automatically. Pick the contact and map only the fields that changed.

When to use it
your help desk or billing app is where customers update their information.
Watch out
if Watch Updated Contact runs in another scenario, this write will trigger it.
Pipeliner CRM21

Update a Lead

Action

In Make“Updates the selected lead.”

Leads move forward without anyone editing them by hand: a score from a marketing tool or an answer from a chatbot can land on the lead record right away.

When to use it
an enrichment or scoring step produces data that sales should see in Pipeliner.
Watch out
test on a dummy lead with Run once and check in Pipeliner what really changed before switching on.
Pipeliner CRM22

Update an Account

Action

In Make“Updates the selected account.”

Company records stay current when your billing or product data changes. Update an Account writes those new values onto the matching Pipeliner account.

When to use it
a customer upgrades its plan in your product and the account should reflect it for sales.
Watch out
find the account first with List Accounts or a trigger; updating needs to know which record to change.
Pipeliner CRM23

Update an Appointment

Action

In Make“Updates the selected appointment.”

A meeting moved in the booking tool keeps the same appointment in Pipeliner CRM, just with its new time or details, so history and links stay intact.

When to use it
a prospect reschedules through a calendar link outside the CRM.
Watch out
the scenario must know which appointment to change, often fetched with List Appointments.
Pipeliner CRM24

Update an Opportunity

Action

In Make“Updates the selected opportunity.”

Deal progress recorded elsewhere, such as a signed quote or a paid invoice, moves the opportunity in Pipeliner CRM without a rep stepping in.

When to use it
an e-signature or payment tool confirms the deal and the CRM should say so.
Watch out
Watch Updated Opportunity will fire after this write, so keep scenarios that read and write deals clearly separated.
Pipeliner CRM25

Update a Task

Action

In Make“Updates the selected task.”

Checking a box in your project tool can close the matching task in Pipeliner CRM, so reps see one list, not two versions of it.

When to use it
tasks are worked on outside the CRM but reported inside it.
Watch out
a scenario that starts on Watch Updated Task and runs this module on the same task can keep looping.
Pipeliner CRM26

List Accounts

Search

In Make“Lists all accounts.”

This search returns your Pipeliner accounts, each as its own bundle, so the modules after it run once per company. It is the base for exports, audits and bulk fixes.

When to use it
you want every account copied into a spreadsheet or checked for missing data.
Watch out
a search can return zero, one or many bundles, and every module after it costs one operation per bundle.
Pipeliner CRM27

List Appointments

Search

In Make“Lists all appointments.”

Pulling the appointments stored in Pipeliner CRM gives you a feed to build a meeting report or to sync another calendar in bulk.

When to use it
the team wants all CRM meetings in a shared sheet, or needs to find one appointment before editing it.
Watch out
an empty result stops the modules after it, which is normal and not an error.
Pipeliner CRM28

List Contacts

Search

In Make“Lists all contacts.”

Your contact base comes out one person at a time, which is exactly what a cleanup or an export needs. Each contact becomes a bundle the following modules can check or change.

When to use it
after an import, you want to spot duplicates before creating anyone new.
Watch out
on a large base, a full run uses many operations, so test on a small result first.
Pipeliner CRM29

List Leads

Search

In Make“Lists all leads.”

Every lead in Pipeliner CRM can be reviewed by the scenario: stale ones flagged, orphans reassigned, all of them exported to a report.

When to use it
you run a lead review and want the data outside the CRM.
Watch out
Delete a Lead placed right after this search would act on every lead it returns, so add a filter in between.
Pipeliner CRM30

List Opportunities

Search

In Make“Lists all opportunities.”

Your pipeline, read deal by deal, can feed a forecast sheet or a dashboard that finance opens without a CRM seat.

When to use it
leadership wants a pipeline view in a tool it already uses.
Watch out
each returned opportunity is a separate bundle, so aggregate them in Make if the next app expects a single file.
Pipeliner CRM31

List Tasks

Search

In Make“Lists all tasks.”

Open follow-ups across the whole team come out of Pipeliner CRM in one pass, ready for a digest sent to a manager or a copy in a project board.

When to use it
a manager wants a summary of pending tasks outside the CRM.
Watch out
the Make documentation mentions no filter for this search, so plan a Make filter after it to keep only the tasks you need.
Need help

Need help automating Pipeliner CRM with Make?

A person reads every message.

FAQ

Pipeliner CRM and Make: common questions

01Is the Pipeliner CRM Make integration free?
Yes, Pipeliner CRM is a standard app in Make, available from the Free plan. That plan allows 2 active scenarios, a 15-minute minimum between two 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 and count usage in credits. Your Pipeliner subscription is a separate matter, and this page does not cover its price.
02What do you need to connect Pipeliner CRM to Make?
A Pipeliner CRM account and a Make account. Add any Pipeliner module, click Create a connection, optionally name it, then authorize Make on the Pipeliner page or paste the key Pipeliner provides, and save. The Make documentation lists no prerequisite for this app. If the authorization fails, the Pipeliner user probably lacks the rights, so the account admin is the best person to set up the connection. Once saved, the same connection serves all 43 Pipeliner modules, so you only do this once per account.
03Do the Pipeliner CRM triggers in Make react instantly?
Yes. All 12 Pipeliner CRM triggers are instant: the CRM calls Make through a webhook as soon as a record is created or updated. That covers accounts, appointments, contacts, leads, opportunities and tasks. You do not wait for the 15-minute default schedule, since that interval applies to scheduled triggers. Each run still uses operations, so busy records can add up on your plan. To react only to certain changes, place a Make filter right after the trigger.
04What if a Pipeliner CRM module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Pipeliner CRM API with the connection you already created, which covers record types or operations beyond the 43 ready modules. Keep in mind that Make describes its own documentation for this app as limited, so you will rely on the Pipeliner API reference to write the request and read the response. Test each request with Run once and read the bundle it returns before switching the scenario on.
05Should you use Make or n8n for Pipeliner CRM?
It depends on the tool your team already builds in. In Make, Pipeliner CRM comes with 43 ready modules, 12 of them instant triggers, and Make an API Call for the rest. Many apps also have an n8n node, so check whether Pipeliner has one that covers the records you need. Compare the modules each side offers for your exact use case rather than a general ranking. Both paths reach the same Pipeliner data; the difference lies in the tool around it.
Same platform

Other docs you might need on this stack.

Browse all integrations