SUMMARY
Use Webhooks to automatically send event data from Factbird to external systems in real time. Webhooks enable event-driven integrations by sending structured JSON payloads to a specified endpoint whenever supported events occur, such as a batch starting or ending.
WHAT THIS IS
Webhooks are an integration feature that allows Factbird to notify external systems when specific events occur.
Instead of an external system repeatedly checking Factbird for changes, Factbird automatically sends an HTTP POST request containing structured JSON data whenever a configured event is triggered.
This makes Webhooks well suited for integrating Factbird with ERP, MES, data platforms, cloud services, or custom applications that need near real-time production updates.
WHY IT MATTERS
Webhooks help automate data exchange between Factbird and other business systems.
Using Webhooks allows you to:
- Send production events to external systems automatically.
- Reduce manual data transfers.
- Eliminate the need for continuous API polling.
- Trigger downstream business processes when production events occur.
- Build near real-time integrations with third-party applications.
WHEN YOU WOULD USE THIS
Use Webhooks when you want to:
- Notify an ERP system when a batch starts or finishes.
- Trigger external workflows based on production events.
- Synchronize production information with another platform.
- Build automated integrations using JSON payloads.
- Reduce polling against the Factbird API.
HOW IT WORKS
A Webhook consists of four primary elements:
- Endpoint URL – The destination that receives the webhook request.
- Trigger Event – The Factbird event that initiates the webhook.
- Optional HTTP Headers – Used when authentication, such as an API key, is required.
- Scope – Defines whether the webhook applies to an entire organization, a site, or a specific production line.
When a configured event occurs, Factbird sends an HTTP POST request containing a structured JSON payload to the configured endpoint.
At the time of writing, the supported trigger events are:
- Batch Start
- Batch End
- Stop registered
- Stop unregistered
- Andon call created
- Andon call taken
- Andon call released
- Andon call resolved
- Andon call reopened
- Andon call cancelled
Each webhook includes an execution history, allowing administrators to monitor successful and failed deliveries. Factbird recommends testing each webhook after creation to verify that the receiving system processes the payload correctly.
KEY TERMS / COMPONENTS
Webhook
- An HTTP callback that automatically sends data when a configured event occurs.
Endpoint
- The HTTPS URL that receives the webhook payload.
Trigger Event
- The Factbird event that causes a webhook to be sent.
JSON Payload
- The structured data sent to the receiving system.
Headers
- Optional HTTP headers used for authentication or other endpoint requirements.
Scope
- Defines where the webhook applies, such as an organization, site, or production line.
COMMON MISUNDERSTANDINGS
- Webhooks send data only when a supported event occurs; they do not continuously stream production data.
- Factbird delivers the webhook, but the receiving system is responsible for accepting and processing the JSON payload correctly.
- Webhooks complement the Factbird API rather than replace it. APIs are better suited for querying data on demand, while webhooks are intended for event-driven notifications.
- At present, only Batch Start and Batch End are supported webhook triggers. Additional trigger types may become available in future releases.
RELATED ARTICLES