Resources · Zapier integration

Pipeline Zapier integrationAutomate Pipeline with Zapier.

2 triggers, 17 actions, 3 searches. The Pipeline Zapier integration lets other tools open, move and close Asks in Pipeline, and lets Pipeline start work elsewhere. Here: the cost in tasks, the connection, a first Zap, every operation and what breaks.

See the 22 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Pipeline Zapier integration does for your team

Pipeline runs requests, called Asks, through Flows made of steps, across teams and even across companies. The integration lets a Zap (an automation on Zapier: a starting event, then the steps that follow) react to those Asks and act on them, so nobody copies a request from one tool to another by hand.

Three results teams build with it. Requests opened from outside: a form answer or a ticket in another tool becomes an Ask through Create Ask, in the right Flow. Work routed without a meeting: when an Ask appears, Reassign Step hands a step to the right colleague and Add Note to Step leaves the context they need. Status pushed back out: New Ask watches a Flow for created, closed or canceled Asks, and a following action in another tool updates a client file or a team channel.

What Zapier does not do for Pipeline. Both triggers work by checking on a timer, so nothing starts the instant an Ask changes. No step deletes an Ask; the closest you get is Close Ask or Cancel Ask. And steps that need a step ID expect you to fetch it first with a search, which makes the Zap multi-step and puts it on a paid plan.

If you want a second opinion on the platform itself, the Zapier review is a good place, and n8n vs Zapier sits alongside it.

Vocabulary

Zapier vocabulary, in one minute

Eight words you will meet in the editor, in plain English.

Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, for instance a new Ask in Pipeline.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you, like closing an Ask.
Task
The unit Zapier bills: one action your Zap carried out successfully. Your plan's allowance is counted in tasks.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. Both Pipeline triggers work this way.
Instant trigger
A trigger the app reports itself, calling Zapier the moment the event happens. Pipeline offers none on Zapier.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it there otherwise.
Search step
A step that looks up something already in an app, an Ask or one of its steps, so later steps can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it needs a paid plan.
Cost

What it really costs

Pipeline is not reserved for paid plans: it works on the free plan.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan Zap sizeTwo steps: one trigger, one action
  • Pipeline triggers2, both polling
  • Searches and filtersMake the Zap multi-step: paid plan

The trigger never costs a task, and Zapier checking Pipeline for new Asks is free however often it looks. Each action that succeeds counts as one task; one that fails does not. The free plan gives 100 tasks a month, but Zaps of two steps only: New Ask plus Send Email fits, New Ask plus Retrieve Ask plus Reassign Step does not. A filter or a search makes the Zap multi-step, so it needs a paid plan. The plan also sets how often polling triggers are checked.

Connect

Connect your Pipeline account

  1. 01

    Go to your apps

    In Zapier, open the Apps page of your account. You need a Pipeline account, plus access to the Flows and Asks the Zap will touch when they belong to someone else.

  2. 02

    Add Pipeline

    Click + Add connection, type Pipeline in the dialog's search box and pick Pipeline from the results. Then click Add connection to open the sign-in tab.

  3. 03

    Sign in and grant access

    Sign in to Pipeline in the tab that opens and grant Zapier access to the account. The connection is saved once and every Pipeline step of every Zap reuses it.

First Zap

Your first Zap: route each new Ask to the right person

GoalWhen a new Ask lands in a chosen Flow, its step goes to the colleague who should handle it.

  1. 01

    Set the trigger

    Create a Zap, pick Pipeline and New Ask. Choose the Flow to watch and the Status that matters, for instance newly created Asks.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent Asks of the connected account. Pick a real one so the next steps are mapped on actual data.

  3. 03

    Fetch the step ID

    Add Retrieve Ask and map the Ask ID from the trigger. This search returns the full Ask, including the step ID the next action needs. It makes the Zap multi-step: paid plan.

  4. 04

    Reassign the step

    Add Reassign Step. Map the Ask ID, the step ID found by the search, and the email of the colleague who takes over the step from now on.

  5. 05

    Test, then publish

    Test each step once and check the result in Pipeline. Then publish the Zap to switch it on. Asks created before that moment are not picked up.

