Trigger.dev
Developer platform for background jobs and scheduled tasks in TypeScript (Node.js). Write jobs as code, Trigger.dev handles execution, retries, observability, and orchestration. Designed for long-running tasks (minutes to hours) that do not fit in serverless function timeouts. Open-source orchestration layer with cloud or self-hosted deployment. Built for engineers who want durable execution without managing queues or workers.
Official site ↗Why it ranks here
Best developer experience for code-first background jobs. Write TypeScript, Trigger.dev runs it reliably with retries, logs, and alerting. No workflow UI to click through; everything is code. For teams already writing Node.js and want durable execution without managing infrastructure, Trigger.dev is faster than building with queues (SQS, RabbitMQ) or cron.
Where it sits
Ranked ninth because it optimizes for developers writing code, not operators building visual workflows. n8n and Pipedream have visual workflow builders. Trigger.dev is pure code. For GTM engineering teams with strong dev capacity, this competes with Pipedream; for teams that need visual workflows, n8n or Make ranks higher. Use Trigger.dev when jobs are complex TypeScript logic, not simple API integrations.
How GTM Engineering teams use it
GTM engineers write background jobs: import lead list (read CSV, call enrichment APIs, write to CRM, takes 30 minutes), sync CRM to warehouse (extract full account list via API, transform, load to Snowflake, takes two hours), send batch email campaigns (query CRM, personalize emails, send via SendGrid, track opens). Jobs are TypeScript functions; Trigger.dev handles execution on schedule or via webhook trigger. Teams use this for tasks too slow for serverless (over 15 minutes) or too complex for visual workflow tools (multi-step transforms with custom business logic).
In-depth notes
Open-source orchestration (Apache 2.0) with cloud or self-hosted execution. Cloud pricing is per compute time; free tier includes 100 hours per month (as of mid-2026). Self-hosted deployment is Docker or Kubernetes. Jobs are TypeScript; import Trigger.dev SDK, define job function, deploy. Execution engine handles retries (configurable backoff), logs per run, and observability dashboard. Integrations exist for common APIs (Slack, OpenAI, Resend) but the value prop is writing custom code, not using pre-built actions. Learning curve: if you write TypeScript, Trigger.dev is simple; if you do not, this is not the tool. For GTM teams, use Trigger.dev when visual workflow tools (n8n, Make) are too limiting and you need custom business logic. Otherwise, Pipedream is easier for event-driven tasks, n8n is easier for visual workflows.
Best for
Developers writing long-running TypeScript jobs; tasks too complex for visual workflow tools
Avoid if
Non-technical users building automations; need visual workflow builder or pre-built integrations
The rest of Workflow automation
n8n Leader Open-source workflow automation with AI nodes, self-hostable, developer-leaning. The builder favorite. #2 
Make Leader Visual automation with complex branching, routers, and error handling. Power user favorite. #3 
Zapier Leader Market-standard automation with 6,000+ app integrations. Easiest for non-technical users. #4 
Pipedream Strong Code-first automation with pre-built actions and generous free compute. Developer favorite for custom logic. #5 
Windmill Strong Open-source workflow engine with script-first design and visual UI. Self-hostable, Git-native. #6 
Relay.app Strong Human-in-the-loop workflows with AI steps. Simpler than Zapier, built for collaboration. #7 
Bardeen Situational Browser-based automation with AI copilot. Desktop app, local execution, built for repetitive web tasks. #8 
Activepieces Situational Open-source n8n alternative with self-hosting and visual builder. Growing connector library. #10 
Gumloop Situational AI-first automation with visual builder. Drag-and-drop AI nodes, API calls, and browser actions. #11 
Latenode Situational Low-code automation with JavaScript code steps. Visual builder + custom logic, affordable pricing. #12 
Lindy Niche AI agent automation with conversational triggers. Emerging, built for personal productivity and GTM tasks. Learning guide
Setup
Install Trigger.dev SDK via npm, write your first job function in TypeScript (define input schema and job logic), test it locally with the dev server, then deploy to Trigger.dev cloud.
First thing to build
Build a long-running CRM sync job: Define a scheduled trigger (daily at 3am), write TypeScript function that extracts all accounts from CRM API, transforms data, loads to Snowflake, with retries on API failures and Slack notification on completion.
What actually matters
- Job function (TypeScript with input/output types)
- Trigger (webhook, schedule, or event)
- Retry config (max attempts and backoff strategy)
- Observability dashboard (logs, traces, alerts per run)
Watch out
No visual workflow builder, everything is code.