Resources · Zapier integration

Pipefile Zapier integrationAutomate Pipefile with Zapier.

The Pipefile Zapier integration covers 8 triggers, 2 actions and 1 search. Every step of a file request (created, opened, uploaded, completed, expired) can start a Zap at once, and a Zap can add a contact or send a new request for you.

See the 11 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Pipefile Zapier integration handles for you

The Pipefile Zapier integration connects your document collection in Pipefile to the rest of your tools. Each event in the life of a file request can start an automation, and a Zap can create Pipefile contacts or send requests without you opening the app. All eight triggers are instant.

Three results firms build with it. A client file that starts itself: a new customer signs up in your CRM or form tool, and Send Request then asks them for their documents. A team that knows when papers arrive: File Request - File Uploaded fires as each document lands, and the person in charge gets a message instead of refreshing a dashboard. No request left to die quietly: File Request Expired starts the Zap when a deadline passes, and a new request goes out to the same client.

Because every Pipefile trigger is instant, the app reports each event to Zapier itself. The polling interval of your plan never applies, free plan included.

What Zapier does not do with Pipefile: there is no action to mark a request complete, delete it, or download the documents themselves. Edits to a contact are not covered either. The only lookup is Search File Requests, and adding it to a Zap needs a paid plan.

Before you settle on a platform, read Make vs Zapier. Training is also available: Zapier training.

Vocabulary

The Zapier words you will meet

Eight terms come back throughout. Here is each one, once, in everyday words.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the event happens.
Trigger
The Pipefile event that starts the Zap, such as a file uploaded to a request. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once started: the step that writes or sends something, like a new request to a client.
Task
The unit Zapier bills. Each action that completes successfully is one task, and your plan counts those.
Instant trigger
The app reports the event to Zapier the moment it happens. All eight Pipefile triggers work that way.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items. Pipefile has none, so no plan delay applies.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something already in an app, so later steps can use what it found. Pipefile has one.
Cost

What a Pipefile Zap really costs

Pipefile is not a premium app, so the free plan can run it.

  • Any Pipefile trigger0 tasks
  • Successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Filter or searchMulti-step Zap, paid plan

Triggers cost nothing: a request being opened or completed does not touch your allowance. Each Create Contact or Send Request that succeeds is one task, and an action that fails is not counted. The free plan gives 100 tasks a month but only two-step Zaps, so one trigger plus one action. A filter, a second action or Search File Requests turns the Zap multi-step, which needs a paid plan. Since triggers are instant, paying more does not make them faster.

Connect

Connect your Pipefile account in three steps

  1. 01

    Find Pipefile

    Open the Apps page of your Zapier account, click + Add connection, type Pipefile in the dialog and pick it. You need a Pipefile account before you begin.

  2. 02

    Sign in

    Click Add connection and sign in to Pipefile in the tab that opens. Use the account that sends the requests, or one with access to requests created by colleagues.

  3. 03

    Allow access

    Grant Zapier access to the account. The connection is saved once and reused by every Pipefile step, whether it watches requests, creates contacts or sends new requests.

First Zap

Your first Pipefile Zap

GoalWhen a client completes a file request, the account manager gets an email, but only for requests tagged as urgent in your rule.

  1. 01

    Pick the trigger

    Create a Zap, choose Pipefile as the app that starts it and File Request Completed as the event, then select your Pipefile connection.

  2. 02

    Test on real requests

    Run the test. Zapier brings back the three most recent completed requests of the account, so the next steps are built on a real client rather than an empty template.

  3. 03

    Add the filter

    From the plus icon, add a filter: the value to look at, the rule, and the value to compare with. It makes the Zap multi-step, so a paid plan is needed.

  4. 04

    Write the email

    Add your email app as the action and fill in the message with what the test request returned, so the account manager sees at once which client is done.

  5. 05

    Test and publish

    Test the action, check the email, then click Publish. Every request completed after that moment will start the Zap on its own.

Triggers

Pipefile triggers on Zapier

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

1

File Request Completed

Instant trigger

In Zapier“Triggers when a file request is marked complete.”

