PipefyInstall

Summary

Retrieve a Pipefy card by its ID. The operation always returns the card’s core details and can include related data or additional fields selected with a GraphQL fragment.

Inputs

• Authentication (required) — Choose Service Account (the default) or Personal Access Token and provide the matching credentials.
• Card ID (required) — The card’s ID, available in its Pipefy URL.
• Include Asignees? — Defaults to false. When enabled, includes the card’s assignees.
• Include Attachments? — Defaults to false. When enabled, includes the card’s attachments.
• Include Comments? — Defaults to false. When enabled, includes the card’s comments and authors.
• Include Fields? — Defaults to false. When enabled, includes card field values and field metadata.
• Include Labels? — Defaults to false. When enabled, includes the card’s labels.
• Include Inbox Emails? — Defaults to false. When enabled, includes emails in the card inbox.
• Include Phases History? — Defaults to false. When enabled, includes the card’s phase history.
• Additional GraphQL Fields — Optional GraphQL selection fragment for extra fields on the Pipefy Card type. Enter the fragment only, without a query or card wrapper; the placeholder is pipe { name }.

Output shape

A single item whose json contains the card object.

Always requests core fields such as ID, title, creation and update times, current phase, due date, status indicators, URL, and creator. Enabled options add their corresponding nested data; the additional GraphQL fragment is inserted into the card selection.

Examples

Example 1: Retrieve a card with its fields and labels

Provide the card ID and enable Include Fields? and Include Labels?; leave other optional sections off unless needed.

Links

• n8n community nodes installation guide