Job Templates

Ready-to-use cron job templates for common use cases. Browse the in-app gallery or use the CLI/API.

TrigRun ships with 14 pre-built templates across 5 categories. The fastest way to create your first job is to browse the in-app gallery at trigrun.com/templates — pick a template, click "Use this template", and your job creation form is pre-filled.

You can also use templates from the CLI or API:

# Browse templates
trigrun templates list
trigrun templates list --category ai_agents

# Show full details for a template
trigrun templates show health-check-ping

# Create a job from a template (prompts for your URL)
trigrun jobs create --template health-check-ping --url https://yourapp.com/health --name "My Health Check"

API:

# List templates (no auth required)
curl https://api.trigrun.com/v1/templates

# Create a job from template
curl -X POST https://api.trigrun.com/v1/jobs \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "template_id": "health-check-ping", "name": "My Health Check", "request": { "url": "https://yourapp.com/health" } }'

The template pre-fills schedule, retry policy, request method, headers, and any other defaults the template defines — you only need to replace the endpoint-specific pieces.

These templates are ready to run. Replace the url with your endpoint and you're done.

Health check ping

Pings your /health endpoint every 5 minutes. Alerts you on failure. Good first job to test TrigRun with a real endpoint.

curl -X POST https://api.trigrun.com/v1/jobs \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "health-check",
    "kind": "cron",
    "schedule": {
      "cron": "*/5 * * * *"
    },
    "request": {
      "url": "https://api.yourapp.com/health",
      "method": "GET",
      "timeout_seconds": 10
    },
    "retry_policy": {
      "max_attempts": 2,
      "retry_on_statuses": [500, 502, 503, 504]
    }
  }'

CLI:

trigrun jobs create \
  --name health-check \
  --url https://api.yourapp.com/health \
  --method GET \
  --kind cron \
  --cron "*/5 * * * *"

Don't have a health endpoint yet? Use https://httpbin.org/get to verify TrigRun is working end-to-end before pointing it at your real service.

Daily data sync

Triggers a POST to your sync endpoint at 2 AM UTC every day. Useful for ETL pipelines, cache refreshes, or any nightly batch operation.

curl -X POST https://api.trigrun.com/v1/jobs \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "daily-data-sync",
    "kind": "cron",
    "schedule": {
      "cron": "0 2 * * *"
    },
    "request": {
      "url": "https://api.yourapp.com/sync",
      "method": "POST",
      "headers": {
        "Content-Type": "application/json",
        "Authorization": "Bearer secret://sync-api-key"
      },
      "body": "{\"source\": \"trigrun\"}",
      "timeout_seconds": 60
    },
    "retry_policy": {
      "max_attempts": 3,
      "retry_on_statuses": [429, 500, 502, 503, 504]
    }
  }'

This template uses secret://sync-api-key — store your API key as a secret so it never appears in plain text.

TrigRun evaluates cron expressions in UTC. If your team thinks in local wall-clock time, convert that intended local time to UTC before saving the job, then confirm the preview in the dashboard.

Weekly report

Posts to your report generation endpoint every Monday at 9 AM UTC. Common for digest emails, analytics summaries, or Slack recaps.

curl -X POST https://api.trigrun.com/v1/jobs \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "weekly-report",
    "kind": "cron",
    "schedule": {
      "cron": "0 9 * * 1"
    },
    "request": {
      "url": "https://api.yourapp.com/reports/weekly",
      "method": "POST",
      "headers": {
        "Content-Type": "application/json"
      },
      "body": "{\"type\": \"weekly_summary\", \"format\": \"email\"}",
      "timeout_seconds": 120
    },
    "retry_policy": {
      "max_attempts": 2,
      "retry_on_statuses": [500, 502, 503]
    }
  }'

CLI:

trigrun jobs create \
  --name weekly-report \
  --url https://api.yourapp.com/reports/weekly \
  --method POST \
  --kind cron \
  --cron "0 9 * * 1"

After creating a job

Trigger it immediately to verify your endpoint receives the request:

trigrun jobs run JOB_ID
# or
curl -X POST https://api.trigrun.com/v1/jobs/JOB_ID/run-now \
  -H "Authorization: Bearer $TOKEN"

Check the execution result:

trigrun executions list --job JOB_ID
# or
curl https://api.trigrun.com/v1/jobs/JOB_ID/executions \
  -H "Authorization: Bearer $TOKEN"

Add a failure alert so you know when something goes wrong — see Notifications.

Health check ping

Daily data sync

Weekly report

After creating a job

On this page