Actions17
- Attachment Actions
- Card Actions
- Pipe Actions
- User Actions
- Webhook Actions
Overview
This node allows updating a card in Pipefy, a workflow and process management platform. It is useful when you want to programmatically modify details of an existing card such as its title, due date, labels, and assignees. Common scenarios include automating task updates based on external triggers, synchronizing data between systems, or bulk editing cards without manual intervention.
For example, you could use this node to:
- Change the title of a card when a related event occurs.
- Set or update the due date of a task card automatically.
- Replace or clear labels and assignees on a card to reflect new statuses or ownership.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose the authentication method: "Service Account" or "Personal Access Token". |
| Card ID | The unique 10-character ID of the card to update (found in the card's URL). |
| Title | The new title to assign to the card. |
| Due Date | The new due date for the card (date and time). |
| Additional Fields | A collection of optional fields to update: |
| - Label Names or IDs | List of labels to replace on the card (can select from list or specify IDs via expression). |
| - Assignee Names or IDs | List of assignees to replace on the card (select or specify IDs). |
| - Clear Labels | Boolean flag to clear all labels from the card (enabled by default if no labels specified). |
| - Clear Assignees | Boolean flag to clear all assignees from the card (enabled by default if no assignees specified). |
Output
The node outputs a JSON array where each element corresponds to the updated card data returned from Pipefy after the update operation. This typically includes the card's current state with updated fields such as title, due date, labels, and assignees.
If the node supports binary data output, it is not indicated here; the primary output is structured JSON representing the card.
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 n8n’s internal methods for loading options dynamically (e.g., fetching available labels or members for the card).
- No additional environment variables are explicitly required beyond the configured credentials.
Troubleshooting
- Invalid Card ID: If the card ID is incorrect or does not exist, the API will fail to find the card. Ensure the card ID is exactly 10 characters and copied correctly from the URL.
- Authentication Errors: Using invalid or expired credentials will cause authentication failures. Verify that the API key or token is valid and has sufficient permissions.
- Labels or Assignees Not Updating: If labels or assignees do not change as expected, check whether the "Clear Labels" or "Clear Assignees" flags are set appropriately. These flags clear all entries unless specific replacements are provided.
- API Rate Limits: Frequent updates may hit Pipefy API rate limits. Implement error handling and retries as needed.
- Dynamic Options Loading Fails: If label or member lists fail to load, ensure the card ID is valid and the API connection is working.
Links and References
- Pipefy API Documentation
- Pipefy GraphQL API Guide
- n8n Expressions Documentation (for specifying dynamic values)