> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/api-reference/zapier.md). # Zapier Connect Pipefile to thousands of other apps through Zapier, without writing code. {% hint style="info" %} The Zapier integration is offered on the **Professional** and **Enterprise** plans, and during the free trial. {% endhint %} Zapier links Pipefile to other apps with automations called Zaps. A Zap starts when something happens in Pipefile, such as a request being completed, and then does something in another app: update a CRM record, post in a team chat, add a row to a spreadsheet or create a task. ## Connect Pipefile to Zapier {% stepper %} {% step %} ### Open Integrations Go to [**Settings** › **Integrations**](https://pipefile.com/dashboard/settings/integrations#zapier) and find the **Zapier** card. {% endstep %} {% step %} ### Click Connect to Zapier Click **Connect to Zapier**. Pipefile opens its Zapier page with ready-made Zaps for Pipefile. On a plan without the integration, the card shows **Upgrade to Professional** instead. {% endstep %} {% step %} ### Pick or build a Zap Choose a ready-made Zap, or start a new one. Zapier opens in a new tab and asks you to sign in to Zapier and connect your Pipefile account. {% endstep %} {% step %} ### Turn the Zap on Finish the Zap in Zapier, test it, and turn it on. {% endstep %} {% endstepper %} You can also start from Zapier's own Pipefile page: ## What can start a Zap Pipefile's Zapier triggers use the same events as [webhooks](/api-reference/webhooks.md). A Zap can start when: * a request is sent * a request link is opened * a reminder is sent * a file is uploaded * a checklist item is reviewed * every checklist item has a response * a request is marked complete * files are exported to cloud storage * a request expires Each trigger hands Zapier the request's details: its subject, status, tags, recipients with their names, emails and personal request links, and the checklist with each item's status. Zapier lists the exact triggers and actions available for Pipefile when you build the Zap. ## Whose requests start your Zaps Your Zaps run for requests you own. They also run for a teammate's request when your team uses a shared inbox, when you are a team admin, or when the request is assigned to you. ## Good to know * Zaps receive request details, not the uploaded files. To move files into a folder automatically, use [cloud storage auto-export](https://app.gitbook.com/s/5FaOvSTk88hXbQhqEN0A/reviewing-and-exporting/cloud-storage-and-auto-export). * To build the same automations in your own code, use [webhooks](/api-reference/webhooks.md) and the API.
My Zap didn't run Check that the Zap is turned on in Zapier, and that the request it should have run for is yours, assigned to you, or visible to you through a shared inbox or as a team admin. Zapier's Zap history shows each run and any error. If Pipefile looks like the cause, email with the Zap name and the request's subject.
## Related * [Webhooks](/api-reference/webhooks.md) * [Cloud storage integrations and auto-export](https://app.gitbook.com/s/5FaOvSTk88hXbQhqEN0A/reviewing-and-exporting/cloud-storage-and-auto-export) * [Plans and features](https://app.gitbook.com/s/5FaOvSTk88hXbQhqEN0A/getting-started/plans-and-features) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://support.pipefile.com/api-reference/zapier.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.