Workflow Library
Turn a verified n8n, GitHub, or Datadog event into one contextual call to the person who can act—then return the answer to the originating workflow.
What This Library Solves
Use a phone call when the automation has verified a high-consequence event, waiting creates material harm, and a named person can take a bounded action immediately. These recipes combine vendor-native triggers with fail-closed policy gates, one supervised self-test, and callback correlation. Routine errors, unverified alerts, unknown recipients, and duplicate events stay in normal text channels.
The Phone-Worthiness Gate
Guarded Workflow Recipes
Each independent recipe includes the exact trigger, suppression rules, safe fields, test fixture, and result path. No native vendor partnership is implied.
Automated checks verify route data, downloadable assets, fail-closed policy gates, secret scans, and the production build. This is not a live vendor-account certification. Complete one supervised call to yourself before production use; live calls can consume calling minutes.
n8n workflow recipe
When an AI workflow is still blocked and a real deadline is closing, call the named owner for one bounded decision—then return the answer to n8n.
Signed webhook recipe
Verify the signed webhook, confirm the alert is open in a protected production repository, and place one acknowledged call—without sending the detected credential to ClawdCall.
Webhook + bridge recipe
Wait for a production P1 to persist, confirm customer impact, and call only while the incident is active, unacknowledged, and owned by someone who can act.
Build the Complete Path
Start with the supervised guide, verify the request contract, and understand usage costs before a production event can spend calling minutes.
Workflow FAQ
It is a controlled outbound call triggered by an automation after a policy gate confirms that a known human can act on an urgent event. The call collects an acknowledgment or bounded decision and returns that result to the originating workflow.
The initial library covers n8n AI workflow failures, GitHub secret scanning alerts, and persistent Datadog monitor incidents. Each integration has its own trigger, suppression rules, downloadable fixture, callback guidance, and supervised test path.
No. The recipes require a verified ClawdCall account, a pre-authorized recipient resolved from trusted configuration, a material event, and a fresh idempotency key. Start with your own number and synthetic data before enabling a production trigger.
Store the vendor event ID and returned ClawdCall call ID before calling. Then authenticate the completion callback or retrieve the transcript, validate a bounded response, and write the outcome back exactly once using the stored idempotency key.
Start Safely
Use synthetic data, inspect the payload, set yourself as the only recipient, and explicitly approve the first call. Live calls can consume calling minutes.
Start the supervised test