Ömer Eker from ezier
Connect Overbooked to Vercel to keep task progress aligned with the code your team deploys. Link tasks to real pull requests, map staging and production, and use verified deployment events to update statuses through your task automation rules.
Here’s how to set up the connection and check your first delivery.
You’ll need manager access to your Overbooked workspace, a Vercel account with access to the team and project you want to connect, the associated repository, and a pull request for the task you want to track. Decide which environments represent staging and production. Start with one project and one task so you can check the complete workflow.
Open Integrations in Overbooked and choose Vercel. Follow the authorization flow, select your Vercel team, and review the requested read permissions before approving. Use your own Vercel account and the projects your workspace needs to track. You don’t need to create a Vercel integration or enter an Overbooked platform secret. After authorization, return to Overbooked to configure the connection.
Select the Vercel project and confirm its repository. Overbooked verifies the selected project against your connection. Check carefully if several Vercel projects share a repository, or if you manage multiple clients. The connection needs to identify the correct Overbooked workspace and project, Vercel account and project, and repository. This gives each deployment update a clear source.
Set the staging and production environments explicitly, then configure the corresponding rules in Task Automation. Use the mapping that matches your release process. A preview deployment should count as staging only when you have deliberately mapped it that way. Production updates also require verified production deployment evidence. For example, your team might move a task to a review stage after a successful staging deployment, then advance it again when the change reaches production. The resulting statuses depend on the rules you configure.
A workspace manager or the task’s assignee can attach the actual pull request to the task. Overbooked verifies the pull request against the repository, project, and workspace. It uses this explicit relationship to connect delivery evidence to the right task, rather than guessing from similar task titles. Check the repository and pull request number before continuing. If a task spans several pull requests, make sure your team’s acceptance checks cover the whole task.
Deploy through your normal Vercel workflow. Overbooked validates incoming deployment events and checks the deployment’s account, project, repository, and commit before applying matching automation rules. Duplicate events are handled to avoid repeating the same update. Confirm the task links to the correct pull request, the deployment contains the linked change, the deployment matches your environment mapping, and the task reaches the status defined by your automation rule. Keep your normal testing and acceptance checks. Deployment evidence helps track delivery; it doesn’t replace reviewing whether the feature works as expected.
The Vercel connection reads the project and deployment information needed for tracking. Your configured rules can change task statuses inside Overbooked. Review access before connecting client projects. Task and deployment links may expose project details to people who can access your workspace. Use the integration’s disconnect control when you want to stop the connection. Disconnecting should not be treated as deleting existing task links or deployment history.
Project missing: Check your Vercel account, selected team, and authorized project access.
Task didn’t update: Check the attached pull request, repository, environment mapping, and automation rule. Compare the deployment’s commit with the linked work.
Deployment failed: Open the deployment in Vercel, inspect the diagnostics, fix the reported problem, and redeploy through your usual process.
Connection stopped working: Check whether authorization or project access changed. For help, share the task, pull request, deployment link, expected status, and visible error. Leave out credentials and environment-variable values.
© 2026 Overbooked. All rights reserved.