Pipefy icon

Pipefy

Interact with Pipefy GraphQL API
Join our community

Actions17

Overview

This node updates a card in Pipefy, a workflow and process management platform. It allows users to modify key attributes of an existing card such as its title, due date, labels, and assignees. This is useful for automating updates to tasks or items tracked in Pipefy based on external triggers or workflows.

Common scenarios include:

  • Automatically updating the due date or title of a card when related data changes.
  • Reassigning cards to different team members programmatically.
  • Clearing or changing labels on cards to reflect status changes or categorization.

For example, you could use this node to update a card’s due date when a related calendar event is rescheduled, or to clear all labels and assign new ones based on a form submission.

Properties

Name Meaning
Authentication Choose between authenticating with a Service Account or a Personal Access Token.
Card ID The unique identifier of the card to update. Found in the card's URL (e.g., https://app.pipefy.com/open-cards/[ID]). Required.
Title The new title to set for the card.
Due Date The new due date for the card, specified as a date-time value.
Additional Fields A collection of optional fields to update:
- Label Names or IDs List of labels to replace on the card. Can be selected from a list or specified by expression.
- Assignee Names or IDs List of assignees to replace on the card. Can be selected from a list or specified by expression.
- Clear Labels Boolean flag to clear all labels from the card if enabled. Hidden if specific labels are provided.
- Clear Assignees Boolean flag to clear all assignees from the card if enabled. Hidden if specific assignees are provided.

Output

The node outputs a JSON array where each element corresponds to the updated card data returned from Pipefy after the update operation. The exact structure depends on the Pipefy API response but typically includes the card's updated fields such as ID, title, due date, labels, and assignees.

If the node supports binary data output, it is not indicated here; thus, only JSON output is expected.

Dependencies

  • Requires authentication via either a Service Account credential or a Personal Access Token credential configured in n8n.
  • Depends on access to the Pipefy GraphQL API.
  • The node uses dynamic loading methods to fetch available labels and assignees for the specified card to assist user selection.

Troubleshooting

  • Invalid Card ID: If the card ID is incorrect or does not exist, the API will return an error. Verify the card ID from the Pipefy UI URL.
  • Authentication Errors: Ensure that the chosen authentication method is correctly configured with valid credentials.
  • Permission Issues: The authenticated user or service account must have permission to update the specified card.
  • Clearing vs. Setting Labels/Assignees: If both clearing flags and specific labels/assignees are set simultaneously, the node hides the clearing options to avoid conflicts. Make sure to configure these fields properly.
  • API Rate Limits: Frequent updates may hit Pipefy API rate limits; consider adding delays or error handling for retries.

Links and References

Discussion