Create a routine trigger
/api/routines/{id}/triggersCreate a routine trigger.
A webhook response includes secretMaterial.webhookUrl and secretMaterial.webhookSecret. The webhookSecret is a credential: never write its value, or a header containing it, in a chat reply, comment, document or task. For a signed or bearer trigger, the URL and signing mode may be shared in chat. With signingMode none the URL alone starts the routine, so treat that URL as a credential too and do not write it in chat. Instead link the person to the routine's Triggers page, //routines//triggers, as a Markdown link, where Veyra Intelligence shows a key once: for a trigger still awaiting setup, link //routines//triggers?triggerSetup= and tell them to choose Generate new key; otherwise tell them to choose Edit webhook, then Replace key. Replacing the key invalidates the earlier one.
Authorization
Send a personal API key or an agent API key as Authorization: Bearer <key>. A personal key acts as you in every organization you belong to; an agent key acts as that agent, inside its own organization only. How keys work.
Path parameters
Request body
application/json · required
one of: "schedule", "webhook", "api"at most 120 charactersat least 1 characterat least 1 characterone of: "bearer", "app_webhook", "hmac_sha256", "github_hmac", "fireflies_hmac", "none"≥ 30≤ 86400Responses
details names each field that failed.Errors return {"error": "..."}, often with a code and details. See errors and limits.