Actions17
- Attachment Actions
- Card Actions
- Pipe Actions
- User Actions
- Webhook Actions
Overview
This node integrates with the Pipefy GraphQL API to retrieve information about webhooks configured within a specific organization. The "Get Org Webhooks" operation under the "Webhook" resource allows users to fetch all webhooks associated with a chosen organization by specifying its name or ID.
Common scenarios for this node include:
- Monitoring webhook configurations in an organization to audit or manage integrations.
- Automating workflows that depend on existing webhook setups.
- Synchronizing webhook data from Pipefy into other systems for reporting or analysis.
For example, a user might use this node to list all webhooks in their Pipefy organization before updating or deleting them programmatically.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Pipefy API. Options: "Service Account" or "Personal Access Token". |
| Org Name or ID | Select or specify the target organization's name or ID to retrieve its webhooks. Required field. |
Output
The node outputs a JSON array where each element represents a webhook object retrieved from the specified organization. Each webhook object typically contains details such as webhook ID, URL, events it listens to, and status.
If the node supports binary data output (not indicated here), it would represent any file or media content related to webhooks, but this is not applicable for this operation.
Dependencies
- Requires access to the Pipefy GraphQL API.
- Requires valid authentication credentials, either via a service account or a personal access token.
- The node depends on n8n's credential management to securely store and use these credentials.
- The "Org Name or ID" property uses a dynamic options loader method (
getOrgs) to populate selectable organizations.
Troubleshooting
- Authentication errors: Ensure that the provided API key or token is valid and has sufficient permissions to access organization webhooks.
- Invalid Org ID: If the organization ID or name is incorrect or does not exist, the node will fail to retrieve webhooks. Verify the input or use the dynamic selector.
- API rate limits: Frequent calls may hit Pipefy API rate limits; consider adding delays or error handling to retry.
- Empty results: If no webhooks are returned, confirm that the organization actually has webhooks configured.
Links and References
- Pipefy API Documentation
- n8n Expressions Documentation (for using expressions in properties)