N8N Tools - Pipefy Card

Overview

This node allows you to interact with Pipefy cards by performing various operations such as creating, updating, retrieving, searching, moving between phases, and deleting cards. It is useful for automating workflows that involve managing tasks or items represented as cards in Pipefy pipes.

For the Get Card operation specifically, the node fetches detailed information about a single card using its unique ID. This is beneficial when you need to retrieve the current state or details of a specific card, for example, to display its data in another system, verify its status, or use its information in subsequent workflow steps.

Practical Example

• Retrieve a card’s details after it has been updated elsewhere to synchronize data.
• Fetch a card before deciding whether to move it to another phase or update its fields.
• Use the card data to trigger notifications or reports based on its properties.

Properties

Output

The output of the Get operation is a JSON object representing the full details of the requested Pipefy card. This includes all standard card fields such as title, phase, assignees, labels, due dates, custom field values, and other metadata associated with the card.

The node does not output binary data for this operation.

Example structure (simplified):

{
  "id": "string",
  "title": "string",
  "phase": {
    "id": "string",
    "name": "string"
  },
  "assignees": [
    {
      "id": "string",
      "name": "string"
    }
  ],
  "labels": [
    {
      "id": "string",
      "name": "string"
    }
  ],
  "dueDate": "ISO8601 date string",
  "fieldValues": [
    {
      "fieldId": "string",
      "value": "string"
    }
  ],
  ...
}

Dependencies

• Requires an API key credential for authenticating with Pipefy's API.
• Requires an additional API key credential for the n8n Tools API (likely used internally).
• The node uses internal utility functions to format dates and validate required fields.
• The Pipefy API must be accessible from the environment where n8n runs.

Troubleshooting

• Missing Card ID: If the Card ID parameter is empty or invalid, the node will throw an error indicating the Card ID is required. Ensure you provide a valid card ID.
• Card Not Found: If the specified card ID does not exist or is inaccessible due to permissions, the API may return an error or empty result. Verify the card ID and your API credentials have sufficient access.
• API Authentication Errors: Invalid or expired API keys will cause authentication failures. Check and refresh your credentials if needed.
• Network Issues: Connectivity problems to the Pipefy API endpoint can cause timeouts or errors. Confirm network access and retry.
• Rate Limits: Excessive requests might hit Pipefy API rate limits, resulting in errors. Implement retries or reduce request frequency.

Links and References

• Pipefy API Documentation
• n8n Documentation - Creating Custom Nodes
• Pipefy Cards Overview (example link)