Connectors

A connector is APIANT's representation of an external system: how to authenticate to it, what events it can emit, and what operations you can run against it. The catalog ships hundreds of pre-built connectors. Every automation you build pulls from this catalog.

You name the system, Claude picks the connector

When you describe a workflow, you name the systems involved by the names you actually use:

> Sync new HubSpot contacts to Mailchimp.

Claude looks up HubSpot and Mailchimp in the catalog, picks the right connectors, and builds against them. You don't navigate a dropdown of supported apps; you ask, Claude checks.

If a system isn't in the catalog yet, Claude tells you and offers to build a new connector for it. See Building with the Plugin → App Connectors.

Auth you have to set up once

Every connector that talks to an external system needs credentials. You set them up the first time Claude builds an integration with that system:

• API key services — paste the key (or token, or PAT) into the keyvault when prompted. The fastest path; covers many services.
• OAuth services — Claude walks you through registering a developer application with the vendor (see Register an OAuth app with a vendor) and authorizing it. Slower the first time, but you only do it once per service.
• No credentials — some connectors talk to public services or APIANT's own surfaces and need no credentials at all.

After the first setup, the same credential carries every subsequent integration with that service. You don't paste keys for every automation.

See also

• Credentials — how stored credentials are scoped
• API Authentication — credential setup walked through with a real integration