Overview
This node integrates with the Pipefy API to create new cards within a specified Pipe (a workflow container in Pipefy). It is useful for automating task or issue creation workflows by programmatically adding cards with custom fields to a Pipefy pipe. For example, you can use this node to automatically create support tickets, sales leads, or project tasks based on incoming data from other systems.
Typical scenarios include:
- Creating a new card in a Pipefy pipe when a form is submitted.
- Automating card creation from CRM or email data.
- Adding cards with specific field values to track processes or requests.
Properties
| Name | Meaning |
|---|---|
| Pipe ID | Numeric ID of the Pipe where the card will be created (e.g., 301397126). |
| Title | The title of the card to be created. |
| Card Fields | A collection of custom fields to set on the card. Each field requires: |
| - Field ID: Identifier of the field in Pipefy (e.g., email, phone, nome). | |
| - Field Value: The value to assign to that field. |
Output
The node outputs JSON data representing the newly created card, including:
id: The unique identifier of the created card.title: The title of the card.url: A direct URL link to the card in Pipefy.
The output is an array of such objects, one per input item processed.
No binary data is produced by this node.
Dependencies
- Requires an API authentication token credential for Pipefy (an API key or OAuth token).
- Makes HTTP POST requests to the Pipefy GraphQL API endpoint at
https://api.pipefy.com/graphql. - The user must provide valid Pipe ID and have permission to create cards in that pipe.
Troubleshooting
Common issues:
- Invalid or missing Pipe ID: Ensure the Pipe ID is correct and numeric.
- Authentication errors: Verify the API token is valid and has sufficient permissions.
- Field IDs not matching Pipefy fields: Confirm that the field IDs correspond exactly to those defined in the Pipe.
- Network or API downtime: Check connectivity and Pipefy service status.
Error messages:
- Errors returned from the Pipefy API are surfaced as node operation errors with the message from the API.
- If the operation is not "create" for resource "card", an error stating the operation is not implemented will be thrown.
- To handle errors gracefully, enable "Continue On Fail" in the node settings.