Schedule Task — One-Off Scheduled Actions

Create and manage one-off scheduled tasks that run at a specific date/time. Unlike routines (which repeat on cron), scheduled tasks execute once and are done.

When to Use

• User wants to schedule something for a specific time: "posta no LinkedIn sexta 10h"
• User wants to run a report later: "roda o financial pulse amanha as 8h"
• User says "agenda pra", "schedule this for", "run at", "agendar tarefa"
• User wants to list or manage pending tasks: "quais tarefas agendadas?"

API Reference

The dashboard backend exposes these endpoints:

Task Types

Agents

Workflow

Creating a Task

1. Understand the request — extract what, when, and how:

   • What: the action to perform
   • When: date + time (convert relative dates like "amanha", "sexta" to absolute ISO 8601 in UTC)
   • Type: skill, prompt, or script
   • Agent: which agent should handle it (if applicable)

2. Confirm with user — show a summary before creating:

   Copy

   Agendar:
   - Nome: Post LinkedIn sobre Evolution Summit
   - Tipo: skill
   - Payload: social-post-writer LinkedIn post about Evolution Summit April 14-16
   - Agent: @pixel
   - Quando: 2026-04-11 13:00 (BRT)
   
   Confirma?
   

3. Create via API:

curl -s -X POST http://localhost:8080/api/tasks \
  -H "Content-Type: application/json" \
  -b "session=..." \
  -d '{
    "name": "Post LinkedIn sobre Evolution Summit",
    "description": "LinkedIn post promoting the Evolution Summit event",
    "type": "skill",
    "payload": "social-post-writer LinkedIn post about Evolution Summit April 14-16",
    "agent": "pixel-social-media",
    "scheduled_at": "2026-04-11T16:00:00Z"
  }'

Important: Convert BRT times to UTC by adding 3 hours. The user's timezone is America/Sao_Paulo (UTC-3).

Listing Tasks

# All pending tasks
curl -s http://localhost:8080/api/tasks?status=pending -b "session=..."

# All tasks
curl -s http://localhost:8080/api/tasks -b "session=..."

Present as a clean table:

ID | Nome                          | Tipo  | Agendado        | Status
---|-------------------------------|-------|-----------------|--------
1  | Post LinkedIn Summit          | skill | 11/04 13:00 BRT | pending
2  | Financial Weekly extra         | script| 12/04 08:00 BRT | completed

Running Now

If user wants to execute immediately:

curl -s -X POST http://localhost:8080/api/tasks/<id>/run -b "session=..."

Cancelling

curl -s -X DELETE http://localhost:8080/api/tasks/<id> -b "session=..."

Date Parsing Rules

The user speaks Portuguese. Common patterns:

• "amanha as 10h" → tomorrow at 10:00 BRT → +1 day, 13:00 UTC
• "sexta 15h" → next Friday at 15:00 BRT → Friday 18:00 UTC
• "segunda de manha" → next Monday at 09:00 BRT → Monday 12:00 UTC
• "hoje a noite" → today at 21:00 BRT → today 00:00+1 UTC
• "daqui 2 horas" → now + 2 hours

Always confirm the parsed date with the user before creating.

Examples

"Agenda um post no LinkedIn pra sexta as 10h sobre o Summit"

{
  "name": "Post LinkedIn — Evolution Summit",
  "type": "skill",
  "payload": "social-post-writer LinkedIn post about Evolution Summit April 14-16, 2026",
  "agent": "pixel-social-media",
  "scheduled_at": "2026-04-10T13:00:00Z"
}

"Roda o community pulse amanha as 8h"

{
  "name": "Community Pulse (manual)",
  "type": "script",
  "payload": "custom/community_daily.py",
  "agent": null,
  "scheduled_at": "2026-04-10T11:00:00Z"
}

"Manda um resumo pro Telegram amanha 14h com status dos projetos"

{
  "name": "Resumo projetos via Telegram",
  "type": "prompt",
  "payload": "Check the status of all active projects (Evo AI, Evolution Summit, Evo Academy) and send a summary via Telegram to Davidson",
  "agent": "atlas-project",
  "scheduled_at": "2026-04-10T17:00:00Z"
}

Important Notes

• Tasks are one-off. For recurring actions, use create-routine skill instead.
• The scheduler checks for pending tasks every 30 seconds.
• Tasks run in background threads — they won't block the scheduler.
• Results are saved in result_summary and visible in the dashboard at /tasks.
• Always confirm with the user before creating a task.
• Convert all times from BRT (UTC-3) to UTC before sending to the API.