Overview
We've upgraded the automations engine behind Pipefy Integrations. Most of the work happens behind the scenes, but it translates into more reliable flows, clearer error messages, better performance, and a more up to date set of connectors.
What's new?
- Clearer action labels: actions now show whether they read, search, write, or delete data, with delete actions highlighted in red.
- Cleaner step forms for HTTP Request, Google Sheets, and Custom API Call.
- Automations are sorted alphabetically, with friendly messages instead of blank screens when something fails to load.
- Over 270 updated connectors, including QuickBooks Desktop, HubSpot Private App token, and a new Google Drive trigger.
- Subflows scheduled for retry no longer cause the parent flow to fail.
- OAuth2 connections with special characters can now be saved correctly.
- Publishing a scheduled flow no longer breaks its schedule.
- Older flows and templates can be imported without errors.
- Large flows run faster and lighter.
- Newly installed connectors no longer fail with a "piece not found" error.
- Error messages now point to the actual cause instead of a generic error.
- Members can no longer access connections from other projects.
- Synchronous webhooks now return 500, instead of 200, when a flow fails. If any system relies on that response, it's worth reviewing that integration.
- HTTP headers are preserved exactly as entered, with no automatic conversion to lowercase.
- The Kimai connector now uses Bearer token authentication. If you already use Kimai, you'll need to reconnect.
How does this help?
- Less risk of running the wrong automation: actions that read, search, write, or delete data are clearly labeled before you build the flow.
- Faster setup: cleaner forms for HTTP Request, Google Sheets, and Custom API Call cut down the time it takes to build new flows.
- Less time hunting for automations: alphabetical sorting removes the manual search through long flow lists.
- Fewer interruptions in critical flows: retry subflows, importing older flows, and publishing scheduled flows now work without unexpected failures.
- Faster troubleshooting: error messages point to the real cause, cutting the time it takes to fix issues.
- More security across teams: connections are no longer visible to members from other projects.
- A wider integrations ecosystem: connectors like QuickBooks Desktop and HubSpot expand what you can automate without leaving Pipefy.
Use cases
1. Finance Pipe Admin syncing reimbursements with QuickBooks Desktop
A Finance team Pipe Admin maintains a flow that updates reimbursement status in QuickBooks Desktop whenever a card changes phase. With the updated QuickBooks Desktop connector, the flow no longer fails with a "piece not found" error and reflects invoice status in real time, so the team no longer has to manually check every entry in the financial system.
2. IT Builder monitoring synchronous webhook failures
An IT team Builder uses a synchronous webhook to trigger a legacy system whenever a card is created. Since the webhook now returns 500 instead of 200 when the flow fails, the IT team catches connection failures the moment they happen, instead of assuming the call succeeded and finding out about the issue days later.
3. Admin reviewing dozens of automations for a company
A flow admin reviews automations for a company with multiple active projects. With the list sorted alphabetically and friendly messages instead of blank screens when something fails to load, they find and fix the problem automation in minutes, without opening a support ticket.
4. Sales team connecting HubSpot with a Private App token
A Sales team connects HubSpot to Pipefy using the new Private App token, without relying on an individual integrator's personal account. Since connections are now isolated per project, the Sales team makes sure only the right people can access that integration, even on accounts with several active projects.
5. Pipe Admin reusing an older flow template
A Pipe Admin imports a flow template created before the upgrade to reuse it in a new process. Without the error that used to block importing older flows and templates, they reuse the existing logic directly instead of rebuilding it from scratch.
Most relevant for
- Builders
- Pipe Admins
- Operations teams
- IT Leaders
- HubSpot, QuickBooks Desktop, and Kimai users
