runCount.
Omitted fields stay as they are. The schedule is checked after your fields are merged with the stored clock. Changing only frequency can reuse the stored timeOfDay. A merged clock that is incomplete returns 400.
Sending attachmentIds replaces the attachment list. Omitting attachmentIds leaves attachments unchanged. Sending a tag array replaces that array. An empty array clears it. Inaccessible tagged ids and slugs are dropped.
Base URL
Required scopes
This endpoint requires theAUTOMATION_API scope (Scheduled Tasks API) on a workspace API key, or on a personal API key after your admin allows that scope.
Parameters
Unknown body fields are rejected. An invalid body returns
400 with message Invalid request and an errors array. An empty body returns 400 with message At least one field must be provided. A merged schedule that is still incomplete returns 400 with message automation_time_of_day_required, automation_day_of_week_required, automation_day_of_month_required, or automation_days_of_week_required.
Example
Response format
Success response (200 OK)
automation matches the scheduled task object without runCount.
Error handling
Langdock intentionally blocks browser-origin requests to protect your API key and ensure your applications remain secure. For more information, please see our guide on API Key Best Practices.