Actions17
- Attachment Actions
- Card Actions
- Pipe Actions
- User Actions
- Webhook Actions
Overview
This node integrates with the Pipefy platform to create webhooks at the organization level. It allows users to register a webhook URL that Pipefy will call when specific user-related events occur within an organization, such as invitation acceptance, invitation sent, user removal, or role changes.
Common scenarios where this node is beneficial include:
- Automating workflows triggered by user management events in Pipefy organizations.
- Synchronizing user status or roles between Pipefy and other systems.
- Receiving real-time notifications about user invitations or removals for auditing or alerting purposes.
For example, you could use this node to create a webhook that notifies your internal system whenever a new user accepts an invitation to join your Pipefy organization, enabling automated onboarding processes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose the authentication method: - Service Account - Personal Access Token |
| Name | The name of the webhook to be created. |
| URL | The destination URL where Pipefy will send webhook requests. Must be a valid URL (e.g., https://example.com/webhook). |
| Org Name or ID | Select or specify the Pipefy organization by name or ID where the webhook will be registered. |
| Events | Select one or more user-related 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 authenticity. Recommended to generate a random string and store securely. |
| Notification Email | (Optional) An email address to receive notifications related to the webhook. |
| Custom Headers | (Optional) JSON object defining custom HTTP headers to include in every webhook request. |
Output
The node outputs a JSON array containing the response from Pipefy 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 involved.
Dependencies
- Requires a valid Pipefy API authentication credential, either via a service account or a personal access token.
- The node depends on Pipefy's GraphQL API to create the webhook.
- The "Org Name or ID" property uses a dynamic options loader to fetch available organizations from Pipefy.
- Proper network connectivity to Pipefy API endpoints is necessary.
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 correct and active credentials.
- Missing required fields: The node requires the webhook name, URL, organization, and at least one event to be specified.
- Authorization token verification issues: If webhook requests are rejected or fail signature verification, confirm the authorization token matches what is configured in Pipefy and your receiving endpoint.
- Event subscription errors: Make sure the selected events are valid and supported by Pipefy for organization-level webhooks.