Actions17
- Attachment Actions
- Card Actions
- Pipe Actions
- User Actions
- Webhook Actions
Overview
This node integrates with the Pipefy GraphQL API, enabling users to interact programmatically with various Pipefy resources such as attachments, cards, pipes, users, and webhooks. It is designed to facilitate automation workflows involving Pipefy by allowing operations like creating, updating, or retrieving data from these resources.
Common scenarios where this node is beneficial include:
- Automating task and project management by manipulating Pipefy cards and pipes.
- Managing user information within Pipefy.
- Handling file attachments related to Pipefy cards.
- Setting up or managing webhooks for event-driven workflows.
For example, a user could automate the creation of new cards in a specific pipe when a form is submitted, or update card statuses based on external triggers.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Pipefy API. Options: "Service Account" or "Personal Access Token". |
Note: Although the node supports multiple resources and operations, only the "Authentication" property is relevant here as per the provided input.
Output
The node outputs an array of JSON objects representing the results of the executed operations against the Pipefy API. Each item corresponds to the processed input item and contains the data returned by the API call.
If the operation involves binary data (e.g., attachments), the output would include binary fields representing that data, but this is not explicitly detailed in the provided code snippet.
Dependencies
- Requires access to the Pipefy GraphQL API.
- Needs either a service account credential or a personal access token for authentication.
- The node depends on internal modules handling resource-specific actions and routing logic to map inputs to API calls.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials.
- API rate limits or permission issues: Verify that the API key or token has sufficient permissions and that usage limits are not exceeded.
- Invalid input data: Confirm that input data matches expected formats for the chosen resource and operation.
- Network connectivity problems: Check internet connection and Pipefy API availability.
Error messages typically relate to authentication failures, invalid queries, or network timeouts. Resolving them usually involves verifying credentials, input correctness, and network status.