Actions17
- Attachment Actions
- Card Actions
- Pipe Actions
- User Actions
- Webhook Actions
Overview
This node integrates with the Pipefy GraphQL API to perform various operations on Pipefy resources. Specifically, for the Card resource with the Get Many operation, it retrieves multiple cards from Pipefy based on configured parameters. This is useful when you want to fetch a list of cards for reporting, automation, or synchronization purposes.
Common scenarios include:
- Extracting all cards from a specific pipe or phase.
- Aggregating card data for dashboards or analytics.
- Automating workflows that require bulk processing of cards.
Example: Fetching all cards assigned to a user or within a particular pipe to trigger follow-up actions or notifications.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Pipefy API. Options: - Service Account - Personal Access Token |
Note: The provided properties JSON only includes the Authentication property. Other properties related to filtering or pagination for "Get Many" cards are defined elsewhere in the bundled dependencies but are not explicitly listed here.
Output
The node outputs an array of JSON objects representing the cards retrieved from Pipefy. Each object corresponds to a single card and contains its fields as returned by the Pipefy GraphQL API. The exact structure depends on the query executed internally but typically includes card ID, title, status, assignees, and other metadata.
No binary data output is indicated.
Dependencies
- Requires access to the Pipefy GraphQL API.
- Requires either a service account credential or a personal access token credential for authentication.
- No additional external services or environment variables are explicitly required beyond these credentials.
Troubleshooting
- Authentication errors: Ensure the selected authentication method is correctly configured with valid credentials.
- API rate limits: If many cards are requested, the API may throttle requests; consider implementing pagination or reducing batch size.
- Empty results: Verify that filters or parameters (not shown here) are set correctly to match existing cards.
- Network issues: Confirm network connectivity to Pipefy API endpoints.