Triggers

Pipeline triggers

2 events start a Zap when something happens in Pipeline. Zapier checks for them at the interval your plan allows.

1

New Ask

Polling trigger

In Zapier“Triggers when a new Ask is created, closed or canceled. Note, this trigger will only occur once per status.”

Starts your Zap when an Ask in the Flow you chose is created, closed or canceled, depending on the Status you set. Each Ask fires it only once per status, so a closed Ask does not come back twice as closed.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
telling a client, a manager or another tool that a request has opened or reached its end.
Watch out
Flow and Status are both required, so one Zap watches one Flow and one status; covering several means several Zaps.
2

Update Ask

Polling trigger

In Zapier“Triggers when an Ask is updated. Note, this trigger could occur multiple times for the same Ask.”

Opens your Zap whenever an Ask in the selected Flow and Status is changed. Unlike New Ask, it can fire several times for the same Ask, once per update Zapier sees.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
keeping a copy of the Ask in sync elsewhere, such as a tracking sheet or a client portal.
Watch out
if the same Zap changes that Ask with Update Field or Add Note to Step, it can set itself off again and burn tasks in a loop.
Actions

Pipeline actions

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

1

Add AdHoc Step

Action

In Zapier“Adds an adhoc step to the Ask for a contact or a team”

Inserts an extra step into a running Ask, for a contact or a team, outside what the Flow planned.

When to use it
a contract over a given threshold needs a legal review that the standard Flow does not include.
Watch out
you must say where it goes: New Step Order is required and takes the position number of the step.
2

Create Bundle

Action

In Zapier“Creates a Bundle with you as the owner”

Sets up a Bundle, a group for related Asks, with a name and an overview, and makes the connected account its owner.

When to use it
a new project starts and its requests need one place to sit together.
Watch out
both the Bundle name and the overview are required, and the overview accepts formatting tags.
3

Add Ask to Bundle

Action

In Zapier“Adds an Ask to a Bundle”

Places an existing Ask inside a Bundle, given the Ask ID and the Bundle.

When to use it
every Ask tagged with a project code in another tool joins that project's Bundle automatically.
Watch out
the Bundle has to exist already; Create Bundle can set one up in an earlier step.
4

Attach File to Step

Action

In Zapier“Attaches a file to a step in the ask”

Puts a file on a step of an Ask from a link to that file, so a quote, a contract or a photo sits where the work happens.

When to use it
a signed document arrives in cloud storage and belongs on the signature step.
Watch out
it needs a step ID, and the field itself tells you to get it with Retrieve Ask first.
5

Add Follower to Ask

Action

In Zapier“Adds a follower to an Ask”

Adds someone, by email, as a follower of an Ask so they can keep an eye on it without owning a step.

When to use it
the account manager of a client follows every Ask that client raises.
Watch out
both the Ask ID and the email are required, so map them from earlier steps.
6

Add Note to Step

Action

In Zapier“Adds a note to a step in the ask”

Writes a note on a step of an Ask, so the person working on it sees the context without leaving Pipeline.

When to use it
pasting a customer's reply from the support inbox onto the step that handles it.
Watch out
on a Zap started by Update Ask, a note on that same Ask can count as an update and start the Zap again.
7

Cancel Ask

Action

In Zapier“Cancels an open Ask”

Cancels an open Ask, with a required note explaining why.

When to use it
a customer withdraws a request in your helpdesk, and the matching Ask should stop rather than close as done.
Watch out
a Zap on New Ask with the canceled status will pick this up on its next check.
8

Close Ask

Action

In Zapier“Closes an open Ask”

Closes an open Ask and records a closing note, which is required.

When to use it
the work is confirmed done in another tool, say a delivery marked received, and the Ask should end.
Watch out
it only acts on open Asks.
9

Complete Step

Action

In Zapier“Completes a step in an Ask”

Marks a step of an Ask as done, which only needs the ID.

