Actions17
- Attachment Actions
- Card Actions
- Pipe Actions
- User Actions
- Webhook Actions
Overview
This node allows users to create webhooks within a specified organization in Pipefy. Webhooks are HTTP callbacks that notify your application when certain events occur in Pipefy, such as user invitations or role changes. This node is useful for automating workflows by triggering external processes or integrations whenever specific organizational events happen.
Practical examples include:
- Automatically updating an internal CRM when a new user accepts an invitation.
- Sending notifications to Slack or email when a user is removed from the organization.
- Logging user role changes for audit purposes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose the authentication method: either using a Service Account or a Personal Access Token. |
| Name | The name of the webhook to be created. |
| URL | The destination URL where webhook payloads will be sent. Must be a valid URL (e.g., https://example.com/webhook). |
| Org Name or ID | Select or specify the organization by name or ID where the webhook will be created. |
| Events | Select one or more events that will trigger the webhook. Options include: user.invitation_acceptance, user.invitation_sent, user.removal_from_org, user.removal_from_pipe, user.removal_from_table, user.role_set. |
| Authorization Token | A secret token sent in every webhook request in the X-Pipefy-Signature header for verifying the authenticity of requests. Recommended to use a random string generated securely. |
| Additional Fields | Optional extra settings: - Notification Email: Email address to receive webhook notifications. - Custom Headers: JSON object defining custom HTTP headers to send with each webhook request. |
Output
The node outputs a JSON array containing the response data from the Pipefy API after creating the webhook. This typically includes details about the newly created webhook such as its ID, name, URL, subscribed events, and other metadata.
No binary data output is produced by this node.
Dependencies
- Requires access to the Pipefy GraphQL API.
- Requires an API authentication credential, either a service account or a personal access token.
- The node uses dynamic loading of organizations (
getOrgsmethod) to populate the Org selection dropdown. - No additional environment variables are explicitly required beyond the API credentials.
Troubleshooting
- Invalid URL error: Ensure the URL provided is a valid HTTPS endpoint accessible from Pipefy.
- Authentication failures: Verify that the selected authentication method has valid credentials and sufficient permissions to create webhooks in the target organization.
- Missing required fields: The node requires the webhook name, URL, organization, and at least one event to be selected. Make sure these are all provided.
- Authorization token issues: If webhook requests fail verification, confirm that the authorization token matches what is expected on the receiving end and is sent correctly in the
X-Pipefy-Signatureheader. - API rate limits or permission errors: Check Pipefy API usage limits and ensure the authenticated user has rights to manage webhooks.