Automation Scheduling

2 Endpunkte. Basis-URL: https://xapi.ambertech.cloud/api/v1

Pause the cron schedule#

POST/automations/{id}/schedule/pauseToken

Sets `is_active=false` on the automation's cron schedule, silencing future cron-triggered runs. The automation itself stays `published` — only the scheduled trigger is muted. Use POST /:id/schedule/resume to reactivate. Has no effect on webhook-triggered automations.

Parameter

Name	Ort	Typ	Beschreibung
`id`Pflicht	Pfad	`string`	Automation UUID

Antworten

200`{ automation_id: string, schedule_active: false }`
401Not authenticated
404Automation not found

Beispiel (cURL)

curl -X POST "https://xapi.ambertech.cloud/api/v1/automations/{id}/schedule/pause" \
  -H "Authorization: Bearer $XISUITE_TOKEN"

Resume the cron schedule#

POST/automations/{id}/schedule/resumeToken

Sets `is_active=true` and recomputes `next_run_at` from the current time using the stored `cron_expression` and `timezone`. Safe to call even when `next_run_at` is stale — it always recalculates from now. Returns 404 if no schedule row exists (automation was never published with a cron trigger).

Parameter

Name	Ort	Typ	Beschreibung
`id`Pflicht	Pfad	`string`	Automation UUID

Antworten

200`{ automation_id: string, schedule_active: true }`
401Not authenticated
404Automation not found or no cron schedule exists

Beispiel (cURL)

curl -X POST "https://xapi.ambertech.cloud/api/v1/automations/{id}/schedule/resume" \
  -H "Authorization: Bearer $XISUITE_TOKEN"