Build a connector, action or trigger

Plan: Enterprise

Claude Code can build an app that is not in the catalog, or add a trigger or action to an app that is. It reads the vendor's API documentation, creates the connector and operations for your account, runs each operation against your connected account until the output is right, and leaves the result private to you. There is no visual editor for connectors: Claude makes every change, and you supply credentials and confirm results.

Who can build connectors

Build an operation for an app that exists

Ask for the operation in plain English and name the app, for example: "Add an Asana action that sets a task's dependencies."

1. Claude checks what the app already has, so it does not build a duplicate.
2. Claude reads the vendor's documentation for that endpoint and asks you for anything it cannot determine, such as which of two similar endpoints you mean.
3. Claude calls the endpoint once with your connected account to get a real response before it defines the output fields.
4. Claude defines the inputs, the request, and the output fields, then runs the operation against your account. If the output is wrong it fixes the operation and runs it again.
5. Claude reports the output of the final run. You can then use the operation in an automation.

Operations can do more than one API call. A single action can look something up, branch, call a second endpoint, loop, and upload files, and still appear as one step in an automation.

Build an app that is not in the catalog

Ask for the app, for example: "Integrate Acme Scheduling. The API docs are at https://developer.acme-scheduling.com/reference."

1. Check the catalog. Claude searches by the app's name and then by what it does, because the app may be listed under a former or parent-company name.
2. Choose operations. If you did not list the operations you want, Claude reads the vendor's API reference and returns a ranked list of the triggers and actions worth building, focused on the app's main records (contacts, orders, tickets and similar). It builds nothing until you choose. If the docs cannot be reached, Claude stops and asks for the API specification or a page that loads without JavaScript.
3. Create the connector. Claude works out how the API authenticates: API key, OAuth 2.0, OAuth 1.0a, no credentials, a token exchange, or a request-signing scheme.
4. Connect your account. You connect your own account on the new app. For OAuth, that usually means registering an app on the vendor's portal first; see Use your own OAuth app or API keys.
5. Build and test each operation, as in the previous section.

Triggers

Claude builds a trigger to match how the vendor delivers the event:

Claude reads the vendor's webhook documentation before concluding an event has no webhook. See Webhook triggers and Polling triggers.

Who can see what you build

Connectors and operations you build are private.

• They are visible to the person who built them. Another user on the same account does not find them when building an automation.
• Automations that use them keep running regardless of who views them.
• They are not listed in the shared APIANT catalog. Listing an operation for every customer is an APIANT review, not a step you or Claude take.

When Claude lists the app's operations, your private ones are reported separately as hidden operations, by name and type.

Change an operation

Ask Claude to change it, for example: "The Acme 'Find booking' action should also accept a date range." Claude edits the request, the logic, the inputs and outputs, dropdowns or settings, and runs the operation again. Operation changes are versioned, so you can ask Claude to compare the current version with an earlier one.

Troubleshooting

Next steps

• Use your own OAuth app or API keys
• Apps and connectors
• Working with Claude
• Testing an automation