Productivity · Integration
Pipefy
Add Pipefy to your product for your customers, and give your AI agents governed access to it.
Embed a Pipefy integration so your customers can run their own processes from inside your product instead of retyping work into another tool. Pipefy models work as pipes made of phases, with cards moving through them and form fields captured at each step, plus database tables for the reference data a process needs. Every team configures its own pipes, fields and phases, so mapping is configuration per customer rather than code. fastn handles per-customer authorisation, token refresh, rate limits and API upkeep, so a customer with an unusual Pipefy setup works without a release from you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Pipefy account so an event in your product creates a card in the right pipe.
Move a card to the next phase and fill its fields from your product so the process reflects what happened.
Read cards, phases and database records so your product can show where a request sits.
Trigger your workflow when a card is created or changes phase, rather than polling for it.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent creates a card with the right fields and phase within governed permissions.
An agent reads the cards in a phase before summarising what is stuck.
An agent comments on or advances a card, with every action attributed and audited.
Example prompt
List cards that have sat in the same phase for over a week and show who they are assigned to.
Set up Pipefy in 4 steps
- 01Open the Pipefy connector from your fastn dashboard.
- 02Have each customer authorise their own Pipefy account.
- 03Map the pipes, phases, fields and database tables your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Pipefy integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Pipefy integration without building it. Your customers connect their own Pipefy account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
- Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Pipefy update is not your on-call problem.
- One integration serves your product and your agents. The same governed Pipefy connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.
Used by these teams
Compare with
monday.com
AsanaWorks well with
Process StreetOften used alongside
Tools the same teams tend to run next to Pipefy, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServicePipefy integration FAQ
How do I add a Pipefy integration to my product?
Enable the Pipefy connector in your fastn dashboard, then let each customer authenticate their own Pipefy account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Pipefy client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Pipefy account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Pipefy account and only ever sees their own work items, assignees and due dates. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Pipefy integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent creates a card with the right fields and phase within governed permissions.
Who maintains the Pipefy integration?
fastn does. When Pipefy changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create and update work in Pipefy automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Pipefy can trigger your workflows in return.
Does it adapt to each team's own Pipefy setup?
Yes. However a team has configured Pipefy, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.
What can I build with the Pipefy integration?
A common starting point: connect their own Pipefy account so an event in your product creates a card in the right pipe. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Pipefy integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Pipefy does not change your per-connector cost. You can start free with 3 connected accounts.
Add Pipefy to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.