Actions32
- Card Actions
- Organization Actions
- Pipe Actions
- Phase Actions
- Table Actions
- Table Record Actions
- User Actions
- Webhook Actions
Overview
This node interacts with the Pipefy API to update an existing card within a Pipefy pipe. It allows users to modify the card's title and update multiple fields on the card, including various field types such as text, checklist, attachments, labels, dates, and more.
Common scenarios where this node is beneficial include:
- Automating updates to task or project cards in Pipefy based on external triggers or data changes.
- Synchronizing card information from other systems by updating specific fields programmatically.
- Bulk updating cards with new information without manual intervention.
For example, you could use this node to update the status of a card, assign it to a different user, add attachments, or change due dates automatically when certain conditions are met in your workflow.
Properties
| Name | Meaning |
|---|---|
| Card ID | The unique identifier of the card to update. This is required to specify which card will be modified. |
| Fields | A collection of fields to set on the card. Each field includes: - Field ID: Identifier of the field to update. - Field Type: Type of the field; options include Assignee, Attachment, Checklist, Cnpj, Connection, Currency, Date, DateTime, Due Date, Email, ID, Label, Long Text, Number, Phone, Radio, Select, Short Text, Statement, Time. - Value: The value to set for the field (string). - Array Values: For checklist or label fields, comma-separated values can be provided. - Attachments: For attachment fields, one or more attachments can be specified, each with a URL and filename. |
Output
The node outputs JSON data representing the updated card object returned by the Pipefy API. The structure includes:
id: The card's unique identifier.title: The updated title of the card.current_phase: Object containing the current phase name of the card.fields: Array of fields on the card, each with:name: Field name.value: Value of the field.array_value: Array values if applicable (e.g., for checklist or label).field: Object withidandtype.
updated_at: Timestamp of the last update.
If the card contains attachments, these are included within the fields array under the appropriate field type.
Dependencies
- Requires an active Pipefy API key credential configured in n8n to authenticate requests.
- Uses the Pipefy GraphQL API endpoint (
https://api.pipefy.com/graphql). - The node sends GraphQL mutations to update card data.
Troubleshooting
- Invalid Card ID: If the provided Card ID does not exist or is incorrect, the API will return an error. Verify the Card ID is correct.
- Field ID Mismatch: Providing invalid or non-existent Field IDs will cause errors. Ensure all Field IDs correspond to fields on the target card.
- Incorrect Field Types or Values: Setting values incompatible with the field type (e.g., string for a date field) may result in API errors. Match field types and values correctly.
- Attachment Errors: When adding attachments, ensure URLs are accessible and filenames are provided. Missing these will cause failures.
- API Rate Limits: Frequent updates may hit Pipefy API rate limits. Implement error handling and retries as needed.
- Authentication Issues: Ensure the API key credential is valid and has sufficient permissions to update cards.