Resources · Zapier integration

Pipeline CRM Zapier integrationAutomate Pipeline CRM with Zapier.

The Pipeline CRM Zapier integration gives you 17 triggers, 15 actions and 5 searches. Every trigger is instant, the app works on the free plan, and this page walks through what each operation does, what it bills and where a Zap tends to break.

See the 37 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Pipeline CRM Zapier integration actually does

It links your Pipeline CRM account to Zapier. An event in the CRM (a deal won, a person added, a field edited) can start an automation, and other apps can write deals, people, companies, tasks and notes back into it. Nothing to install: you connect the account once, then pick operations from a list.

A handover nobody forgets. Deal Won starts the Zap and Create Task drops the next step into the CRM calendar, so the kickoff exists before anyone thinks about it.

A contact base without twins. A sign-up form feeds Create Person with its duplicate check switched on, and an email address already in the account does not become a second record.

A timeline that tells the whole story. Create Activity adds a note to a deal, a person or a company each time another tool records an exchange. Notes pile up on the timeline; none overwrites the previous one.

What Zapier does not do here: there is no delete action, so removing a record stays a manual job, even though three triggers report deletions. A Zap also ignores everything that existed before you switched it on. On the bright side, all 17 triggers are instant, so a free account reacts as fast as a paid one; the plan only starts to matter once a Zap grows past two steps. For the wider picture, read Make vs Zapier and n8n vs Zapier.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every line of this page. Here is what each one means, in plain terms, before you open the editor.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event, in Pipeline CRM or another app, that starts the Zap. Once the Zap is switched on, Zapier waits for it.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, often a record in the CRM.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself. Every Pipeline CRM trigger is instant.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
Search step
A step that looks up a record that already exists, so the steps after it can use what it found.
Connection
Your Pipeline CRM account linked to Zapier once, then reused by every step of every Zap that touches the app.
Cost

What a Pipeline CRM Zap really costs

Zapier bills tasks, not Zaps. The trigger never costs a task, and looking for new data costs nothing either. Only an action that goes through is counted; one that fails is not.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan Zap sizeTwo steps: one trigger, one action
  • Reserved for paid plans?No, Pipeline CRM works on the free plan
  • Pipeline CRM triggers17 instant, 0 polling

Each successful action counts on its own: a three-action Zap spends three times what a one-action Zap spends. The free plan stops at two steps, one trigger and one action. A second action, a filter or a search makes the Zap multi-step, and that needs a paid plan. Pipeline CRM is not reserved for paid plans. The interval grid below only applies to polling triggers, and this app has none, which is why its triggers ignore it.

Connect

Connect Pipeline CRM to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. Have a Pipeline CRM account ready, with read or write access on any record you do not own and want a Zap to touch.

  2. 02

    Pick Pipeline CRM

    Type Pipeline CRM in the search box of the dialog, choose it in the results, then click Add connection. A new browser tab then opens on the Pipeline CRM side.

  3. 03

    Sign in and grant access

    Sign in to Pipeline CRM in that tab, then grant Zapier access to the account. The connection is saved once and every Zap that uses the CRM reuses it afterwards.

First Zap

Your first Zap: a won deal gets a task and a note

GoalEvery deal marked as won in Pipeline CRM receives a follow-up task and a note on its timeline, without anyone typing them.

  1. 01

    Build: choose the trigger

    In a new Zap, pick Pipeline CRM as the app that starts it and Deal Won as the event, then select the connection you made earlier. A lightning bolt shows the trigger is instant.

  2. 02

    Test it on a real deal

    Run the test. Zapier brings back the three most recent items from the connected account, so you map the next steps on a real won deal rather than an invented one.

  3. 03

    Add Create Task

    Add Create Task as the first action. Name is the only required box: build it from what the trigger returned, so the task clearly points to its deal.

  4. 04

    Add Create Activity

    Add Create Activity and attach the note to the same deal. This second action makes the Zap multi-step, so this version needs a paid plan; on the free plan, stop after the task.

  5. 05

    Test, then publish

    Test each action once and check the result inside Pipeline CRM. When both look right, publish the Zap to switch it on. From then on, each won deal costs two tasks.

