set_trigger_schedule
Change how often the trigger checks, from the choices the Studio's schedule form has: every N minutes or hours (frequency "custom", with every and unit; N must split the hour or day evenly), "daily", "weekly" (daysOfWeek 0 = Sunday to 6 = Saturday) or "monthly" (day 1 to 28). Give times as the user's own clock (hour 0-23, minute); never convert to UTC, and pass timeZone for a time of day. It takes effect at once, with no publish. It changes how often every playbook that uses the trigger gets items, and how often the app is called: when more than one playbook uses it, confirm with the user first. The answer lists when it will really run next.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"triggerId": "<triggerId>",
"frequency": "<frequency>"
},
"name": "set_trigger_schedule"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hour | No | For daily, weekly, monthly: 0-23, on the user's clock. | |
| unit | No | For custom. | |
| every | No | For custom: every N, from 1, 2, 3, 4, 5, 6, 10, 12, 15, 20, 30 minutes or 1, 2, 3, 4, 6, 8, 12 hours. | |
| minute | No | For daily, weekly, monthly: 0-59. | |
| timeZone | No | The user's IANA time zone, e.g. "Australia/Sydney". Pass it when you know it: times are read back on the user's own clock and never in UTC. Without one, a time of day is refused and no clock times are shown. | |
| frequency | Yes | ||
| triggerId | Yes | The trigger's id, from list_triggers or create_trigger. | |
| dayOfMonth | No | For monthly: 1 to 28. | |
| daysOfWeek | No | For weekly: 0 (Sunday) to 6 (Saturday). |