Webhook Trigger
Key Capabilities
- Unique webhook URL generation: Each workflow instance gets its own stable, unique URL that you share with the calling system.
- Multiple HTTP methods: Supports GET, POST, PUT, PATCH, DELETE, and HEAD — configure whichever the caller uses.
- Full request access: The workflow receives the request body, HTTP headers, query string parameters, and path parameters as structured data.
- Built-in authentication: Protect your endpoint with No Auth, Basic Auth, API Key, or Bearer Token authentication modes.
- Flexible response modes: Respond immediately on receipt (for fire-and-forget), or return the result of the last workflow node (for synchronous integrations).
- Custom response payloads: Define exactly what data the caller receives back, including HTTP status codes and response headers.
- Path parameterization: Embed dynamic values in the URL path (e.g.,
/orders/:orderId/confirm) for RESTful patterns.
Business Benefits
Real-Time Responsiveness
Workflows fire the instant an event occurs in an external system — no polling delays, no batch windows. Orders, payments, and alerts trigger automated responses within milliseconds.
Universal Integration
Any system that can send an HTTP request — Shopify, Stripe, SAP, GitHub, Salesforce, or a custom in-house app — can trigger your BizFirstAI workflows without custom connectors.
Secure by Default
Enforce authentication on every incoming request. API key, Bearer token, and Basic Auth options mean only authorized callers can activate your business processes.
Synchronous or Async
Choose whether the caller waits for the full workflow result or gets an immediate acknowledgment. This flexibility supports both real-time data-return APIs and fire-and-forget event pipelines.
Use Cases
E-Commerce Order Processing
A Shopify store posts a webhook on every new order. The Webhook Trigger receives the order payload, enriches it with customer data, and initiates fulfillment workflows — all in under a second of the order being placed.
Payment Gateway Callback
Stripe or PayPal sends a webhook on successful payment, failed charge, or refund. The Webhook Trigger captures the event type and payment details, then routes the workflow to update the accounts receivable system, send a receipt, or flag an exception.
GitHub CI/CD Event
A push or pull request event in GitHub triggers a webhook. BizFirstAI receives the repository, branch, and commit metadata and can kick off approval workflows, deployment jobs, or code review notifications to the relevant team.
ERP Data Sync Trigger
When an inventory record changes in SAP or Oracle ERP, the ERP posts a change event to the BizFirstAI webhook. The workflow transforms and syncs the data downstream to the WMS, e-commerce platform, and reporting database in real time.
Alert & Notification Pipeline
A monitoring system (PagerDuty, Datadog, or a custom tool) sends an alert webhook when a threshold is breached. BizFirstAI routes the alert, escalates to the right team, creates a ticket, and sends SMS and email notifications automatically.
In This Guide
Configuration
Set up the webhook path, HTTP method, authentication, and response behavior. Full property reference with types, defaults, and valid values.
Input & Output
Understand the output ports, what data is available downstream, and see a real data object with body, headers, query params, and path params.
Examples
Step-by-step configurations for Stripe payment webhooks, GitHub push events, ERP sync triggers, and more real business scenarios.