Inbound Webhooks automation integration with GenticFlow
Receive external events, device records, and alerts into GenticFlow
GenticFlow inbound webhooks accept JSON payloads from external systems and turn them into connector data items or alerts. Data payloads create or update items using ID, Name, and Type fields, with optional Description and Category. Alert payloads can create or update alerts for existing webhook items.
What GenticFlow does with this integration
Data Item Ingestion
- JSON payloads can create or update webhook-backed data items
- Each item uses ID, Name, and Type fields
- Description and Category fields are optional
- IDs can be auto-generated when that webhook setting is enabled
Alert Endpoint
- POST requests to the alert endpoint create or update alerts for webhook items
- endpoint_id, level, and message are required for alert payloads
- unique_id can deduplicate repeated alerts
- Details, error_code, and data can carry extended context
Controls and Automation
- X-Secret header authentication is supported when a webhook secret is configured
- Request logging can be enabled per webhook
- Rate limits and payload validation protect the ingestion endpoint
- Webhook-created data items and alerts can trigger workflows
How It Works
Create an inbound webhook
Configure method, active state, optional secret, logging, policy, and whether IDs can be autogenerated.
Send JSON payloads
External systems POST data items with ID, Name, Type, and optional Description or Category fields.
Create alerts when needed
Use the webhook alert endpoint to attach warning, error, or critical alerts to existing webhook items.
Trigger workflows
Webhook data item and alert events can start event-driven workflows with the payload context attached.
Automation with guardrails.
Inbound Webhooks extends GenticFlow without bypassing the product controls. Events, alerts, or approved callable functions can enter the workflow while validation, permissions, and execution history stay in place.
Request a Demo