Guides
Agent target guides
Per-target setup for the agent destinations Hooks delivers to: what to copy on the target side, how the destination config references secrets, how the task or input renders, and what each response status means. Start with the use-case overview if you have not wired an endpoint yet.
Trigger AI agents from webhooksPoint the provider's webhook at a Hooks endpoint, add one destination per agent target with filters and a task template, and every matching event becomes an agent task with retries and a delivery log.Grok Bot target guideA Hooks destination POSTs one JSON task to your Grok Bot routine URL with a Bearer key; a 2xx means the task was queued. Configure the routine URL and key once, then map event fields into the task template.T3 Code target guideA Hooks destination POSTs JSON to your T3 Code task's On a webhook URL; T3 Code answers 202 when the agent run is accepted. Keep the URL (it carries a token) in a project secret and sign the body when the task requires it.Paseo target guideA Hooks destination POSTs one manual-run dispatch to Paseo Hub (on: manual.run) with project, trigger, actor, and rendered input. Hub answers 200 with a triggerRunId that Hooks records on the delivery.