Pipefy icon

Pipefy

Interact with Pipefy GraphQL API
Join our community

Actions17

Overview

This node interacts with the Pipefy GraphQL API to update fields of a specific card within a Pipefy pipe. It allows users to specify the card by its ID, select the phase to move the card to, and update the card's fields with different operations such as replacing existing values, adding to lists, or removing from lists. This is useful for automating workflow updates, managing card data dynamically, and integrating Pipefy with other systems.

Use Case Examples

  1. Automatically update card fields when a new form submission is received.
  2. Move a card to a different phase and update its fields based on external triggers.
  3. Add or remove labels, attachments, or assignees to a card programmatically.

Properties

Name Meaning
Authentication Select the authentication method to use for API access, either Service Account or Personal Access Token.
Card ID The unique identifier of the card to update. This is required and can be found in the card's URL.
Phase Name or ID The ID of the phase to which the card should be moved. This is required and can be selected from a list or specified via expression.
Update Operation Defines how the field values will be updated: replace existing values, add to lists, or remove from lists. This is required and depends on the phase being specified.
Fields The fields of the card to update. Supports adding, replacing, or removing values depending on the update operation. This is required and dynamically loads fields based on the selected phase and update operation.

Output

JSON

  • id - The unique identifier of the updated card.
  • fields - The updated fields of the card with their new values.
  • phaseId - The ID of the phase to which the card was moved.

Dependencies

  • Pipefy GraphQL API

Troubleshooting

  • Ensure the Card ID is correct and accessible with the provided authentication method.
  • Verify that the Phase ID exists and is valid for the card's pipe.
  • Check that the update operation is compatible with the field types being updated (e.g., add/remove operations only work with list-type fields).
  • Authentication errors may occur if the API key or token is invalid or expired; re-authenticate or update credentials as needed.

Discussion