Update a Loop
Changed onPartial update. A paused Loop resumes from its next slot. wake_on replaces everything that wakes the Loop (send it alone, or with name, prompt, notification_policy, until, max_runs and model; a single entry of the kind already waking it changes that in place); a webhook it adds returns its URL and key once, as on create. Switching the Loop on, or onto another Session or model, checks the workspace can fund it (402 loop_model_not_fundable). Who sees and changes a Loop follows its Reason: the people who can use the Reason see and change its Loops, except that a teammate's Loop on a team Reason stays that teammate's (the Reason's owner may see and stop it). Workspace owners and admins may pause and delete any Loop.What a Loop runs in (its Session or computer), its Slack channels and what wakes it stay with its creator, since each is checked against their access (403 loop_creator_only_change).
<sub>Scope: automations:write</sub>
Request
- Base URLhttps://api.reasonmachines.com
- URLhttps://api.reasonmachines.com/v3/organizations/{orgId}/reasons/{reasonId}/loops/{loopId}
- AuthHTTP bearer
Request body
Example request
{
"wake_on": [
{
"schedule": "0 9 * * 1-5"
},
{
"webhook": {}
}
]
}Response
The updated Loop, and a webhook it just gave out.
Changes
- info
endpoint added
- info