Triggers

The 17 Pipeline CRM triggers

17 events start a Zap when something happens in Pipeline CRM, and 17 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Company Field Changed

Instant trigger

In Zapier“Triggers when a specific field on a company changes in your Pipeline CRM account. Select which field to watch.”

Pick one company field and this trigger keeps watch over it. Each time that field is edited on any company in the account, the Zap starts and carries the company with it, while edits to other fields go unnoticed.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
warn your accounting team when the one company field they rely on is changed by a salesperson.
Watch out
Field to Watch is required, so decide which field matters before you build; the trigger reacts to that field and nothing else.
2

Deal Field Changed

Instant trigger

In Zapier“Triggers when a specific field on a deal changes in your Pipeline CRM account. Select which field to watch.”

Same idea, applied to deals: you choose a single deal field, and every edit to it starts the Zap with the deal attached. Changes elsewhere on the record stay quiet.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
ping the account owner in your team chat when someone else touches the field your sales process depends on.
Watch out
pair it with Update Deal on that very field and the Zap sets itself off again and again, burning tasks; write to another field or add a filter.
3

Deal Lost

Instant trigger

In Zapier“Triggers when a deal is marked as lost in your Pipeline CRM account.”

Starts the Zap every time a deal is marked as lost. It gives you one clean exit point for everything that should happen once an opportunity closes the wrong way.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
log the loss in a reporting sheet, or queue a polite check-in with the contact for later.
Watch out
only losses recorded after you publish the Zap come through; deals lost last month are never picked up.
4

Deal Status Changed

Instant trigger

In Zapier“Triggers when a deal in your Pipeline CRM account is updated from one status to another.”

Reacts when a deal moves from one status to another, in either direction. Reach for it when the status itself means something to the rest of your tools.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
keep a project board in step with the CRM, flipping the project state each time the deal status changes.
Watch out
Deal Won and Deal Lost already cover those two outcomes; use this broader trigger for the other statuses, with a filter (paid plan) if only some of them matter.
5

Deal Won

Instant trigger

In Zapier“Triggers when a deal is marked as won in your Pipeline CRM account.”

Fires the Zap when a deal is marked as won. It is the natural starting line for onboarding: the sale is closed, the delivery work begins.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
create a kickoff task, open a client folder in your file storage, or post the win in the sales channel.
Watch out
winning a deal does not turn its company into a customer; add Convert Company to Customer as an action if you want both to happen together.
6

Deleted Company

Instant trigger

In Zapier“Triggers when a company is deleted from your Pipeline CRM account.”

Tells the Zap that a company has just been removed from the account. Since no action can delete anything in Pipeline CRM, this is how your other tools hear about a cleanup done in the CRM.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
archive the matching account in your billing or support tool so both sides stay aligned.
Watch out
the company no longer exists in the CRM when the Zap runs, so do not plan a later step that looks it up there.
7

Deleted Deal

Instant trigger

In Zapier“Triggers when a deal is deleted from your Pipeline CRM account.”

Each deal removed from the account starts the Zap. Handy when your deals are mirrored somewhere else and a deletion should not leave a ghost line behind.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
clear the deal from a forecast spreadsheet or a shared dashboard that copies your pipeline.
Watch out
deleting and losing are two different events; a deal marked as lost does not fire this trigger, Deal Lost does.
8

Deleted Person

Instant trigger

In Zapier“Triggers when a person is deleted from your Pipeline CRM account.”

Starts when a person record disappears from Pipeline CRM. Leads and contacts both count, since the account stores all of them as people.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
remove the address from your newsletter tool, or flag the contact in the helpdesk so support stops writing to them.
Watch out
a large cleanup produces a burst of deletions at once, and Zapier's flood protection may hold part of that batch back.
9

