Pipefy icon

Pipefy

Interact with Pipefy GraphQL API
Join our community

Actions17

Overview

This node interacts with the Pipefy GraphQL API to retrieve detailed information about a specific card within Pipefy. It is useful for scenarios where you need to fetch comprehensive data about a card, including optional related data such as assignees, attachments, comments, fields, labels, inbox emails, and phases history. For example, it can be used to automate workflows that require card details for reporting, notifications, or further processing in other systems.

Use Case Examples

  1. Fetching a card's details along with its assignees and attachments to display in a custom dashboard.
  2. Retrieving card comments and labels to analyze team communication and task categorization.
  3. Getting the phases history of a card to track its progress through different stages.

Properties

Name Meaning
Authentication Selects the authentication method to access the Pipefy API, either via a service account or a personal access token.
Card ID The unique identifier of the card to retrieve, found in the card's URL in Pipefy.
Include Assignees? Whether to include the assignees of the card in the response.
Include Attachments? Whether to include the attachments of the card in the response.
Include Comments? Whether to include the comments of the card in the response.
Include Fields? Whether to include the fields of the card in the response.
Include Labels? Whether to include the labels of the card in the response.
Include Inbox Emails? Whether to include the emails in the card's inbox in the response.
Include Phases History? Whether to include the phases history of the card in the response.

Output

JSON

  • id - The unique identifier of the card.
  • title - The title or name of the card.
  • assignees - List of users assigned to the card, if requested.
  • attachments - List of attachments associated with the card, if requested.
  • comments - List of comments made on the card, if requested.
  • fields - Custom fields and their values on the card, if requested.
  • labels - Labels or tags assigned to the card, if requested.
  • inboxEmails - Emails received in the card's inbox, if requested.
  • phasesHistory - History of the card's movement through different phases, if requested.

Dependencies

  • Pipefy GraphQL API

Troubleshooting

  • Ensure the Card ID is correct and accessible with the provided authentication method.
  • Verify that the selected authentication method (service account or personal token) has the necessary permissions to access card data.
  • If optional data like assignees or attachments are not returned, check that the corresponding boolean flags are enabled.
  • Common errors may include authentication failures, invalid Card ID, or insufficient permissions. Resolving these typically involves verifying credentials and input parameters.

Links

Discussion