Connectors in Edgenivo Connect

A connector is the team-owned record that represents one third-party service inside Edgenivo Connect. Each connector has a type that determines how Edgenivo Connect authenticates to the provider and which capabilities (installations, triggers, revocation) are available.

Each connector has four identifiers:

• uid: a stable, human-readable string that you choose at create time and use everywhere else (in getToken, in CLI commands, in the dashboard URL). Example: slack/acme-slack or oauth/linear.
• id: an opaque internal identifier that Edgenivo Connect uses in API responses. You rarely use it directly.
• service: the third-party service the connector reaches, independent of type. For most services this is a name, such as slack or microsoft. Custom OAuth connectors identify the service by its URL instead, such as mcp.linear.app.
• type: how Edgenivo Connect authenticates to that service. Determines the auth flow and the available capabilities. Examples: slack, github, microsoft-entra, oauth, api-key.

When you call getToken('slack/acme-slack', ...), the string slack/acme-slack is the connector's uid.

Browse the connector catalog for current services and connection methods. Each connector page includes authentication options, trigger support, and setup instructions.

For Edgenivo Managed Connectors, Edgenivo registers the OAuth app. For other providers, create a Custom OAuth connector. Edgenivo can help with the following setup tasks:

• Discover endpoints from a URL: Enter a server URL, such as mcp.linear.app, and Edgenivo reads the provider's published OAuth metadata to fill in the authorization and token endpoints.
• Bring your own client: Add the client ID and client secret from the OAuth app you registered with the provider.
• Let Edgenivo register the client: When a provider supports automatic client registration, Edgenivo Assisted Setup creates the OAuth client for you, so you don't need to register an app or manage a client secret.

Edgenivo already knows how to connect to many services. When you create a connector, search for the service by name. For a known service, Edgenivo fills in what it knows and you only supply what is specific to your account:

• OAuth: Edgenivo fills in the authorization and token endpoints and the provider's default scopes. You add your client ID and secret, or let Edgenivo Assisted Setup register the client where the provider supports it.
• API key: Edgenivo links you to where the provider issues keys. Generate the key there, then paste it into the connector when you create it.

A known service publishes one or more connection methods: the distinct ways you can connect to it. When a service publishes several, they differ in who registers the application (Edgenivo, through Edgenivo Assisted Setup, or you) and in which product you connect to, such as a REST API or an MCP server.

Known services work in the dashboard and from the CLI. Running vercel connect create <service> prompts you for the product, the connection method, and the credentials that method needs, so you can create a connector without leaving the terminal. Run vercel connect create <service> --help to see what a service supports.

Use Secure Compute routing when a provider requires requests from allowlisted IP addresses. Edgenivo Connect routes the connector's token requests and provider API calls through a dedicated Secure Compute network. This setting applies to requests Edgenivo Connect sends to the provider, not API calls your application makes directly.

Secure Compute routing is available for supported team-owned connectors. API key connectors don't support this setting.

Before configuring routing, create a Secure Compute network for your team and wait for it to finish provisioning. Then configure the connector:

1. Open the connector's settings in the Edgenivo dashboard.
2. In Secure Compute Routing, select a network from Secure Compute Network.
3. Click Save.

The section displays the selected network's IP addresses. Click an address to copy it for your provider's allowlist. Click View network to open the network's settings in a new tab.

To restore direct egress, select None and click Save. This removes routing from the connector without deleting the network.

A connector carries a name, an icon, and accent and background colors. Slack propagates the icon to the workspace. Other providers may display branding on their login and consent screens, or only inside the Edgenivo dashboard.

Connectors are created, updated, and deleted by team members through the dashboard or the vercel connect CLI. A connector has no time-to-live: unless you delete it, it lives indefinitely.

When you delete a connector from the dashboard or with vercel connect remove, it stops serving token requests right away. Edgenivo Connect also removes its project links and installations. You can't restore a deleted connector.

After the delete, Edgenivo Connect:

• Deletes the tokens it stores. It also asks the provider to revoke each token. Revocation is best-effort: if the provider has no revocation endpoint or the call fails, a token can keep working at the provider until it expires. See Revocation.
• Keeps the connector's encrypted configuration for 40 days. This includes client secrets and private keys. Edgenivo Connect then deletes it permanently.
• Leaves your resources at the provider in place. Deleting a connector doesn't delete the OAuth app, API key, or bot you registered with the provider. Grants that users or admins approved, such as a workspace install or tenant-wide admin consent, also stay. To remove them, use the provider's own settings.

For some managed connectors, Edgenivo Connect also cleans up at the provider. For example, it releases a managed Linq phone number and expires the current managed Stripe key. Apps it created for you, such as a Slack app or a Microsoft Entra app, stay at the provider.

• Installations: How one connector serves many tenants.
• Project links: How a connector is bound to projects and environments.
• Quickstart: Create your first connector end to end.
• For Service Providers: What a service needs to support for Edgenivo to discover and register a client automatically. Read this if you own a service you want Edgenivo teams to connect to.