Time-Trigger Your Workflows
Run any workflow at a specific future time, no cron hacks needed.
GitHub's `schedule` is for cron. WarpTrigger is for triggering a single, time-sensitive pipeline via `workflow_dispatch` with a simple, reliable API call. No YAML commits needed.
Trigger Anything, Anywhere, Exactly When You Need It
Schedule precise, fire-and-forget events in the future—set them relative to now (like "in 34 days 3 hours") or at specific times (like "9am New York time on August 1st"). Deliver via email, push, Telegram, webhooks, Zapier, GitHub Actions, and more. No servers, no cron boilerplate, just reliable execution.
Cron Isn't for Ad-Hoc Jobs
Using the `on: schedule` trigger for a single, non-recurring job is a clumsy and inefficient use of a cron-based system.
Wrong Tool for the Job
Cron is built for repetition (`0 0 * * *`), not for reliably handling a specific, one-off task like 'next Tuesday at 14:30:00 UTC'.
Slow, Commit-Based Changes
Changing a schedule requires a code commit and push. This is far too slow and cumbersome for dynamic, one-off tasks.
No Direct API for One-Off Tasks
There is no simple, external API to say 'run this workflow in 3 hours'. You're forced into manual runs or cron hacks.
An API-First Trigger for Your CI/CD Workflows
WarpTrigger gives you a simple, powerful REST API to programmatically schedule the execution of any GitHub Actions workflow.
We trigger your pipelines using the native `workflow_dispatch` event, allowing you to pass custom inputs and target specific branches.
Schedule your one-off pipeline runs programmatically from your own tools or scripts. Perfect for ad-hoc testing, deployments, or maintenance.
Schedule a critical, one-time job and trust that it will run. Our managed queue ensures your trigger is never lost, even if your own systems restart.
How to Schedule a Future GitHub Actions Run
Three simple steps to add API-driven scheduling to your CI/CD workflows.
1. Enable `workflow_dispatch`
Ensure your workflow can be triggered by a `workflow_dispatch` event in your workflow YAML file.
2. Create a Personal Access Token
Create a GitHub Personal Access Token (PAT) with `repo` scope to authorize the API call to trigger the workflow.
3. Schedule the Trigger via WarpTrigger
Make one API call to WarpTrigger, pointing to the GitHub API's `workflow_dispatch` endpoint, providing your PAT for auth, and specifying the branch, inputs, and exact future time.
Use Cases for Scheduled Pipeline Triggers
How developers and DevOps teams use WarpTrigger for reliable, one-off pipeline automation.
Scheduled Feature Branch Deploys
Schedule a deployment of a feature branch to the staging environment to happen at a specific time for QA review.
Ad-Hoc Data & Cleanup Jobs
Run a data migration or cleanup script via a pipeline at a specific, off-peak hour without using a cron schedule.
One-Time Security Audits
Trigger a deep security scan on your default branch to run over the weekend, just once, without a recurring schedule.
Temporary Environment Provisioning
From an external system, schedule a pipeline to spin up a temporary testing environment for a specific one-time need.