Overview
This node allows you to search for cards within Pipefy pipes based on various criteria such as title, assignee, and label. It is useful when you want to filter and retrieve specific cards from a Pipefy pipe without fetching all cards manually.
Common scenarios include:
- Finding cards assigned to a particular user.
- Searching for cards with a specific label.
- Filtering cards by partial or full title match.
- Limiting the number of returned cards for performance or pagination purposes.
For example, you could use this node to find all cards in a sales pipeline assigned to a certain salesperson or to locate cards tagged with a priority label.
Properties
| Name | Meaning |
|---|---|
| Pipe ID | ID of the pipe to get cards from. |
| Limit | Maximum number of cards to return (1 to 50). |
| Search Title | Search cards by their title (partial or full match). |
| Assignee ID | Search cards assigned to a specific user by their user ID. |
| Label ID | Search cards that have a specific label applied by its label ID. |
Output
The output is an array of card objects matching the search criteria. Each card object contains detailed information about the card, including but not limited to its ID, title, current phase, assignees, labels, due dates, and custom field values.
The json output field holds these card objects. There is no binary data output for this operation.
Dependencies
- Requires an API key credential for authenticating with Pipefy's API.
- Requires an additional API key credential for the n8n Tools API (likely used internally).
- The node uses Pipefy GraphQL queries to perform the search operation.
- No special environment variables are needed beyond standard API credentials configured in n8n.
Troubleshooting
- Empty results: If no cards are returned, verify that the Pipe ID is correct and that the search criteria (title, assignee ID, label ID) actually match existing cards.
- Invalid Pipe ID or Card ID errors: These occur if the provided IDs do not exist or are malformed. Double-check the IDs.
- API authentication errors: Ensure that the API keys are valid and have sufficient permissions to access the Pipefy pipe and cards.
- Limit out of range: The limit must be between 1 and 50; setting it outside this range may cause errors.
- Network or timeout issues: Check your network connection and Pipefy service status if requests fail repeatedly.