---
title: Getting Started
product: vercel
url: /docs/connect/getting-started
canonical_url: "https://vercel.com/docs/connect/getting-started"
last_updated: 2018-10-20
type: tutorial
prerequisites:
  - /docs/connect
related:
  - /docs/connect
  - /docs/integrations
summary: Learn about getting started on Vercel.
install_vercel_plugin: npx plugins add vercel/vercel-plugin
---

# Getting Started with Vercel Connect

Create your first connector in Vercel Connect and request runtime credentials for an agent workflow.

> **🔒 Permissions Required**: Vercel Connect

## Pre-requisites

- Access to a Vercel team and project where Vercel Connect is enabled
- A Slack workspace you can connect
- Team permissions to create connectors and link them to projects

## Create a connector with your Vercel project

- ### Open Connect in your team dashboard
  Open the [Connect page](https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fconnect\&title=Vercel+Connect) in the Vercel dashboard for your team.

- ### Create a Slack connector
  In **Connect**, create a connector and choose **Slack** as the connector type.

  When prompted:
  - Name the connector (for example, `acme-slack`)
  - Enable trigger forwarding if you plan to receive Slack webhooks

- ### Link the connector to a project
  Attach the connector to the Vercel project where your app or agent runs.

  Select at least one environment, such as production. Add more environments if your workflow runs in preview or development too.
  We recommend using separate connectors for all environments for enhanced security. This way, each environment has its own authorization grant, scopes, and audit trail, so a compromised token in one environment cannot be replayed against another.

- ### Scope token requests and request a runtime token
  When you request a token, scope it for the workload:
  - Set provider scopes only for the action you need
  - Add `installationId` when you need a specific installation
  - Add `resources` or `authorizationDetails` for provider-specific scoping
  Then request a token with the SDK or CLI:
  ```ts filename="app/lib/connect-token.ts"
  import { getToken } from '@vercel/connect';

  const token = await getToken('slack/acme-slack', {
    subject: { type: 'app' },
    installationId: 'inst_...',
    // Add provider-specific request options when needed.
    scopes: ['channels:read'],
    resources: ['channel:C123'],
  });
  ```
  ```bash filename="terminal"
  vercel connect token slack/acme-slack
  ```
  Do not persist runtime tokens in long-lived environment variables.

## Reference: CLI and other connector options

For teams that prefer CLI setup or OAuth connectors:

```bash filename="terminal"
vercel connect create slack --name acme-slack --triggers
```

```bash filename="terminal"
vercel connect create oauth --name acme-oauth
```

```bash filename="terminal"
vercel connect attach slack/acme-slack --project my-project --environment production
```

Trigger forwarding is Slack-only in Beta. A connector can have up to three trigger destinations.

## Next steps

- Review [Vercel Connect](/docs/connect) for concepts, limitations, and product boundaries
- Explore [Vercel Integrations](/docs/integrations) if you need marketplace integration installs
- Run `vercel connect --help` to review your current CLI surface


---

[View full sitemap](/docs/sitemap)