Skip to main content
Automated tasks let a Waker run on its own — best for “every day at 9am” or “respond whenever a new issue is filed.” Go to Waker details → Triggered Tasks → New and configure:
  • Task name and description — clear enough that the Waker can act on it directly.
  • AI model — which model to use.
  • Working directory — the local directory, repository, or project workspace where the task should run.
  • Trigger type (up to 5, mix and match):
    • Scheduled — one-off, recurring, or complex schedules (daily 9am, every Monday, first of each month).
    • Event-driven — listen for GitHub Issue / PR / comment activity.
    • API trigger — invoke tasks from external systems via HTTP. Best for CI pipelines, webhooks, and internal platform integrations.
  • Max runs / expiration date (optional) — cap how many times or how long a task can run.
Once saved, the Waker runs on the cadence you set. You can pause, resume, run a one-off test, or review run history at any time.

​
Trigger a task via API

The QoderWake API authenticates with a PAT (Personal Access Token). Every request must include a valid PAT in the HTTP header. Obtain a PAT:
1

Sign in to the Qoder console

Open the Qoder console and log in.
2

Open Service Integrations

Navigate to Personal Settings → Service Integrations.
3

Create a new token

Click Create New Token, then set a name and an expiration date.
4

Copy and save the token

Copy the generated token (shown only once). A PAT starts with the pt- prefix, formatted as pt-your-token-here.
Do not commit a PAT to code repositories or share it publicly.
Bearer header format: pass the PAT as a Bearer token in the Authorization header of each request. 
Authorization: Bearer pt-your-token-here
Invocation example: use the curl request below to trigger a specific automated task. <auto_generate_invoke_key> is the invocation key generated when the task is created and is shown on the task detail page. 
curl -X POST 'https://api.qoder.com/v1/qoderwake/automation/invoke/<auto_generate_invoke_key>' \
  --header 'Authorization: Bearer pt-your-token-here' \
  --header 'Content-Type: application/json' \
  --data '{
    "prompt": "your appended prompt here"
  }'
The prompt field in the request body is appended for this invocation and is merged with the task description before being passed to the Waker.