Fires when a file request is marked complete. That is the finish line of a collection: the file can move to the next stage, be archived or be handed to whoever processes 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
an accounting firm that wants the tax preparer told as soon as a client's paperwork is all in.
Watch out
it waits for the request to be marked complete; a client who uploaded everything but whose request is still open does not start it.
2

File Request Created

Instant trigger

In Zapier“Triggers when a file request is created.”

Runs each time a new file request is created in Pipefile, whoever on the team made it. Useful to keep a log of every collection in progress outside the app.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an office manager who keeps a shared tracker of every request sent to clients this season.
Watch out
never pair it with Send Request in the same Zap, since each request it sends is a new one and starts the Zap again.
3

File Request Expired

Instant trigger

In Zapier“Triggers when a file request expires.”

Starts the Zap when a file request reaches its end date without being closed. It is your safety net for clients who simply never answered.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a mortgage broker who wants a new request sent, or a call scheduled, as soon as a borrower lets a deadline pass.
Watch out
a re-sent request is a new request; if another Zap watches File Request Created, it will fire too.
4

File Request Exported

Instant trigger

In Zapier“Triggers when a file request is exported.”

Triggers when someone exports a file request from Pipefile. An export usually means the documents are leaving Pipefile for another system, which is a good moment to record 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
a compliance lead who wants a trace in a spreadsheet of each request exported, with who it concerned.
Watch out
the trigger reports the export; it does not carry the documents into the next step for you.
5

File Request - File Uploaded

Instant trigger

In Zapier“Triggers when a client uploads a file to a request.”

Goes off when a client uploads a file to a request. It is the most granular trigger of the app: one upload, one run of the Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a small law office that wants a chat message for each document a client sends, so nothing sits unread overnight.
Watch out
a client sending ten files means ten runs; with an action after it, that is ten tasks.
6

File Request Opened

Instant trigger

In Zapier“Triggers when a file request link has been opened by one of the recipients”

Reacts when one of the recipients opens the link of a file request. You learn that the client has seen it, before any document arrives.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a recruiter who wants to call a candidate right after they open the request, while the list of documents is in front of them.
Watch out
opening is not answering; use File Request Responded to know something actually came back.
7

File Request Reminder Sent

Instant trigger

In Zapier“Triggers when a file request reminder is sent.”

Fires when Pipefile sends a reminder for a file request. It tells you which clients are being chased, so your team can add a personal touch.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a property manager who wants a note in the tenant's record each time a reminder about missing papers goes out.
Watch out
it follows the reminders Pipefile sends; it does not let a Zap send one itself.
8

File Request Responded

Instant trigger

In Zapier“Triggers when a file request changes to the responded status, either when a client completes the checklist or uploads a document to an open-ended request.”

Starts when a request switches to the responded status, either because the client completed the checklist or uploaded a document to an open-ended request. It marks the moment the ball is back in your court.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an insurance agency that wants a review task created as soon as a claimant replies.
Watch out
responded is not completed; your team still has to check and close the request.
Actions

Pipefile actions on Zapier

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

1

Create Contact

Action

In Zapier“Add to contacts”

Adds a person to your Pipefile contacts, with the Name and Email it requires. The contact is then ready for future requests.

When to use it
every new client signed in your CRM appears in Pipefile without anyone retyping them.
Watch out
no email in the previous step, no contact: both fields are mandatory.
2

Send Request

Action

In Zapier“Create and send a new request”

Creates a new file request and sends it to the recipient whose Recipient Name and Recipient Email you provide. It is the action that starts a collection from outside Pipefile.

When to use it
a signed engagement letter triggers the request for onboarding documents.
Watch out
each request sent counts one task and can set off File Request Created.
Searches

The Pipefile search on Zapier

1 search step looks for data that already exists in Pipefile, so a later step can use it.

A search step looks for a request that already exists, so the steps after it can use it. It sits at the bottom of the action list, under SEARCH, and adding one makes the Zap multi-step. Three settings decide what happens when the result is not a clean single match.

1

Search File Requests

Search

In Zapier“Finds all file requests matching this search query (contact name, email, tags, etc).”

Looks up file requests that match what you type, such as a contact name, an email or a tag. The request found can feed the next steps of the Zap.

