App Connectors

A connector is APIANT's adapter for a single service — Salesforce, Stripe, Mindbody, your in-house API. Each connector defines the triggers (events that service emits) and actions (operations it performs) that Claude can use in your automations, handles authentication, and lets each user connect their own account. The catalog ships with hundreds of connectors; Claude can build new ones on demand.

Authentication flavors

Every connector uses one of three auth styles, matched to how the vendor exposes its API:

• OAuth — vendor-managed login. The user clicks Connect, authenticates with the vendor in a popup, and approves access. The connector stores access and refresh tokens, and the platform refreshes them automatically when they expire. Used by services that gate API access behind a user account: Salesforce, HubSpot, Google, Slack, most major SaaS.
• API key — the user pastes a static key (and sometimes a secret, account ID, or region) into a connection dialog. The credentials live in the keyvault and ride along on every request. Used by services that issue per-account keys: Stripe, OpenAI, Anthropic, most modern API-first products.
• No credentials — public APIs with no auth at all. The user creates a connection just to label it; nothing is stored. Used for public data feeds and internal services that already sit inside a trusted network.

Claude picks the right flavor when building a new connector based on the vendor's API documentation. You can also tell Claude which to use if you already know.

Register an OAuth app with a vendor

OAuth registration is the manual chore in front of every OAuth-only integration: log into the vendor's developer portal, find the "create app" button, fill in callback URLs, pick scopes, copy out a client ID and secret. Every vendor does it slightly differently, and the differences are what make it slow.

Ask Claude to register an OAuth app for a vendor. Claude:

• Looks the vendor up in the APIANT catalog and reads the connector's required scopes and redirect URI directly from the catalog, so it knows what to ask for before opening the portal.
• Opens the vendor's developer portal in dev-browser and clicks the unambiguous next steps (create app, paste redirect URI, check scope boxes, submit).
• Pauses and tells you exactly what to do at the human gates the vendor enforces: login, MFA, admin approval, sandbox-vs-production org selection, accepting terms.
• Captures the resulting client_id and client_secret from the success page and saves them straight into the keyvault under the connector's pre-existing slot names.
• Opens the connection-test dialog in App Connections so you can confirm the new credentials work end-to-end.

You do this once per vendor per tenant. After that, every automation built against that vendor reuses the same credentials.

Example: "Register a HubSpot OAuth app." Claude finds the HubSpot connector, reads the scopes the connector expects, opens developers.hubspot.com, walks you through login and app creation, and saves the credentials when you finish.

Related

• Building with the Plugin — every skill the plugin offers, organized by task.
• API Authentication — how the keyvault and OAuth fit into a typical first build.
• Build — building a brand-new connector from a vendor's API.
• Edit — changing an existing connector or automation.