Pipefy icon

Pipefy

Interact with Pipefy GraphQL API

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 react to events occurring within a particular pipe, such as card creation, updates, or transitions.

Practical examples include:

  • Automatically syncing Pipefy pipe events with other systems by fetching existing webhooks.
  • Auditing or managing webhook configurations programmatically.
  • Triggering workflows based on pipe activity by first retrieving relevant webhook details.

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 from which to retrieve webhooks. Can be chosen from a list or provided via expression.

Output

The node outputs an array of JSON objects representing the webhooks associated with the specified pipe. Each object contains details about a webhook, such as its ID, URL, events it listens to, and status. This structured data can be used downstream in workflows to process or analyze webhook configurations.

No binary data output is involved in this operation.

Dependencies

  • Requires access to the Pipefy GraphQL API.
  • Needs authentication credentials, either a service account API key or a personal access token.
  • The node depends on n8n's ability to load pipe options dynamically for the "Pipe Name or ID" property.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication tokens will prevent successful API calls.
    • Specifying a non-existent pipe ID or name will result in no webhooks being returned or an error.
    • Network connectivity issues may cause timeouts or failures when calling the Pipefy API.

  • Error Messages:

    • Authentication errors typically indicate invalid credentials; verify and update your API keys.
    • "Pipe not found" or similar messages suggest the pipe ID/name is incorrect; double-check the input.
    • API rate limits might cause temporary failures; consider retrying after some time.

Links and References

Discussion