When to use it
before sending a new request to a client, check whether one is already open for them.
Watch out
several requests often match one client, so set the multiple-results option on purpose.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on default, a search that finds nothing stops the Zap and the dependent steps are skipped. Switched on, the Zap carries on with nothing found.
  2. Create X if it doesn't exist yet?
    This box turns a search into find-or-create. Pipefile offers no find-or-create variant on Search File Requests, so it does not apply here.
  3. If multiple search results are found?
    Three ways out when several requests match: keep the first one, the default, stop the Zap, or pass all of them on at once.
When it breaks

When a Pipefile Zap breaks

Zapier links no help article to Pipefile and no app-specific limit has been recorded. The cases below come from how every Zap behaves, applied to file requests.

Most only show once real clients are in the loop. When a Zap stops for no clear reason, see Zapier troubleshooting.

  • The Zap keeps sending requests

    File Request Created as the trigger and Send Request as the action: each request sent is a new one, which starts the Zap again and burns tasks fast.

  • Old requests are ignored

    A Zap only reacts to events after it is published. Requests completed or expired before that never come through; catching up on them is a separate job.

  • A missing email stops the action

    Send Request and Create Contact both require an email. If the step before brings none, the action fails, which costs no task but sends nothing.

  • A bulk send is held back

    Sending many requests at once can return a huge batch of events. Zapier's flood protection may then hold those runs back.
Need help

Need help automating Pipefile with Zapier?

A person reads every message.

FAQ

Pipefile Zapier integration: frequent questions

01Is the Pipefile Zapier integration free?
Yes, the free plan can run it. Pipefile is not a premium app, so Zapier does not hold it back for paid plans. On the free plan you get 100 tasks a month and Zaps of two steps: one Pipefile trigger plus one action, or a trigger from another app plus Create Contact or Send Request. As soon as you add a filter, a second action or Search File Requests, the Zap becomes multi-step and needs a paid plan.
02How many tasks does a Pipefile Zap use?
Only actions that succeed count. None of the eight Pipefile triggers costs a task, so a request being opened or a file being uploaded is free on its own. Each successful Create Contact, Send Request or action in another app is one task, and an action that fails is not counted. Watch File Request - File Uploaded: one client sending many files means many runs, and with an action after it, as many tasks.
03Does Pipefile trigger Zaps in real time?
Yes. All eight Pipefile triggers are instant: Pipefile reports each event to Zapier itself, and the Zap starts right away, whatever your plan. The polling interval that slows many apps on the free plan does not apply to Pipefile at all. This comes from the app, not from a setting you could change in the editor. Paying for a higher plan does not make these triggers any faster. Speed is the same on every plan.
04What does it take to connect Pipefile to Zapier?
A Pipefile account. In Zapier you open Apps, click + Add connection, pick Pipefile, click Add connection, sign in in the tab that opens and grant access. If the requests you want to watch were created by a colleague, the account you connect needs access to them. To use the actions, keep an email address at hand in the earlier steps: both Create Contact and Send Request refuse to run without one.
05Why does a Pipefile Zap keep sending new requests?
Because it is feeding itself. When File Request Created is the trigger and Send Request is the action, each request the Zap sends is a brand new request in Pipefile, which starts the same Zap again. The loop only ends when you switch the Zap off, and each pass costs a task. Pick another trigger, such as File Request Expired, or put the Send Request step in a Zap that starts from your CRM or a form.
06What if the Pipefile operation you need does not exist?
Then the list on Zapier stops at eight triggers, two actions and one search. There is no step to close a request, delete one, update a contact or fetch the uploaded documents. Search File Requests can find an existing request, but not change it. For the missing part, a manual step in Pipefile is often the simplest fix, or another automation tool if it offers more Pipefile operations than Zapier does.
07Zapier, Make or n8n for Pipefile?
Compare them on what this app needs. On Zapier, Pipefile brings eight instant triggers, two actions and one search, works on the free plan for two-step Zaps, and bills only successful actions. That suits a team that wants alerts and new requests without much setup. If your Zaps will often need filters or searches, check how each platform bills multi-step runs, and whether Pipefile is offered there with the same events.
Same platform

Other docs you might need on this stack.

Browse all integrations