Overview
This node enables interaction with Pipefy cards, specifically allowing users to retrieve multiple cards from a specified pipe. The "Get Many" operation fetches a list of cards, optionally filtered by the pipe ID and limited in number.
Common scenarios include:
- Retrieving a batch of cards for reporting or analysis.
- Synchronizing card data from Pipefy into another system.
- Displaying a list of cards within an automation workflow.
For example, you might use this node to get up to 50 cards from a particular pipe to process their statuses or extract key information for further automation steps.
Properties
| Name | Meaning |
|---|---|
| Pipe ID | ID of the pipe to get cards from. If left empty, cards from all pipes may be returned. |
| Limit | Maximum number of cards to return. Accepts values from 1 to 50. Defaults to 50. |
Output
The output is an array of card objects under the json field. Each object represents a Pipefy card with its properties as returned by the Pipefy API. Typical fields include card identifiers, titles, phases, labels, assignees, due dates, and custom field values.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with Pipefy.
- Requires an additional API key credential for the n8n Tools API (used internally).
- The node uses internal utility functions to format dates and validate required fields.
- Proper configuration of these credentials in n8n is necessary for successful execution.
Troubleshooting
- Missing Pipe ID: If no Pipe ID is provided, the node may return cards from all pipes or none depending on API behavior. To avoid unexpected results, specify the Pipe ID.
- Limit Exceeded: Setting the limit above 50 will be rejected; ensure the limit is between 1 and 50.
- API Errors: Common errors include authentication failures or invalid Pipe IDs. Verify that API keys are valid and that the Pipe ID exists.
- Empty Results: If no cards are returned, check if the pipe contains cards or if filters applied exclude all cards.