Mutation
mutation CreateBoltSchedule($schedule: BoltScheduleInput!) {
createBoltSchedule(schedule: $schedule) {
ok
slug
name
}
}Variables
{
"schedule": {
"name": "string",
"schedule": "string",
"environment": "string",
"commands": [
"string"
]
}
}Response
{
"data": {
"createBoltSchedule": {
"ok": true,
"slug": "string",
"name": "string"
}
}
}createBoltSchedule
Create a new bolt schedule with the full parameter set the Bolt UI supports.
Caller supplies a human-readable name; the backend generates a
unique slug from it and returns both fields. Use the slug for any
follow-up triggerBoltRun / deleteBoltSchedule calls. The schedule is
validated synchronously (allowed commands, cron expression, timezone,
notification events) before being persisted.
MUTATION
createBoltSchedule(schedule: BoltScheduleInput!): CreateBoltScheduleArguments
schedule
required
Returns
ok
Boolean!
slug
String!
The generated slug — use this as the identifier in subsequent API calls.
name
String!
The human-readable name as persisted.
Mutation
mutation CreateBoltSchedule($schedule: BoltScheduleInput!) {
createBoltSchedule(schedule: $schedule) {
ok
slug
name
}
}Variables
{
"schedule": {
"name": "string",
"schedule": "string",
"environment": "string",
"commands": [
"string"
]
}
}Response
{
"data": {
"createBoltSchedule": {
"ok": true,
"slug": "string",
"name": "string"
}
}
}Related topics
Bolt APIBolt CLIKeep Bolt schedules running past a failed commandBoltCreate a schedule