Moved Deal

Instant trigger

In Zapier“Triggers when a deal in your Pipeline CRM account is moved from one deal stage to another.”

Watches your pipeline stages. A deal moved from one stage to another, forward or back, starts the Zap with the deal attached.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
send the proposal template to the contact once the deal reaches your proposal stage, with a filter on that stage.
Watch out
without a filter, every stage change on every deal starts the Zap, and each one spends tasks on a busy pipeline.
10

New Activity

Instant trigger

In Zapier“Triggers when a new activity or note is created in your Pipeline CRM account.”

Covers every new activity or note created in the account, whether a rep typed it or another Zap added it. The note travels with the Zap to the next step.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
copy call summaries into a shared document so people outside the CRM can read them.
Watch out
a Zap that ends with Create Activity on the same account feeds this trigger and loops; keep those two apart.
11

New Event

Instant trigger

In Zapier“Triggers when a new calendar event is created in your Pipeline CRM account.”

Starts on each calendar event created in Pipeline CRM. Meetings booked inside the CRM can then reach the tools that live outside it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
push the meeting to a shared team calendar, or email the attendee a short confirmation from your mail tool.
Watch out
events written by Create Event in another of your Zaps fire it too, so check that two Zaps do not bounce events back and forth.
12

New Task

Instant trigger

In Zapier“Triggers when a new task is created in your Pipeline CRM account.”

Picks up every calendar task created in the account, whoever creates it. Your CRM to-do list becomes a source for other apps.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
mirror sales tasks into the project tool your delivery team already works in.
Watch out
it reacts to creation only; a task that is later edited or marked complete will not start the Zap a second time.
13

New Company

Instant trigger

In Zapier“Triggers when a new company is created in your Pipeline CRM account.”

Runs the Zap for each company added to Pipeline CRM, typed in by hand or brought in some other way. The new company is what the Zap carries forward.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
open a matching folder in your file storage, or create the account in your invoicing app.
Watch out
turning a company into a customer is a different event, covered by New Customer; this trigger only sees creations.
14

New Customer

Instant trigger

In Zapier“Triggers when a company is converted to a customer in your Pipeline CRM account.”

A company converted to a customer starts this Zap. It marks the switch from prospect to paying account, the moment billing and support usually need to hear about.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
create the customer in your invoicing tool and enroll the main contact in a welcome sequence.
Watch out
Convert Company to Customer, used in another Zap, sets this trigger off as well; make sure the two Zaps do not undo each other.
15

New Deal

Instant trigger

In Zapier“Triggers when a new deal is created in your Pipeline CRM account.”

Every new deal created in the account sets this Zap in motion, with the deal as the item it hands to the next step.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
warn the sales manager in a chat channel when an opportunity lands, or start a quote in your proposal tool.
Watch out
deals that already exist when you publish are ignored; moving that backlog into another tool is a separate job.
16

New Person

Instant trigger

In Zapier“Triggers when a new person, lead, or contact is created in your Pipeline CRM account.”

Fires for each new person, lead or contact entered in Pipeline CRM. One trigger covers all three, because the account files them all as people.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
add the newcomer to an email list or a welcome sequence in your marketing tool.
Watch out
if a form already feeds Create Person through another Zap, those records reach this trigger too; avoid sending them back where they came from.
17

Person Field Changed

Instant trigger

In Zapier“Triggers when a specific field on a person changes in your Pipeline CRM account. Select which field to watch.”

Choose one person field, and each edit to it on any contact starts the Zap. The rest of the record can change freely without waking it up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
update a lead's segment in your email tool once a rep changes the qualification field you rely on.
Watch out
Field to Watch is required and points at one field; to follow a second field, build a second Zap.
Actions

The 15 Pipeline CRM actions

Pipeline CRM gives you 15 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Convert Company to Customer

