Skip to main content
Run an implemented project task once, verify its result, then create a schedule for recurring execution. Set an API credential with access to the project. The example uses a task named daily-summary in support-assistant. Implement the task before running it. Creating task metadata alone does not implement its behavior.

1. Run the task once

Start the task with POST /runs. Replace <PROJECT_ID> with the project’s UUID:
run-task.sh
The response includes run.run_id. Acceptance means the run was created, not that the task finished successfully.

2. Create a recurring schedule

Schedule the task with POST /projects/{project_reference}/schedules:
schedule-task.sh
This schedule runs at 08:00 UTC each day. Forbid prevents overlapping runs from this schedule.

Verify the result

Read GET /runs/{run_id} and confirm the one-off run completes with the expected output. If it fails, inspect its events before enabling repeated execution. Read the saved schedule and check its target, timezone, and enabled state. Each scheduled execution creates a separate run to inspect. Use a workflow when the implementation needs multiple coordinated steps. Workflow runs have their own request fields; do not change only the task run’s kind.

API references