Each template is a pre-built webhook configuration: the canonical field mapping, the exact payload your platform expects, and a curl command that creates the automation. No new services to stand up.
Push canonical readings into SiteWise on every normalize event. Includes the canonical-to-property alias map and the ingest shim that signs the AWS call.
Open an incident on the Table API when a machine breaches a threshold, with the machine ID, the reading, and the recommended action in the description.
Create a Case for field service dispatch so the technician arrives knowing the fault. Includes OAuth setup and token rotation.
Page the on-call engineer when an anomaly fires, with deduplication and automatic resolution when the reading recovers. The fastest one here.
Every template is the same two API calls. A tool holds the destination, the credentials, and the body shape. A trigger holds the condition. Forge evaluates the condition on every normalize event and fires the tool when it matches.
POST /v1/tools → register the destination once (returns a tool id)
POST /v1/triggers → attach a condition to that tool (fires from then on)
GET /v1/triggers/{id}/executions → every dispatch, with status and response
Because Forge normalizes first, the condition is written against a canonical field name like spindle_load_pct. It keeps working when you add a machine from a different manufacturer that calls the same measurement something else.