Overview
Version v0.2.0 of the Pipefy Connector brings modular return to the search and lookup actions for both cards and records. You now decide, field by field, what each action brings back. Smaller payloads, faster runs, and cleaner downstream steps in your flow.
What's new?
- Return-field selection for cards, available in Get card by id, Get cards by field value, Get cards by phase, and Get cards by title. The sections you can check or uncheck are: Card Information, Phases History, Attachments, Comments, Inbox Emails, Assignees, Created By, Parent Relations, and Child Relations. The `id`, `fields`, and `pipe` fields are always returned.
- Return-field selection for records, available in Get record by id and Get records by filter. The available sections are: Record Information, Status, Assignees, Parent Relations, and Created By. The `id`, `fields`, and `database` fields are always returned.
Across every action, each section is selected by default. Uncheck what you don't need, or clear a whole section, to trim the response. If you don't touch anything, you keep getting the full payload.
How does this help?
- Faster, lighter flows: by returning only the fields your next step uses, the payload shrinks and the run consumes less memory, a real difference in large flows running close to their memory and time limits.
- Cleaner downstream steps: with less irrelevant data moving through, field mapping in later actions becomes more direct and easier to maintain.
- Field-by-field control: you set the scope of each query independently, instead of treating every lookup action the same way.
Use cases
Syncing cards to an external data warehouse
A nightly flow uses Get cards by phase to export cards from the billing phase into an external BI tool. Every card used to carry phase history, comments, and inbox emails that the destination never consumed. By checking only Card Information and Assignees, the flow now moves a fraction of the volume, runs within the nightly window without hitting the time limit, and delivers exactly the schema the BI expects, with no cleanup step afterward.
Most relevant for
- Builders working with integrations in Pipefy Integrations
- Operations teams maintaining high-volume flows
- Pipe Admins responsible for data syncing
- Data and BI teams consuming cards and records from Pipefy
Plans and availability
This update is not applied automatically and is optional. To get the changes, update the connector version manually by following the step-by-step in the video included with this post. After updating, you will need to reconnect your Service Account, your organization, and your Pipe. When you update an existing step to this version, the fields you had already filled in will be cleared and will need to be filled in again.
