• AUTOMATION
  • MONITORING
  • CONTROL
  • HUMAN

How to schedule recurring cron tasks with your AI

Connect Trigger.dev to your AI client to turn plain English instructions into active background jobs.

Ask AI about this page

Short answer

How can I automate recurring tasks with my AI?

You tell your agent when you want a job to run, and it uses Trigger.dev to register that schedule. You'll get automated background processes that run exactly when you specified.

Task outcomes

Where your automation lives.

Your AI handles the scheduling logic so you don't have to write cron syntax.

AUTOMATION

New cron schedules

The AI creates recurring jobs based on your timing. These run in the background via Trigger.dev.

MONITORING

Active job lists

Your agent can pull a list of everything currently scheduled. You'll see exactly what is running.

CONTROL

Schedule oversight

The AI manages the lifecycle of your tasks. It keeps track of what you've set up so you stay organized.

HUMAN

Manual oversight

You decide when a schedule is no longer needed. The AI handles the setup, but you maintain control.

The workflow

What your AI does when a task arrives.

The AI translates your intent into specific API calls to manage your background workload.

  1. Analyze timing

    Your agent looks at your request to figure out the specific cron pattern needed for the job.

    create_schedule

  2. Register the job

    The AI sends the schedule details to Trigger.dev to start the background process.

    create_schedule

  3. Verify schedules

    The agent checks the existing list of jobs to ensure there are no conflicts or duplicates.

    list_schedules

  4. Confirm status

    The AI reports back to you that the schedule is active and ready to run.

    list_schedules

Try it

Copy these to start.

Use these prompts to kick off your automation.

Starting points

Swap out the job names and timing details to match your actual needs.

Trigger.dev Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_DiUWSJJpaOcItA1IYDF4PWPoPmppnbeSDfcRQ8O3/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Trigger.dev capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "triggerdev-background-tasks-jobs-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_DiUWSJJpaOcItA1IYDF4PWPoPmppnbeSDfcRQ8O3/mcp"
    }
  }
}
Copy into chat04

  • Create a new cron schedule in Trigger.dev to run a cleanup job every Sunday at midnight.

  • List all my current Trigger.dev schedules so I can see what is running.

  • Set up a recurring task to ping my webhook every hour on the hour.

  • Check my existing schedules to see if the database backup job is still active.

  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Start here

Connect Trigger.dev once, then ask.

Just link your account once. Your credentials stay encrypted and secure, and you can immediately start managing jobs through your AI client.

Connect Trigger.dev to your AI

FAQ

How this task behaves

  • 01

    Can the AI delete my existing schedules?

    No. The current tools only allow the AI to create and list schedules.

  • 02

    Does the AI run the actual code in the background jobs?

    No. The AI only manages the schedule. The actual job execution happens within Trigger.dev.

  • 03

    Can I ask the AI to change the timing of a job I already made?

    The AI can create a new schedule, but it cannot modify an existing one with the current tools.

  • 04

    How does the AI know what schedules already exist?

    It uses the list tool to pull your current schedule data before taking any new actions.

  • 05

    Can the AI see the logs of my completed jobs?

    No. The AI can only see the schedules themselves, not the execution logs or output.

  • More questions about Trigger.dev? See everything the Trigger.dev Connector can do

Connect Trigger.dev to Claude, Cursor, ChatGPT & more