Overview
This node allows you to update an existing card in Pipefy, a workflow and process management platform. It is useful when you want to modify details of a card such as its title, due date, assignees, labels, or custom fields after the card has been created.
Common scenarios include:
- Changing the title of a task or item represented by the card.
- Updating the due date to reflect new deadlines.
- Assigning or reassigning users responsible for the card.
- Adding or removing labels to categorize or prioritize the card.
- Modifying custom field values to capture additional information relevant to your workflow.
For example, if a task's deadline changes, you can use this node to update the card’s due date accordingly. Or if a task needs to be reassigned to different team members, you can update the assignee IDs.
Properties
| Name | Meaning |
|---|---|
| Card ID | The unique identifier of the card to update (required). |
| Card Title | The new title for the card. |
| Additional Fields | A collection of optional fields to update on the card: |
| - Due Date | The new due date for the card (date and 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. Each consists of a Field ID and the corresponding Value. |
Output
The output JSON contains the updated card object returned from Pipefy after the update operation. This includes all the card’s properties such as its ID, title, due date, assignees, labels, and custom fields reflecting the latest state.
No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with Pipefy.
- Requires a second API authentication token credential specific to the Pipefy service.
- Uses internal utility functions for formatting dates and making API requests to Pipefy’s GraphQL endpoints.
Troubleshooting
- Missing Required Fields: If the "Card ID" is not provided, the node will throw an error indicating that this required field is missing. Ensure you supply a valid card ID.
- Invalid Date Format: The due date must be in a valid date-time format; otherwise, the API request may fail.
- Incorrect User or Label IDs: Providing invalid or non-existent assignee or label IDs may cause the update to fail or have no effect.
- API Authentication Errors: Make sure the API credentials are correctly configured and have sufficient permissions to update cards.
- Network or API Errors: Temporary network issues or Pipefy API downtime can cause failures. Retrying later or checking Pipefy status may help.