Appearance
Integrations & Webhooks
Webhooks let you receive automatic notifications in external systems when specific events occur in produuz.it.
How Webhooks Work
When a configured event happens (e.g., a constructible is marked as ready), produuz.it sends an HTTP POST request to your specified URL with event data in the payload.
Event Types
| Event | Triggered When |
|---|---|
| Constructible Start | A constructible begins production (first station started). |
| Constructible Ready | A constructible completes all production stations. |
| Station Ready | A specific station is marked as completed for a constructible. |
| Report Deprecation | A report's underlying design data has been updated. |
Configuring a Webhook
| Field | Description |
|---|---|
| URL | The endpoint that will receive the POST request. |
| Event type | Which event triggers this webhook. |
| Payload fields | Which data fields to include in the request body. |
| Production line | Optionally scope the webhook to a specific production line. |
| Auth method | Authentication type (Bearer token, API key, etc.). |
| Secret | Shared secret for request signing or authentication. |
| Custom headers | Additional HTTP headers to include with each request. |
Authentication
You can secure your webhook endpoint by configuring:
- Auth header — Adds an
Authorizationheader with your chosen method and secret. - Custom headers — Add any additional headers your endpoint requires.
Watching Users
Assign users to "watch" a webhook. Watching users receive in-app notifications when the webhook fires, in addition to the external HTTP request.
Use Cases
- ERP integration — Sync production status to your business system.
- Label printing — Trigger label printing when a constructible is ready (see NiceLabel tutorial).
- Notifications — Send alerts to Slack, Teams, or other messaging platforms.
- Quality tracking — Log production events in external quality management systems.