Pipefy icon

Pipefy

Interact with Pipefy GraphQL API
Join our community

Actions17

Overview

This node integrates with the Pipefy platform via its GraphQL API, specifically focusing on managing webhooks related to pipes. The "Get Pipe Webhooks" operation retrieves all webhooks configured for a specified pipe in Pipefy. This is useful for scenarios where you want to monitor or manage event-driven integrations tied to a particular pipe, such as triggering workflows when cards are moved or updated.

Practical examples include:

  • Automatically syncing Pipefy events with other systems by fetching existing webhooks.
  • Auditing or listing all webhooks associated with a pipe to ensure correct event handling.
  • Dynamically adjusting workflow triggers based on current webhook configurations.

Properties

Name Meaning
Authentication Method of authenticating with Pipefy API: either using a Service Account or a Personal Access Token.
Pipe Name or ID Select or specify the Pipe by name or ID to retrieve its associated webhooks.

Output

The node outputs a JSON array where each item represents a webhook associated with the specified pipe. Each webhook object typically contains details such as the webhook's ID, URL, events it listens to, and status. This structured data allows further processing or conditional logic within n8n workflows.

No binary data output is involved in this operation.

Dependencies

  • Requires an active Pipefy account.
  • Needs either a Service Account credential or a Personal Access Token credential configured in n8n for authentication.
  • Internet access to reach the Pipefy GraphQL API endpoint.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication credentials will cause authorization failures.
    • Specifying a non-existent or inaccessible pipe ID/name will result in errors or empty results.
    • Network connectivity issues can prevent successful API calls.

  • Error Messages:

    • Authorization errors indicate problems with the provided API key or token; verify and update credentials.
    • "Pipe not found" or similar messages suggest the pipe ID/name is incorrect or the user lacks permissions.
    • Timeout or network errors require checking internet connection and Pipefy service status.

Links and References

Discussion