Pipefy icon

Pipefy

Interact with Pipefy GraphQL API
Join our community

Actions17

Overview

This node integrates with the Pipefy platform via its GraphQL API to create new cards within a specified pipe of an organization. It is useful for automating workflows where new tasks, requests, or items need to be programmatically added to Pipefy pipes based on external triggers or data inputs.

Typical use cases include:

  • Automatically creating a new card in Pipefy when a form is submitted.
  • Adding tasks to a project management pipe from another system.
  • Integrating customer support tickets into Pipefy as cards for tracking.

Properties

Name Meaning
Authentication Method used to authenticate with Pipefy: either "Service Account" or "Personal Access Token".
Org Name or ID The identifier of the Pipefy organization where the pipe exists. Can be selected from a list or provided by expression.
Pipe Name or ID The identifier of the pipe within the organization where the card will be created. Selectable or set by expression.
Title The title of the new card to be created in the pipe.
Fields Additional fields to populate on the new card. This uses a resource mapper to define field values dynamically based on the pipe's start form fields.

Output

The node outputs an array of JSON objects representing the newly created cards. Each object contains the details of the created card as returned by the Pipefy API, including at least the card's ID and any other relevant metadata.

No binary data output is produced by this node.

Dependencies

  • Requires access to the Pipefy GraphQL API.
  • Requires authentication credentials, either a service account or a personal access token.
  • The node depends on dynamic loading of organizations, pipes, and pipe fields via internal methods to populate dropdowns and map fields correctly.
  • No additional external dependencies beyond the Pipefy API and n8n environment are needed.

Troubleshooting

  • Authentication errors: Ensure that the provided API key or service account credentials are valid and have sufficient permissions to create cards in the target organization and pipe.
  • Invalid Org or Pipe IDs: Selecting or specifying incorrect organization or pipe IDs will cause failures. Use the dropdowns or verify IDs carefully.
  • Missing required fields: The "Title" and "Fields" properties are mandatory. Omitting them or providing invalid field mappings can cause errors.
  • Field mapping issues: If no fields are found for the selected pipe, the node will error out. Verify that the pipe has a start form configured.
  • API rate limits or network issues: Temporary failures may occur due to API limits or connectivity problems; retrying may help.

Links and References

Discussion