Change how an agent is allowed to run

patch https://api.intelig.ai/api/v1/intelig/agents/{name}/activation

Auth: Authorization: ApiKey <key> (an API key sent as Bearer is rejected) or Authorization: Bearer <jwt> for a dashboard session. operationId: updateActivation

Sets which triggers are live (manual, event, scheduled), what each trigger is allowed to do, and whether the agent may deliver output or spend on model calls. Send a preset for the common profiles, or the individual switches for full control; omitted fields are left as they are. Requires the `agent:write` scope.

Example request

curl -X PATCH "https://api.intelig.ai/api/v1/intelig/agents/string/activation" \
  -H "Authorization: ApiKey $INTELIG_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "preset": "ADVISORY",
    "manualEnabled": true,
    "eventEnabled": true,
    "scheduledEnabled": true
  }'

Path parameters

Name	Type	Required	Description
`name`	string	yes	—

Request body

application/json

Field	Type	Required	Description
`preset`	string	no	Shorthand for a whole activation profile. When set, it fills in the individual switches below. One of: OFF, MANUAL_ONLY, AUTOMATIC, AUTOMATIC_ADVISORY, AUTOMATIC_APPLY, SCHEDULED_SEND Example: ADVISORY
`manualEnabled`	boolean	no	Whether a human may trigger this agent on demand. Example: true
`eventEnabled`	boolean	no	Whether inbound events (a push, a merged PR, an ingested meeting) may trigger it. Example: true
`scheduledEnabled`	boolean	no	Whether its cron schedule may trigger it. Example: true
`eventMode`	string	no	What an event-triggered run is allowed to do. One of: OFF, PREVIEW, DRY_RUN, APPLY Example: DRY_RUN
`scheduledMode`	string	no	What a scheduled run is allowed to do. One of: OFF, PREVIEW, DRY_RUN, APPLY Example: DRY_RUN
`sendEnabled`	boolean	no	Whether the agent may deliver its output (email, Slack). False keeps runs internal. Example: false
`aiSpendEnabled`	boolean	no	Whether the agent may spend on model calls. False makes every run a no-op. Example: true

Response 200

application/json · ApiResponseAgentDetailResponse

Field	Type	Description
`success`	boolean	—
`message`	string	—
`data`	AgentDetailResponse	—

Status codes

200 — OK
401 — —
404 — Not Found
429 — —

Every response is wrapped in { success, message, data }. A 4xx means the request is wrong — do not retry it unchanged. A 429 carries Retry-After in seconds.