Vercel Quickstart
Send your first Vercel logs to Sazabi in 5 minutes
Vercel Quickstart
Get your Vercel logs flowing to Sazabi in 5 minutes.
Prerequisites
- Sazabi account
- Vercel account with Pro or Enterprise plan (log drains require a paid plan)
- At least one Vercel project deployed
Log drains are only available on Vercel Pro and Enterprise plans. If you are on the Hobby plan, you will need to upgrade before setting up this integration.
Step 1: Create a Vercel API token
Generate an API token in your Vercel account settings:
- Go to Vercel Account Settings > Tokens
- Click Create Token
- Give it a descriptive name like "Sazabi Log Forwarding"
- Set the scope to Full Account or the specific team you want to connect
- Copy the token and store it securely
The token needs read and write permissions to create log drains on your projects.
Step 2: Connect Vercel to Sazabi
- Log in to Sazabi and go to Settings > Data Sources
- Click Add Source and select Vercel
- Paste your Vercel API token when prompted
- If connecting a Vercel team, enter your team ID or slug (found in your team settings URL:
https://vercel.com/teams/YOUR_TEAM_SLUG/settings) - Select the projects you want to forward logs from
- Click Connect
Sazabi will create log drains on each selected project automatically.
Step 3: Verify logs are flowing
Trigger some activity in your Vercel project to generate logs:
- Push a change to your repository to trigger a new deployment, or
- Visit your deployed application to generate runtime logs
Then verify logs are arriving in Sazabi:
- Open a chat thread in Sazabi
- Ask: "Show me recent Vercel logs" or "What errors appeared in my deployments today?"
You should see logs appear in Sazabi within 1-2 minutes.
Vercel forwards build logs, runtime logs (console.log from serverless functions), edge logs, and static file access logs automatically.
Troubleshooting
If logs are not appearing:
- Verify your API token has the correct scope (Full Account or team access)
- Check that the log drain was created in Vercel: go to your project settings and look under Log Drains
- Confirm you triggered new activity after connecting (existing logs are not backfilled)
- Allow a few minutes for logs to propagate through the pipeline
Next steps
- Set up alerting to get notified about errors
- Create a chat thread to investigate issues
- Add more data sources to get a complete picture of your stack