Run Manual Trigger
POST/v1/automations/:trigger_id/run
Run a manual automation trigger.
Only triggers whose event is manual can be run through the API. The trigger's actions
run under the same cooldown/burst/monthly-budget limits as message/timer/schedule
triggers, with the bot as the action author. There is no member or channel context, so
per-member work must go through a for_each_member action inside the trigger.
Pass an optional context map to supply extra template variables to the run, a flat map
of scalars, readable in the trigger's actions as {{ key }}. Unknown variables render as
empty, so a trigger that references a variable you didn't send still runs.
skipped is true when the trigger was found and allowed to run but Monni chose not to
execute its actions, either because its top-level conditions evaluated false or because
an abuse-prevention gate (per-trigger cooldown, guild burst cap, monthly execution
budget) rejected the run. Nothing ran, and errors is empty. A skipped run still
counts against your rate limits.
Runs are counted against the automation-runs limit on top of the limits every endpoint
shares.
Requires an API key with the automations.run permission.
Request
Responses
- 200
- 429
Successful Response
Out of requests. X-RateLimit-Bucket says which limit you hit and Retry-After how many seconds to wait. This request was not counted against you.
Response Headers
Plan your limits were taken from.
The limit the other headers describe, the one closest to running out.
Requests allowed in that window.
Requests left in the current window.
Unix timestamp in seconds of when that window resets.
Seconds to wait before trying again.