Overview
Automation Alerts via Webhook delivers real-time notifications for every automation execution in Pipefy, whether it succeeds or fails. You configure a webhook endpoint per pipe and start receiving execution status automatically, including root cause context whenever something goes wrong.
What's new?
- Automation execution webhook: configure an endpoint via the Pipefy API with the automation.execution action to receive alerts for every execution, both successes and failures.
- Full payload: each notification includes the automation name, trigger, action, execution status (success or failed), duration, and card and pipe details.
- Root cause context on failures: when an execution fails, the payload includes the reason: wrong conditional field, required field violation, empty field, and others.
- Filters by trigger and action type: each webhook can be configured with specific filters, delivering only the relevant alerts for that pipe.
- Requires Pipe Admin or Service Account to create the webhook.
How does this help?
- Proactive visibility into failures: your team is notified the moment an automation fails, without manual monitoring or waiting for a user to report the issue.
- Faster diagnosis: root cause context arrives with the alert, cutting investigation and resolution time for automation incidents.
- Centralized monitoring: connect alerts to tools your team already uses: dashboards, notification channels, BI platforms.
- Execution traceability: every execution is logged with duration and status, creating an auditable history for process health reviews.
Use cases
1. IT team monitors automation health via DatadogAn IT analyst configures a webhook on the vendor onboarding pipe pointing to a Datadog endpoint. Every automation execution sends a payload with status, duration, and action name. When an automation fails due to a required field not being filled, Datadog creates an alert automatically. The analyst identifies which phase generated the failure without opening Pipefy.
2. Ops team receives critical failures directly in SlackThe procurement operations team configures a webhook on the purchase approval pipe integrated with a Slack channel. When a card movement automation fails due to a conditional violation, the message arrives in the channel with the automation name, the affected card, and the root cause. The team acts within minutes, without waiting for the requester to notice the request has stalled.
3. Process manager tracks automation efficiency in Power BIA process manager configures webhooks on the company's key pipes, sending payloads to an endpoint that feeds Power BI. Using status, duration, and action type data, they build an automation health dashboard by pipe, identifying which processes have the highest failure rates and where errors are concentrated.
4. IT team catches integration errors before the process stallsOn a pipe integrated with an ERP, field update automations depend on data coming from external systems. With the webhook in place, when a field arrives empty and the automation fails, the alert reaches the integration team immediately. The fix happens before other cards in the same process are affected.
5. Service Account centralizes monitoring across a multi-pipe environmentA Pipefy admin configures webhooks across all critical pipes using a Service Account, with alerts pointing to a central monitoring system. The team gains consolidated visibility into automation health across the entire company, with execution history and failure patterns identifiable over time.
Most relevant for
- IT teams responsible for maintaining and governing Pipefy processes
- Pipe Admins managing automations on critical pipes
- Operations analysts who need visibility into automation execution
- Process architects monitoring flow health across multiple pipes
Documentation
For the full step-by-step, check the developer documentation.
