Integrations / Vercel
Vercel
Cron jobs on your projects, exactly as deployed.
Why connect it
Vercel cron is defined in vercel.json and forgotten. The schedule and path are exact; whether it runs is usually unknown until something downstream breaks.
What you'll see
- Every project's cron definitions: schedule, path, enabled or not
- Run history from runtime logs where the API exposes it — and an honest 'schedules only' note where it doesn't
What the credential can and cannot do
Where to get it: Add: Vercel's own approve screen, scoped to the projects you choose. Token: vercel.com → Settings → Tokens, scoped to a team.
It grants: Read on projects and deployments.
It cannot: Cannot deploy or change settings. Removing a cron is a change to vercel.json — proposed as a pull request.
Whatever you connect lives in an encrypted cookie in your browser and nowhere else. Sign out and it's gone; revoke it at the provider and it stops working immediately.