Keragon

Register a new named bridge to a Keragon workflow -- paste the workflow's HTTP Webhook Trigger URL (from the trigger step's setup screen inside Keragon) and give it a short label so you can fire it by name later with send_bridge_event.

List your configured outgoing bridges to Keragon workflows -- names and descriptions only, never the underlying trigger URLs.

Read one outgoing bridge's name and description by id (never the underlying trigger URL).

Update an existing outgoing bridge's name, trigger URL, and/or description. Only given fields change.

Permanently remove an outgoing bridge. Cannot be undone -- the Keragon workflow itself is unaffected, only Imperal forgets its URL.

Fire one configured Keragon workflow right now by POSTing a JSON payload to its HTTP Webhook Trigger URL. Run create_outgoing_bridge first if you haven't registered this workflow yet.

Fire the SAME payload to several configured Keragon workflows in one call -- e.g. notify both 'New patient intake' and 'Slack alert' bridges at once. Continues past per-bridge failures and reports each outcome. This is an Imperal-side convenience -- Keragon itself has no bulk-trigger endpoint.

Read the inbound webhook URL and whether a shared secret is set up for receiving events FROM a Keragon workflow (via its 'HTTP Client action' step). Never reveals the secret itself.

Generate a fresh shared secret for the inbound direction (Keragon -> Imperal), discarding any previous one. Paste the new value into a custom header named X-Keragon-Webhook-Secret on your workflow's 'HTTP Client action' step.

List the most recent events a Keragon workflow has POSTed into this app via the inbound webhook, newest first. Optionally filter by event_kind.

Get the full stored body and headers preview of one inbound event, by id from list_inbound_events.

Aggregate health report across every configured Keragon bridge: how many outgoing bridges exist, whether the inbound webhook is ready, how many inbound events arrived per event_kind, and which bridges have never produced a matching inbound callback (a signal a workflow's trigger URL may be broken or misconfigured). Keragon itself has no cross-bridge delivery-history view -- this is built entirely from what Imperal has recorded on its own side.