Action

In Zapier“Converts an existing company to a customer in your Pipeline CRM account.”

Turns an existing company into a customer in the account.

When to use it
the first paid invoice in your billing app flips the company to customer status.
Watch out
Company is required, and the conversion fires New Customer, so any Zap watching that trigger will run as well.
2

Create Activity

Action

In Zapier“Creates a new activity (note) on a person, company, or deal. Use this to log meeting notes, call summaries, or any record of interaction — each activity is added to the timeline, not overwritten.”

Logs a note on a person, a company or a deal. Each new activity is added to the timeline; nothing gets overwritten.

When to use it
record call summaries from your phone system, or meeting notes from your note-taking app, on the right record.
Watch out
paired with the New Activity trigger in the same account, it can loop.
3

Create Event

Action

In Zapier“Creates a new calendar event in your Pipeline account.”

Puts a new event in the Pipeline CRM calendar, with its start and end.

When to use it
a demo booked through your scheduling tool shows up in the CRM calendar of the rep.
Watch out
Start Date & Time and End Date & Time are required and need both a date and a time; a time alone defaults to today. Tick All Day? for full-day events.
4

Create Task

Action

In Zapier“Creates a new calendar task in your Pipeline CRM account.”

Adds a calendar task to the account, the simplest way to turn an event elsewhere into a to-do for someone.

When to use it
a support ticket flagged as an upsell chance becomes a call task for the account owner.
Watch out
Name is the only required field, so make it descriptive enough to make sense out of context.
5

Create Company

Action

In Zapier“Creates a new company in your Pipeline CRM account.”

Adds a new company to the account, filled with whatever the earlier steps gave you.

When to use it
a signed order in your e-commerce or billing tool should leave a company record behind in the CRM.
Watch out
nothing here checks for an existing company; run Find Company with its find-or-create option if duplicates worry you.
6

Create Deal

Action

In Zapier“Creates a new deal in your Pipeline CRM account.”

Opens a new deal in the pipeline, ready for your reps to work on.

When to use it
a quote request submitted on your site lands straight in the pipeline as an opportunity.
Watch out
Name is required, so build it from fields the trigger actually returns; an empty name stops the action. Archived, if set to true, files the deal away at once.
7

Create Person

Action

In Zapier“Creates a new person in your Pipeline CRM account.”

Writes a new person into Pipeline CRM, lead or contact, from data another app collected.

When to use it
every webinar registration or contact-form entry becomes a person the sales team can follow up.
Watch out
switch Check for Duplicates? on; it skips the creation when a person with the same email address already exists in the account.
8

Find User

Action

In Zapier“Find an existing user on your Pipeline CRM account.”

Looks up a user of your Pipeline CRM account, the person who logs in, not a contact. Zapier lists it among the actions.

When to use it
you need the right rep before assigning a deal or a task in the next step.
Watch out
a search with the same name sits under SEARCH; pick one and keep it consistent across your Zaps.
9

Move Deal to Next Stage

Action

In Zapier“Moves a deal to next stage.”

Pushes a deal one stage further down the pipeline.

When to use it
a proposal signed in your e-signature tool moves the deal forward without a rep doing it.
Watch out
Id is required, and the move sets off any Zap built on Moved Deal; plan for both Zaps running.
10

Update Event

Action

In Zapier“Updates an existing calendar event in your Pipeline CRM account.”

Changes an event already in the Pipeline CRM calendar, for a moved or extended meeting.

When to use it
a rescheduled meeting in your booking tool updates its twin in the CRM.
Watch out
Event ID is required, so the Zap must carry it from an earlier step; All Day? can switch the event to a full day.
11

Update Task

Action

In Zapier“Updates an existing calendar task in your Pipeline CRM account.”

Edits a calendar task that already exists, including its completion.

When to use it
ticking an item off in your project tool closes the matching task in the CRM via Complete.
Watch out
Task ID is required; keep it in the other tool when the task is first created, or the Zap cannot find it again.
12

