Walkthrough

Connect Platforms When There Is No Connector

When your AI agent needs to reach a platform that has no pre-built connector, you tell the agent which platform you need and it builds the connection for you.

12 minutesIntermediateAny model

Built-in connectors like Gmail and Calendar let you click "Connect" and authorize through the platform's own login screen. The connector handles everything after that. When no connector exists for the platform you need, you can still reach it through its API: a structured way for software to talk to that platform. You tell your agent which platform you want, the agent identifies the right kind of API credential, walks you through the setup, and writes the connection code for you.

Tell your agent which platform you need, and it builds the connection

1
No connector? Reach the platform's API directly
Most platforms have APIs, just like the ones connectors use behind the scenes.
2
Get the credential your agent asks for
Tell your agent which platform you want, and it tells you which settings page to open and walks you through the setup.
3
Describe what you want and the agent builds the connection
Describe what you want in plain language: which platform, which action, and where the data lives.
4
Ask the agent to test it with one real request
Now that the connection code and credential are in place, tell the agent to run the connection against one real, low-stakes item, like a dra...

A working connection between your AI agent and one real platform, built by telling the agent what you want.

Agent directions

Agent directions for Codex Computer Use

Use browser control to research the platform I named in my goal: find its API documentation, identify the right credential type and setup path for that platform, create the connection code, store the credential safely, and verify one low-stakes request.

Copy with member access

Understanding

Every connector is a pre-built API connection

When you click "Connect" on Gmail or Slack, the connector authorizes your account, manages your credentials, and sends structured requests to the platform's API. You never see the technical layer. Connectors only exist for a few popular platforms. For everything else, you reach the same kind of API yourself, with your agent handling the setup.

An agent request, API credential, connection code, and platform API shown as one flow.

Build the connection

1
No connector? Reach the platform's API directly
Most platforms have APIs, just like the ones connectors use behind the scenes. You need an API credential: a token or key from the platform's developer settings that identifies your account and defines what the connection can do. Tell your agent which platform you want, and it identifies the right credential type for you.
PromptResearch This Platform's APIOpen when you are ready to copy it.
Sign in as a member to copy this prompt.
Sign in
2
Get the credential your agent asks for
Tell your agent which platform you want, and it tells you which settings page to open and walks you through the setup. Treat any credential the same way you would treat a password: anyone who has it can act as you on that platform. Store it in a secure location your agent recommends, never in a chat transcript, public file, or code repository.
Tip: Some platforms require an approval review before the credential works. Others use OAuth, where you authorize through the platform's own login screen instead of copying a token. Your agent will check which authentication method your platform uses and tell you what to expect.
PromptWalk Me Through Getting the CredentialOpen when you are ready to copy it.
Sign in as a member to copy this prompt.
Sign in
3
Describe what you want and the agent builds the connection
Describe what you want in plain language: which platform, which action, and where the data lives. The agent writes the connection code and saves it for reuse. You review what it plans to do before it sends any requests.
PromptBuild the Connection CodeOpen when you are ready to copy it.
Sign in as a member to copy this prompt.
Sign in
4
Ask the agent to test it with one real request
Now that the connection code and credential are in place, tell the agent to run the connection against one real, low-stakes item, like a draft event or a test task. Check the platform to confirm the item showed up. From here, the agent can run this connection whenever you have new content. For anything going to a public audience, keep a review step where you approve before the agent publishes.
PromptTest With One Low-Stakes RequestOpen when you are ready to copy it.
Sign in as a member to copy this prompt.
Sign in