Pipefy icon

Pipefy

Interact with Pipefy GraphQL API
Join our community

Actions17

Overview

This node integrates with the Pipefy platform to update fields of a specific card within a pipe phase. It allows users to modify card data dynamically by replacing, adding to, or removing values from the card's fields. This is particularly useful for automating workflows where card information needs to be updated based on external triggers or processes, such as updating task statuses, adding attachments, or modifying assignees.

Practical examples include:

  • Automatically moving a card to a new phase and updating its fields when a related event occurs.
  • Adding labels or checklist items to a card as part of an automated review process.
  • Removing outdated attachments or connections from a card during cleanup operations.

Properties

Name Meaning
Authentication Method of authenticating with Pipefy: either using a Service Account or a Personal Access Token.
Card ID The unique identifier of the card to update. This ID can be found in the card's URL on Pipefy (e.g., https://app.pipefy.com/open-cards/[ID]).
Phase Name or ID The target phase within the pipe where the card will be moved. Users can select from a list of phases or specify an ID via expression.
Update Operation Defines how the field values will be updated:
- Replace: Overwrite existing value with the new one.
- Add: Append values to existing lists (for fields like Attachments, Assignees, Labels, Connections, Checklists).
- Remove: Remove values from existing lists (compatible with list-type fields).
Fields The set of fields to update on the card. Supports defining individual fields or mapping multiple fields at once. The available fields depend on the selected phase and update operation.

Output

The node outputs an array of JSON objects representing the updated card(s). Each object contains the card's data after applying the specified field updates. The exact structure corresponds to Pipefy's card schema, including updated field values and metadata.

If binary data is involved (e.g., attachments), it would be handled accordingly, but this node primarily focuses on JSON data representing card fields.

Dependencies

  • Requires access to the Pipefy GraphQL API.
  • Needs authentication credentials, either a service account or a personal access token.
  • The node depends on dynamic loading of pipe phases and fields, which requires network connectivity to Pipefy.
  • No additional environment variables are explicitly required beyond the provided credentials.

Troubleshooting

  • Invalid Card ID: If the card ID is incorrect or does not exist, the node will fail to update fields. Verify the card ID from the Pipefy UI URL.
  • Phase ID Not Found: Selecting a phase that does not belong to the pipe or is invalid will cause errors. Ensure the phase ID corresponds to the card's pipe.
  • Field Type Mismatch: Trying to add or remove values on fields that do not support list operations may result in errors. Use "Replace" for single-value fields.
  • Authentication Errors: Incorrect or expired credentials will prevent API access. Re-authenticate or update credentials as needed.
  • API Rate Limits: Frequent updates might hit Pipefy API rate limits; consider adding delays or batching updates.

Links and References

Discussion