Update Company

Action

In Zapier“Updates an existing company in your Pipeline CRM account.”

Changes an existing company record with fresh values from another tool.

When to use it
your billing app holds the latest company details and the CRM should follow.
Watch out
Id is required; get it from a trigger that carries the company or from a Find Company step placed just before.
13

Update Deal

Action

In Zapier“Updates an existing deal in your Pipeline CRM account.”

Edits a deal that already exists, without creating a new one.

When to use it
a payment recorded in your invoicing tool updates the matching deal in the pipeline.
Watch out
Id is required. Setting Archived to true archives the deal, and writing to the field a Deal Field Changed Zap watches can loop.
14

Update Person

Action

In Zapier“Updates an existing person in your Pipeline CRM account.”

Rewrites fields on a person who is already in the account.

When to use it
a contact changes their details in your newsletter tool and the CRM picks up the change.
Watch out
Id is required; a Find Person step placed just before supplies it, and when the field offers the + Add search step button, that button inserts one for you.
15

Upload Document

Action

In Zapier“Uploads a document from a URL and attaches it to a deal, person, or company in your Pipeline CRM account.”

Fetches a file from a link and attaches it to a deal, a person or a company.

When to use it
a signed contract from your e-signature tool lands on the deal it belongs to.
Watch out
File URL is required, and Pipeline CRM downloads the file from that address itself, so the link must point to a file Pipeline CRM can open.
Searches

The 5 Pipeline CRM searches

5 search steps look for data that already exists in Pipeline CRM, so a later step can use it.

Searches sit at the bottom of the Action event list, under SEARCH. Each one adds a step, so a Zap that uses one is multi-step and needs a paid plan. Three of them also exist as find-or-create, which is the same search with one box ticked, not an extra operation. Three settings decide what happens next.

1

Find Activity

Search

In Zapier“Find an existing activity or note in your Pipeline CRM account.”

Retrieves an activity or note already logged in the account, so a later step can read or reuse it.

When to use it
before adding a follow-up note, check what the last logged exchange said.
Watch out
it has no find-or-create variant; if nothing matches, the first setting above decides whether the Zap stops.
2

Find Company

SearchFind or create

In Zapier“Find an existing company in your Pipeline CRM account.”

Locates a company already in Pipeline CRM and passes it to the following steps.

When to use it
it feeds the Id that Update Company and Convert Company to Customer require.
Watch out
the editor also shows Find or Create Company; it is this same search with the creation box ticked, and it then asks for the fields of the new company.
3

Find Deal

SearchFind or create

In Zapier“Find an existing deal in your Pipeline CRM account.”

Brings back a deal that already exists, ready for an update or a stage move.

When to use it
a payment in your billing tool needs the matching deal before Update Deal can touch it.
Watch out
Find or Create Deal is the same search with the creation box ticked; whether it wants an exact or a close match is up to Pipeline CRM.
4

Find Person

SearchFind or create

In Zapier“Find an existing person on your Pipeline account.”

Finds a person record, lead or contact, already in the account.

When to use it
before logging an activity from your phone tool, fetch the person the call belongs to.
Watch out
Find or Create Person is this search with creation switched on, a safer route than Create Person alone when a contact may already exist.
5

Find User

Search

In Zapier“Find an existing user on your Pipeline CRM account.”

Identifies a member of your Pipeline CRM team, someone with a login, from the SEARCH section of the list.

When to use it
route a new deal to the rep named in your form before Create Deal runs.
Watch out
an action called Find User also exists; this is the search version, the one whose settings above apply.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that depend on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create: the setting above disappears and the step asks for the fields needed to create the missing record.
  3. If multiple search results are found?
    Three ways out when several records match: keep the first one (the default), stop the Zap, or hand all of them on at once.
When it breaks

When a Pipeline CRM Zap breaks