When to use it
a payment confirmed in accounting closes the payment step in Pipeline with nobody clicking anything.
Watch out
the ID field is the only required one, so check which Ask or step it points to before publishing.
10

Create Ask

Action

In Zapier“Creates an Ask with you as the submitter”

Opens a new request in Pipeline, in the Flow you pick, with the connected account recorded as the submitter.

When to use it
a purchase request typed into a form becomes an Ask that follows its approval Flow.
Watch out
the Ask always shows the connected account as submitter, not the person who filled in the form.
11

Create Contact

Action

In Zapier“Create a contact in Pipeline”

Adds a person to Pipeline with a first name, a last name and an email, all three required.

When to use it
a new supplier or client signs up somewhere else and needs to exist in Pipeline before Asks reach them.
12

Reassign Step

Action

In Zapier“Reassigns a step to someone”

Gives a step of an Ask to someone else, identified by email, so the work moves without a manual handover.

When to use it
a holiday calendar shows the usual approver is away and the step goes to the backup.
Watch out
like Attach File to Step, it wants a step ID that Retrieve Ask provides.
13

Remove Ask From Bundle

Action

In Zapier“Removes an Ask from a Bundle”

Takes an Ask out of a Bundle it belongs to, without touching the Ask itself.

When to use it
a request is moved to another project and should stop showing in the old group.
Watch out
it needs the same pair as Add Ask to Bundle: the Ask ID and the Bundle.
14

Send Email

Action

In Zapier“Sends a Pipeline notification email with a customizable body”

Sends a Pipeline notification email to one recipient, with your own subject and a body placed inside Pipeline's email template.

When to use it
warning an outside partner that a request needs their attention, without giving them a seat in another tool.
Watch out
recipient email, recipient name, subject and body are all required.
15

Skip Step(s)

Action

In Zapier“Skips steps in an ask”

Jumps over one or more steps of an Ask, named by their step names.

When to use it
small orders under an agreed limit skip the manager approval.
Watch out
skipped steps are not left open: Pipeline Bot completes them, and that is what the history will show.
16

Spawn Ask

Action

In Zapier“Spawns an ask from a parent ask”

Creates a child Ask from an existing parent Ask, so one request can split into separate pieces of work.

When to use it
an approved onboarding Ask spawns a separate equipment request for IT.
Watch out
Include Files? links the parent's files to the new Ask; it does not make copies of them.
17

Update Field

Action

In Zapier“Update a field in an Ask”

Changes the value of one field on an Ask, named by its field name, with the new value you map.

When to use it
a budget approved in finance software is written back onto the matching Ask.
Watch out
the Ask ID, the field name and the new value are all required, and on a Zap started by Update Ask this write counts as one more update.
Searches

Pipeline searches

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

A search step reads Pipeline and hands the result to the next step. In the editor, the three Pipeline searches sit at the bottom of the Action event list, under the SEARCH heading. Three settings decide what happens when the answer is not one clean match.

1

Find Ask

Search

In Zapier“Finds an Ask based on search criteria”

Looks for an Ask from search criteria rather than from its ID, handy when another tool only knows what the request is about.

When to use it
a client emails about a request and the Zap needs the Ask before adding a note to it.
Watch out
several Asks can match; decide in the settings above which one goes on.
2

Retrieve Ask

Search

In Zapier“Retrieves an Ask with full data based on the ID”

Pulls one Ask with its full data from the ID you give it, including the step IDs other actions ask for.

When to use it
just before Attach File to Step or Reassign Step, both of which point to it for their step ID.
3

Retrieve Ask Step

Search

In Zapier“Retrieves the Ask Step based on the Ask ID”

Finds one step inside an Ask, from the Ask ID plus keywords found in the step's name or description.

When to use it
you know the step is called something like legal review but not which position it holds.
Watch out
keywords are required and are matched against the step's name or description, so pick words that only that step carries.

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 and skips the steps that relied on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. None of the three Pipeline searches offers that variant, so it will not appear here.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks

When it breaks

Zapier links no help article to Pipeline, so these cases come from how Zapier works in general and from the notes written on the operations themselves.

