Overview
Flows that depend on many manual conditions get harder to maintain as a process changes, and every new scenario means another rule to configure and review. This Pipefy Integrations update focuses on cutting that kind of manual work in the builder, adding authentication options aligned to corporate security standards, expanding the actions available in connectors you already use day to day, and fixing behaviors that caused data loss or slowdowns while building flows.
What's new?
- AI Router: a new routing option available in the step configuration. Instead of building a condition for every scenario, you write a single question and AI decides which branch of the flow to follow.
- Clearer configuration forms: labels, fields, and validation were revised across pieces such as Slack, Google Drive, Google Docs, Google Calendar, Airtable, Tables, PDF, File Helper, Math Helper, Discord, WordPress, Pinterest, Delay, and Manual Trigger.
- Slack for multiple users: you can now send the same message to several users in a single action, instead of duplicating the step for each recipient.
- New authentication options: Zendesk (OAuth2), Shopify (Dev Dashboard), Azure SQL (Entra ID), and Amazon Bedrock (temporary SSO/STS credentials).
- More connector actions: now available in HubSpot, Jira Cloud, Salesforce, Typeform, Calendly, Brevo, Trello, Google Contacts, Resend, and others.
- Continue on failure is back: this option is visible again on 37 helper actions.
- Bigger editor for long text: long text fields now have a larger editing area in the builder.
- Heads up on Airtable, Pinterest, and Trello: the configuration forms for these three pieces changed. Reopen flows that use them after the upgrade and confirm the settings are still correct.
- Zagomail discontinued: the connector was removed because the vendor shut down the service.
How does this help?
- Less manual work building flows: with AI Router, you write a question and AI decides the path, without creating and maintaining a condition for every possible scenario.
- Faster way to notify whole teams: sending one Slack message to several users removes the need to repeat the step for each person in the group.
- Authentication that matches corporate security standards: with OAuth2, Entra ID, and temporary SSO/STS credentials, IT teams connect systems without relying on static tokens stored inside the flow.
- A faster, more predictable builder: opening a step or testing an action no longer slows down as the flow grows, and a publish error now explains the reason instead of failing with no explanation.
- Safer Table editing: editing a cell or deleting a column no longer erases data from other columns in the same Table.
Use cases
Support team uses AI Router to direct tickets automatically
A support agent receives the customer's question as free text inside a triage flow and, instead of testing several manual conditions, uses AI Router so AI decides whether the case is about billing, account access, or a technical issue. Based on that decision the flow moves to the correct phase, applies the matching SLA, and assigns the responsible team, removing the manual reclassification step that used to depend on someone reading the ticket content.
Pipe Admin notifies several finance approvers at once through Slack
In an expense approval flow, the Slack step now sends the same message to every approver on the committee at the same time, instead of needing a separate step for each person. This ensures the whole group receives the request at the same moment, reducing the delay caused by approvers who used to be notified only at a later stage of the automation.
IT team connects corporate systems using modern authentication
When integrating an employee onboarding flow with Azure SQL, the IT team now authenticates through Entra ID instead of maintaining a connection string with fixed credentials. The same applies to Amazon Bedrock integrations, which now accept temporary SSO/STS credentials. This removes the need to store long lived secrets inside the flow and reduces the risk of an integration breaking when a token expires without warning.
Builder maintains a routing rules Table without fear of losing data
A flow that queries a Table to decide which service queue to use needs frequent adjustments as new business rules come up. Previously, editing a cell or deleting a column could erase data in other columns of the same Table; now those edits only affect the changed field, letting the builder adjust routing rules directly in the Table without recreating the content from scratch.
Builder reviews flows using Airtable, Pinterest, or Trello before the upgrade affects operations
Since these three pieces had changes to their configuration forms, a flow that automatically publishes content to Pinterest, for example, needs to be reopened after the upgrade to confirm the fields are still filled in correctly. This check prevents a production automation from silently breaking because a field changed format.
Most relevant for
- Automation builders
- IT and security teams
- Pipe Admins
- Operations teams
