Pipefy icon

Pipefy

Interact with Pipefy GraphQL API
Join our community

Actions17

Overview

This node operation creates a webhook in a specified Pipefy pipe. It allows users to set up webhooks that listen to various events occurring within a Pipefy pipe, such as card creation, updates, comments, and more. This is useful for automating workflows by triggering actions in other systems when specific events happen in Pipefy.

Use Case Examples

  1. Automatically notify a team chat when a new card is created in a Pipefy pipe.
  2. Trigger an external system to update its records when a card is moved or updated in Pipefy.

Properties

Name Meaning
Authentication Select the authentication method to use for connecting to Pipefy (Service Account or Personal Access Token).
Name The name of the webhook to create.
URL The URL that Pipefy will call when the webhook event occurs. Must be a valid URL.
Pipe Name or ID The Pipefy pipe where the webhook will be created. Can be selected from a list or specified by ID.
Events The list of Pipefy events that will trigger the webhook. Multiple events can be selected.
Authorization Token A secret token sent in the 'X-Pipefy-Signature' header with every webhook request for verification.
Additional Fields Optional additional settings for the webhook, including notification email, custom headers, and filters.

Output

JSON

  • id - The unique identifier of the created webhook.
  • name - The name of the created webhook.
  • url - The URL configured for the webhook.
  • pipeId - The ID of the Pipefy pipe where the webhook was created.
  • events - The list of events that trigger the webhook.
  • authorizationToken - The authorization token used for webhook request verification.

Dependencies

  • Pipefy GraphQL API

Troubleshooting

  • Ensure the provided URL is a valid and reachable HTTPS endpoint to avoid webhook creation failures.
  • Verify that the selected Pipe ID exists and the user has permission to create webhooks on it.
  • If using filters, note that only the first event in the events list will be applied due to Pipefy API limitations.
  • Authorization token must be a secure, random string to prevent unauthorized webhook calls; use recommended methods to generate it.
  • Common errors include authentication failures due to invalid credentials and validation errors for missing required fields like name, URL, or events.

Links

Discussion