Zapier attaches no help article to this app, so the traps below are the general ones, applied to a CRM where many triggers and actions point at the same records.

Most problems come from timing and loops, not from the connection itself. If a Zap still behaves oddly after these checks, the Zapier troubleshooting page is the next stop.

  • The past is never picked up

    A Zap only reacts to what happens after it is switched on. Deals, people and companies already in the account stay where they are; moving them is a separate job.

  • A Zap that triggers itself

    Update Deal writing to the field a Deal Field Changed Zap watches, or Create Activity feeding New Activity, sets the Zap off again and again and eats tasks fast.

  • Bulk imports get held back

    Importing or deleting many records at once sends a large batch of events. Zapier's flood protection can hold that batch back instead of running every Zap.

  • A search that finds nothing

    With default settings, a Find step that comes back empty stops the Zap there, and the update after it never runs. Switch the setting on if the Zap should carry on.
Need help

Need help automating Pipeline CRM with Zapier?

A person reads every message.

FAQ

Pipeline CRM and Zapier: the questions people ask

01Is the Pipeline CRM Zapier integration free?
Yes, as long as the Zap stays at two steps. Pipeline CRM is not reserved for paid plans, so the free plan can use it, with 100 tasks a month and unlimited Zaps. The limit is size: one trigger and one action. A second action, a filter or a search turns the Zap into a multi-step Zap, and that needs a paid plan. Every trigger and action of this app is open to free accounts; a search, being an extra step, is not.
02How many tasks does a Pipeline CRM Zap use?
One task per action that completes successfully, and nothing for the trigger. A Zap that creates a task when a deal is won spends one task per won deal. Add Create Activity after it and the same deal costs two tasks. An action that fails is not counted against the plan. Watching for new deals or people costs nothing either, however often it happens. Keep that in mind before adding a third action: each one adds a task per run.
03Is Pipeline CRM on Zapier real time?
Yes, for all 17 triggers. Each one is instant: Pipeline CRM itself reports the event to Zapier, so the Zap starts right away whatever the plan. The polling interval set by each plan does not apply to any of them. The editor shows a lightning bolt on these triggers. That matters most on the free plan, where polling triggers in other apps wait for the next check. Here, a won deal or a new contact reaches the Zap without that wait.
04What is needed to connect a Pipeline CRM account?
A Pipeline CRM account and a few clicks in Zapier. Open Apps, click + Add connection, search for Pipeline CRM, then sign in and grant access in the tab that opens. The login used should be able to read or edit every record your Zaps will touch, including those owned by colleagues. The connection is made once, then every Zap that touches Pipeline CRM reuses it, so the choice of login affects all of them.
05Why does a Pipeline CRM Zap keep running on its own?
Because it writes into the place its own trigger watches. Update Deal on the field a Deal Field Changed trigger follows, or Create Activity after New Activity, makes the Zap start itself again and again. Each loop spends tasks. Write to another field, add a filter, or split the job into two separate Zaps. Before publishing, test each step once and check what came back in Pipeline CRM, so a loop shows up during the test rather than on your task count.
06What if the operation needed is not in the list?
Then the integration cannot do it directly, and the page lists everything it can. There is, for instance, no delete action for any record. The usual way around is a combination: a search to find the record, then an update. For anything beyond that, check whether a step from another app can cover the gap. The update actions all need a record Id, which a Find step can supply right before them, for example Find Deal ahead of Update Deal.
07Zapier, Make or n8n for Pipeline CRM?
It depends on criteria rather than on a winner. On Zapier, Pipeline CRM brings 37 visible operations, all 17 triggers are instant, and the app works on the free plan, which suits a two-step Zap built by someone non-technical. If your flows need many steps, filters and searches, weigh the cost of a paid plan against the other tools. On Zapier, any search or filter added to the Zap also makes it multi-step, so count that in before comparing.
Same platform

Other docs you might need on this stack.

Browse all integrations