Integrations / Dev

Vercel

Authorize your Vercel team and projects for deployment investigations. Bring the relevant account context into your conversations with Indie and your specialists.

Connect Vercel ↗

What you can work on

  • Failed deployment → reviewed investigation

Available actions depend on the connected account, provider permissions and the tools available for your request. Indie should explain when access or an action is unavailable.

Connect your account

  1. Open Connectors in your Indie workspace and find Vercel.
  2. Select Connect and complete the provider’s authorization flow. Use the account whose resources you want your workspace to access.
  3. Choose the resources and permissions offered by the provider, then return to Indie. Confirm the connection is active.
  4. Ask Indie for a specific task. Name the repository, channel, document or other resource when relevant.

This integration uses provider-specific configuration. If connection setup is unavailable, a workspace operator must finish the app’s authentication configuration first. Customers should authorize their own accounts.

Try it in chat

Investigate the latest failed deployment for my connected project. Explain the build error and suggest next steps.

Read and analysis tasks can run directly. External changes go through the applicable approval flow; review the proposed destination and content before approving.

Deployment investigations

Once the operator has configured the integration webhook and signing secret, a successful Vercel connection can establish a default failed-deployment rule. Check its setup status in Automations → Events.

A verified deployment.error event can ask a build specialist to read the logs and prepare a diagnosis. It does not automatically change code, redeploy or publish a response. Other Vercel event selections do not currently start investigations.

Operator setup
  1. Configure the product’s Vercel OAuth2 integration in Composio with its client ID, client secret and integration slug.
  2. Register https://indieterminal.com/api/events/vercel/integration as the integration Webhook URL and select Deployment Error.
  3. Set VERCEL_INTEGRATION_WEBHOOK_SECRET to the integration client secret on the app server, then deploy.
  4. Connect a customer account through Indie and verify a real signed event before treating monitoring as live.

Never put a client secret in a public URL, document or chat message.

Access and troubleshooting

Indie can only use resources accessible to the connected account. Missing results may mean the wrong account is connected, a resource was not shared, or authorization has expired. Reconnect through Connectors and retry with an exact resource name or URL.

You can disconnect the account in Connectors and revoke access with the provider. Disconnecting prevents future use through that connection; it does not undo actions already approved or delete reports already saved in Indie.