Run an autonomous outreach agent

A Task is an AI worker you schedule once and let run on its own. This recipe creates a recurring Task that uses live web research to find leads, drafts personalized outreach email, and surfaces each run for your approval before anything goes out.

Tasks are your AI workforce. Each scheduled execution is a Task Run you can inspect. With approval_mode: "supervised", runs that want to act pause as needs_input and show up in your dashboard for sign-off. See Tasks.

Recipe

Create the outreach Task

The prompt is the agent’s standing instructions. trigger_type: "cron" plus a cron_expression schedules it; approval_mode: "supervised" means it won’t send anything without you.

curl -X POST https://api.crevio.co/v1/tasks \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Weekly lead outreach",
    "agent": "business",
    "trigger_type": "cron",
    "cron_expression": "0 9 * * 1",
    "timezone": "America/New_York",
    "approval_mode": "supervised",
    "delivery_methods": ["email"],
    "prompt": "Each Monday, use web research to find 10 local businesses — dentists, law firms, and restaurants — whose websites look outdated or aren't mobile-friendly. For each, draft a short, personalized outreach email pitching our web-design studio's redesign service. Summarize who you found and attach the drafts for my review."
  }'

{
  "id": "task_out01",
  "object": "task",
  "name": "Weekly lead outreach",
  "agent": "business",
  "trigger_type": "cron",
  "cron_expression": "0 9 * * 1",
  "approval_mode": "supervised",
  "delivery_methods": ["email"],
  "active": true,
  "next_run_at": "2026-06-22T13:00:00Z",
  "total_runs_count": 0
}

agent: "business" is the default operator agent (use engineering only for code/site builds). The cron 0 9 * * 1 runs every Monday at 09:00 in the given timezone.

Read the Task's runs

Every execution creates a Task Run. List them to see what the agent did and what’s awaiting you.

curl "https://api.crevio.co/v1/task_runs?task_id=task_out01" \
  -H "Authorization: Bearer YOUR_API_TOKEN"

{
  "object": "list",
  "data": [
    {
      "id": "trun_run01",
      "object": "task_run",
      "task_id": "task_out01",
      "status": "needs_input",
      "summary": "Found 10 local businesses; drafted 10 outreach emails awaiting approval.",
      "credits_consumed": 42,
      "tool_calls_count": 18,
      "started_at": "2026-06-22T13:00:02Z"
    }
  ],
  "has_more": false
}

A status of needs_input means the supervised run is paused for your review.

Approve a supervised run

Supervised runs are reviewed and resumed in the dashboard — that’s where the drafts and the agent’s reasoning are shown for interactive approval. To resolve a run’s state programmatically, PATCH /task_runs/{id}:

curl -X PATCH https://api.crevio.co/v1/task_runs/trun_run01 \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "status": "completed" }'

Interactive input (editing a draft, approving a send) happens in the dashboard and via notifications. The API PATCH resolves the run’s status; it doesn’t carry an approval payload.

Variation: trigger on an event instead of a schedule

Instead of cron, fire the agent when something happens in your account. Use trigger_type: "event" with event_conditions — for example, kick off a follow-up sequence whenever an order is paid.

curl -X POST https://api.crevio.co/v1/tasks \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Post-purchase follow-up",
    "agent": "business",
    "trigger_type": "event",
    "approval_mode": "autonomous",
    "delivery_methods": ["email"],
    "event_conditions": { "event": "order.paid" },
    "prompt": "When an order is paid, draft and send a warm thank-you email to the client with next steps and a link to book their project kickoff call."
  }'

Event-triggered Tasks and Webhooks both react to platform events, but they’re different tools: a webhook notifies your server so your code acts; an event Task wakes up Crevio’s AI to act on your behalf. See Events for the subscribable event list.

Next steps

Tasks

Full Task model — triggers, agents, approval modes.

Events

Internal and third-party triggers for event Tasks.

AI content generation

The web research tools your agent uses under the hood.

Usage & billing

How Task runs consume credits.

Getting started

AI & agents

Core concepts

Integrations

Recipes

Run an autonomous outreach agent

Recipe

Variation: trigger on an event instead of a schedule

Next steps

Tasks

Events

AI content generation

Usage & billing

​Recipe

​Variation: trigger on an event instead of a schedule

​Next steps

Tasks

Events

AI content generation

Usage & billing

Recipe

Variation: trigger on an event instead of a schedule

Next steps