Skip to main content
By the end of this guide your CI can start an agent with one HTTP request: when a deploy fails, it POSTs to a URL, and an agent reads the recent changes and says what probably broke. The URL belongs to a webhook trigger declared in the workflow. Webhooks is the reference for every option this guide uses.

Before you begin

1

Declare the webhook trigger

The filter decides which deliveries start a run. The inputs mapping copies the fields the run needs out of trigger.payload.body, the parsed JSON body. ?field.orValue(...) keeps a missing field from failing the delivery.
.reliant/workflows/deploy-failure-triage.yaml
mode: plan gives the agent read-only tools. The on_failure: step makes a failed unattended run say so; without it reliant workflow lint warns [no-failure-path].
2

Check it against a sample delivery

--trigger-payload runs the filter, the inputs mapping and the prompt against a sample event. -V prints the warnings:
terminal
A sample with "status":"failed" passes with no warning. A scenario can fire the trigger to test the whole run. Have nodes read inputs, as above: in v1.21.3 a node that reads trigger.payload fails under scenario run with no such key: payload, though it works in a real run.
3

Enable it and copy the URL and token

Commit the workflow. In the app, open Workflows → Library, open the workflow and choose Enable. The dialog shows the Webhook URL and a Token. The token is shown once, so store it in the sender now.reliant trigger activate turns the trigger on from a terminal:
terminal
The token is printed once. A CLI older than v1.24 doesn’t print it: run reliant trigger rotate <activation id>, or open the automation in the app and choose Rotate token.
4

Send a test delivery

terminal
202 means the delivery was recorded; the run starts asynchronously. Sending the same Idempotency-Key again returns "duplicate":true and starts nothing. A body the filter rejects returns 202 with "outcome":"skipped".
5

Verify the run started

terminal
Open the launched run under Workflows → Runs, or follow it with reliant workflow follow <chat-id>. Its first message is the prompt with service: checkout-api filled in, and the record step says Deploy of checkout-api failed at commit 9f2c1ab.
6

Pause or remove it

terminal
While it is disabled, a delivery with a valid token gets 409 trigger is disabled, so a retrying sender knows to stop. After you delete it, the URL answers 404.

What this does not do

  • It does not trust the payload. Anyone holding the token can start a run with any body. The filter and the inputs mapping only pick fields out of it. The prompt above labels those fields as data and the agent can’t change files, but a payload can still try to steer the agent. Keep agents that act on webhook data read-only, or put an approval before anything that writes.
  • The response is not the run’s result. The sender gets 202 as soon as the delivery is recorded. Read the outcome in the run, or have the workflow report it, for example with a Slack step.
  • In an organization with two or more members, runs spend only the organization’s AI accounts (Unattended funding: org_only). Without one that can run the model, the run stops at its first agent step.
  • A machine that is off can’t run it. A suspended cloud machine is woken; your own laptop or server must be online.
  • Send your own idempotency key. Two identical bodies sent without one were recorded as two events and would have started two runs.

Troubleshooting

The trigger ID or the token is wrong, or the token was rotated: an old token stops working at once. Each gets the same answer, so IDs are not revealed. A signed delivery to a trigger with no HMAC secret gets it too.
The token is right but the trigger is paused. Run reliant trigger enable <name>, or choose Enable again in the app.
The workflow declares webhook: {hmac: …}, so enabling it needs the secret the sender signs with. Pass it from a file: reliant trigger activate … --hmac-secret-file <trigger name>=<file>. The Enable dialog doesn’t take one yet, and neither does a CLI older than v1.24: there, remove the hmac: block and authenticate with the bearer token.
The run started; its first agent step could not be funded. An admin adds an organization API key or turns on Reliant credits in Settings → Organization → AI accounts. reliant workflow status <chat-id> shows call_llm FAIL, and reliant workflow follow <chat-id> prints the full error.

Next steps

Webhooks reference

Path tokens, HMAC, dedupe_key, every response code and what the run sees.

Call an API without exposing the key

Have the run call back out with a key no step or model can read.

Agent on a schedule

Start the same kind of run from cron instead of a request.

HTTP integration

Calling out of a workflow rather than in.