Actions17
- Attachment Actions
- Card Actions
- Pipe Actions
- User Actions
- Webhook Actions
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 sources.
Typical use cases include:
- Automatically creating a new card in Pipefy when a form is submitted.
- Adding tasks to a project management pipe when an event occurs in another system.
- Integrating customer support tickets into Pipefy as cards for tracking and processing.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Pipefy: either using a Service Account or a 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 via expression. |
| Pipe Name or ID | The identifier of the pipe within the organization where the new card will be created. Selectable from a list or by expression. |
| Title | The title of the new card to be created in the specified pipe. |
| Fields | Additional fields to set on the new card. This uses a resource mapper to define values for 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, title, and any other fields that were set or returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires access to the Pipefy GraphQL API.
- Requires authentication credentials, either a service account credential or a personal access token credential configured in n8n.
- Uses dynamic loading of organizations and pipes for selection in the node UI, which depends on proper API access and permissions.
Troubleshooting
- Authentication errors: Ensure that the provided API key or service account has sufficient permissions to create cards in the target organization and pipe.
- Invalid Org or Pipe ID: If the organization or pipe cannot be found or accessed, verify that the IDs are correct and that the authenticated user has access rights.
- Missing required fields: The "Title" and "Fields" properties are mandatory; omitting them will cause errors.
- Field mapping issues: If the fields do not match the pipe’s start form fields, the API may reject the request. Use the resource mapper carefully to ensure field names and types align with the pipe configuration.
Links and References
- Pipefy API Documentation
- n8n Expressions Documentation (for using expressions in property values)