Overview
This node enables creating a new card in Pipefy, a workflow and process management platform. It is useful for automating task or issue creation within specific pipes and phases of your Pipefy workspace. For example, you can automatically create a card when a form is submitted, a new customer request arrives, or an event triggers a workflow.
The "Create Card" operation allows specifying the pipe and optionally the phase where the card should be created, along with additional details such as title, due date, assignees, labels, and custom field values.
Properties
| Name | Meaning |
|---|---|
| Pipe ID | ID of the pipe where the card will be created (required). |
| Card Title | Title of the card to be created. |
| Phase ID | ID of the phase where the card will be created. If not provided, the card goes to the first phase. |
| Additional Fields | Collection of optional fields: |
| - Due Date | Due date for the card (date-time). |
| - Assignee IDs | Comma-separated list of user IDs to assign to the card. |
| - Label IDs | Comma-separated list of label IDs to apply to the card. |
| - Field Values | Custom field values for the card. Multiple entries allowed, each with: |
| -- Field ID | ID of the custom field. |
| -- Value | Value to set for the custom field. |
Output
The output JSON contains the newly created card object returned by the Pipefy API. This includes all standard card properties such as its ID, title, current phase, assigned users, labels, due date, and any custom fields set during creation.
No binary data is output by this node.
Dependencies
- Requires valid API credentials for Pipefy configured in n8n.
- Uses Pipefy's GraphQL API to perform card creation.
- The node depends on utility functions for formatting dates and validating required fields.
Troubleshooting
- Missing Required Fields: If "Pipe ID" or other required parameters are missing, the node throws an error indicating which field is required. Ensure all mandatory inputs are provided.
- Invalid IDs: Providing invalid pipe, phase, or user IDs may cause API errors. Verify IDs exist in your Pipefy workspace.
- Date Format Issues: The due date must be in a valid date-time format; otherwise, the API may reject it.
- API Authentication Errors: Ensure that the API key credential is correctly set up and has sufficient permissions.
- Comma-Separated Lists: Assignee and label IDs must be comma-separated strings without extra spaces; improper formatting may cause assignment failures.