trigger-scheduled-tasks

Automate recurring tasks with cron-based scheduling using the Trigger.dev SDK.

1.8k|375|Updated Jan 15, 2025

Search Tags:#automation #multi-tenant #tasks #scheduling #timezone #cron #trigger.dev

Ready to run

npx skills add https://github.com/trycompai/comp --skill trigger-scheduled-tasks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trigger-scheduled-tasks
Source: https://github.com/trycompai/comp/tree/main/.agents/skills/trigger-scheduled-tasks
Command: npx skills add https://github.com/trycompai/comp --skill trigger-scheduled-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and management of scheduled tasks using cron expressions with Trigger.dev, enabling reliable recurring workflows.

Core Features & Use Cases

Define a scheduled task with an id and a run function.
Attach schedules declaratively (cron) or imperatively (runtime creates).
Handle timezones and multi-tenant use cases to run tasks across environments.

Quick Start

Create a scheduled task with an id and a run function, then attach a cron pattern and optional timezone to activate recurring executions.

Frequently Asked Questions about trigger-scheduled-tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I schedule recurring tasks across different timezones using Trigger.dev?▼

Schedule recurring tasks using cron patterns with Trigger.dev by defining a task id and run function, then attaching an optional timezone for timezone-aware executions across environments.

Does Trigger.dev support multi-tenant cron scheduling for recurring workflows?▼

Yes, multi-tenant cron scheduling is supported by attaching schedules imperatively at runtime, allowing each tenant to receive isolated recurring task executions.

How do I set up a scheduled task with cron expressions in Trigger.dev?▼

Create a scheduled task by defining an id and a run function, then attach a cron pattern declaratively or imperatively to activate recurring executions using the Trigger.dev SDK.

What is the difference between declarative and imperative schedule attachments?▼

Declarative schedules attach cron patterns statically during task definition, while imperative schedules are created dynamically at runtime to support multi-tenant use cases.

Can I run timezone-aware scheduled tasks across different environments and runtimes?▼

Yes, timezone-aware scheduled tasks run reliably across environments and runtimes by specifying an optional timezone alongside the cron pattern in the Trigger.dev SDK.