Pipefy icon

Pipefy

Interact with Pipefy GraphQL API

Actions17

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 chosen 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 alerts or notifications 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 your CRM or messaging system.

Properties

Name Meaning
Authentication Choose the authentication method: either using a Service Account API credential or a Personal Access Token for Pipefy.
Name The name of the webhook to create.
URL The target URL where Pipefy will send webhook requests. Must be a valid URL.
Pipe Name or ID Select or specify the Pipe (workflow) where the webhook will be created. You can choose from a list or provide an expression resolving to a Pipe ID.
Events Select one or more card-related events that will trigger the webhook. Options include card creation, deletion, comments, field updates, and others related to card lifecycle.
Authorization Token A secret token sent in the X-Pipefy-Signature header with each webhook request for verification purposes. Recommended to use a strong random string.
Additional Fields Optional extra settings:
• Notification Email: email address to receive webhook notifications.
• Custom Headers: JSON object defining additional HTTP headers to send with each webhook request.
• Filters: JSON filters to limit events (note Pipefy API limitation: only first event used if filters set).

Output

The node outputs a JSON array containing the response from Pipefy's API after creating the webhook. This typically includes details about the newly created webhook such as its ID, URL, subscribed events, and configuration.

No binary data output is involved.

Dependencies

  • Requires access to the Pipefy GraphQL API.
  • Requires either a Service Account API credential or a Personal Access Token configured in n8n for authentication.
  • The node uses dynamic loading of available Pipes for selection.
  • The user must provide a valid webhook URL reachable by Pipefy.

Troubleshooting

  • Invalid URL error: Ensure the URL provided is a valid and publicly accessible HTTPS endpoint.
  • Authentication failures: Verify that the selected authentication method has correct credentials and permissions.
  • Event subscription issues: If filters are used, only the first event in the list will be applied due to Pipefy API limitations; check the documentation linked in the property hint.
  • Authorization token mismatch: If webhook requests fail signature verification, confirm the authorization token matches what is configured in Pipefy and the receiving endpoint.
  • API rate limits or network errors: Check connectivity and Pipefy API status.

Links and References

Discussion