With Pipeline, most surprises come from the triggers: they check on a timer, they watch one Flow and one status, and one of them can fire more than once per Ask. When a Zap misbehaves, start with Zapier troubleshooting.

  • Older Asks are never picked up

    A Zap only reacts to what happens after it is switched on. Asks created or closed before that stay out of it; moving that history is a separate job.

  • A Zap that keeps setting itself off

    A Zap on Update Ask that writes back into the same Ask, with Update Field or a note, can start itself again and again and eat through the task count.

  • Update Ask fires several times

    Unlike New Ask, Update Ask can run more than once for the same Ask. Plan the following actions so a second run does no harm, or switch to New Ask.

  • No double start on New Ask

    Zapier remembers what a polling trigger has already returned, and New Ask fires once per status, so the same closed Ask does not start the Zap twice.

  • Missing step ID

    Attach File to Step and Reassign Step need a step ID, and the field itself says to get it with Retrieve Ask. Without that search before them, the required step field has nothing to map.

  • A bulk change gets held back

    When a Flow suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold it back instead of running every Zap.
Need help

Need help automating Pipeline with Zapier?

A person reads every message.

FAQ

Pipeline Zapier integration: questions people ask

01Is the Pipeline Zapier integration free?
Yes, within limits. Pipeline is not one of the apps Zapier reserves for paid plans, so it runs on the free plan: 100 tasks a month and unlimited Zaps. Each Zap is capped at two steps, though, one trigger and one action. New Ask followed by Send Email fits. Anything that needs Retrieve Ask to fetch a step ID, a filter or a second action makes the Zap multi-step, and that requires a paid plan.
02How many tasks does Pipeline use on Zapier?
One task for each action that succeeds. Creating an Ask, closing it or sending an email each count once when they work; a failed action is not counted. The two triggers cost nothing, and Zapier checking Pipeline for new or updated Asks is free however often it happens. Watch Update Ask: since it can fire several times for the same Ask, every extra run repeats the tasks of the actions that follow.
03Does Pipeline on Zapier work in real time?
No. Both Pipeline triggers, New Ask and Update Ask, are polling triggers: Zapier checks on a timer. That is every 15 minutes on Free, every 2 minutes on Professional, and every minute on Team and Enterprise. Paid plans can also change how often a polling trigger checks, and run a check by hand from the editor. Pipeline offers no instant trigger on Zapier, so there is no way to skip the wait.
04What does connecting Pipeline to Zapier take?
A Pipeline account, plus access to the Flows and Asks you want the Zap to touch if they belong to someone else. In Zapier, open the Apps page, click + Add connection, search for Pipeline and pick it, then click Add connection. Sign in to Pipeline in the tab that opens and grant Zapier access. Once saved, the connection is reused by every Zap with a Pipeline step, and the account must see the Flows the triggers ask for.
05Why does Update Ask start the Zap several times for one Ask?
Because that is how this trigger is built: it fires on updates, and one Ask can be updated many times. New Ask works differently and fires only once per status. If a Zap on Update Ask then changes the same Ask, with Update Field or Add Note to Step, it can trigger itself in a loop and burn tasks fast. Either pick New Ask with the right status, or make sure the actions never touch the Ask that started the run.
06What if the Pipeline operation you need is not listed?
Then Zapier does not offer it today. The visible catalog has 2 triggers, 17 actions and 3 searches covering Asks, steps, Bundles, contacts and notification emails. There is no instant trigger, no delete step for an Ask, and no trigger on a step being completed. Those needs have to be handled inside Pipeline or another way. The Pipeline page on Zapier remains the reference, since an app's catalog can change between two readings.
07Zapier, Make or n8n for Pipeline?
Decide on criteria, not a ranking. On Zapier, three questions settle it. Does a check every few minutes suit your process, given that both Pipeline triggers are polling? Do your Zaps stay at two steps, or do they need Retrieve Ask for step IDs, which means a paid plan? Do the 17 actions cover what you do with Asks? Hold the other platforms' Pipeline offers up against those same three points before you choose.
Same platform

Other docs you might need on this stack.

Browse all integrations