Actions17
- Attachment Actions
- Card Actions
- Pipe Actions
- User Actions
- Webhook Actions
Overview
This node integrates with the Pipefy platform to create webhooks within a specified Pipe (a workflow container in Pipefy). Specifically, the "Create Pipe Webhook" operation allows users to register a webhook URL that Pipefy will call when certain events occur on cards within the selected Pipe. This is useful for automating workflows by triggering external processes or notifications based on Pipefy activity.
Common scenarios include:
- Automatically syncing Pipefy card updates with other systems.
- Triggering notifications or alerts when specific card events happen.
- Logging or auditing card changes externally.
- Integrating Pipefy with custom applications via real-time event handling.
For example, you could create a webhook that triggers whenever a new card is created or a comment is added, sending this data to an external CRM or messaging system.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Pipefy API: either using a Service Account or a Personal Access Token. |
| Name | The name to assign to the webhook being created. |
| URL | The callback URL where Pipefy will send webhook requests. Must be a valid URL. |
| Pipe Name or ID | The target Pipe in which to create the webhook. Can be selected from a list or specified via expression. |
| Events | List of Pipefy card events that will trigger the webhook. Options include: card.comment_create, card.create, card.delete, card.done, card.email_received, card.expired, card.field_update, card.late, card.move, card.overdue. |
| Authorization Token | A secret token sent in the X-Pipefy-Signature header with each webhook request for verification purposes. Recommended to use a random string for security. |
| Additional Fields | Optional extra settings including: - Notification Email: email address to receive webhook notifications. - Custom Headers: JSON object defining additional headers sent with webhook requests. - Filters: JSON filters to limit webhook triggers (note Pipefy API limitation: only first event used if filters set). |
Output
The node outputs an array of JSON objects representing the created webhook(s) as returned by the Pipefy API. Each object typically contains details such as webhook ID, name, URL, subscribed events, and configuration metadata.
If the webhook creation fails, the output will contain error information.
The node does not output binary data.
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.
- The node uses dynamic loading of Pipe options (pipes list) via an internal method.
- No additional external dependencies beyond standard HTTP and authentication mechanisms.
Troubleshooting
- Invalid URL: If the provided webhook URL is not valid or reachable, the API may reject the creation request. Ensure the URL is correct and publicly accessible.
- Authentication errors: Using incorrect or expired credentials will cause authorization failures. Verify that the API key or token is valid and has necessary permissions.
- Event selection issues: Selecting no events or invalid events will cause errors. At least one valid event must be selected.
- Filters limitation: When filters are set, only the first configured event is used due to Pipefy API limitations. Users should consult Pipefy docs to understand filter constraints.
- Authorization token missing or weak: Not providing a strong authorization token can lead to security risks. Use a secure random string as recommended.
- API rate limits or downtime: Temporary API unavailability or rate limiting can cause failures; retry later or check Pipefy status.