1.7 Connector: Reach External Systems and Authorize Access
A common situation: you want the agent to read supplier mail and book a meeting on its own. You open 【Explore】 to find Outlook, and it is not there.
That is not a fault. A Connector's availability depends on three layers, and authorization itself comes in three forms. This lesson covers what it is, which authorization applies, and what to do when it is missing.
What a Connector Is
A Skill supplies the method; a Connector supplies the channel. Without one, the agent can only work on what you have already handed over. With one, it can go and fetch, or write back.
Technically, some Connectors are built on MCP (Model Context Protocol) and others talk directly to a third-party API. You do not need to tell them apart: add it, complete the required configuration, and check an actual query result.
Three Kinds of Work It Enables
| Kind | Example |
|---|---|
| Read external information | Check supplier mail in an inbox, pull data from another system |
| Write to an external system | Create a review meeting in the calendar, write results back to a business system |
| Call models and services | Generate images or video, call an internal company API |
Three Forms of Authorization, Not One
For configuration and maintenance, see the demo in AOS Work: Connector.
Authorization depends on the service the Connector reaches. When you add a Connector, the page offers whichever form that service uses:
| Authorization form | What you do | Typical service |
|---|---|---|
| None required | Run a read-only query and check the result | Public data sources, internal endpoints without authentication |
| Account details | Fill in credentials in a secure form, submit, then run a read-only query | Services using an API key or fixed credentials |
| Browser authorization | Sign in and authorize on the external page, return, then run a read-only query | OAuth services such as Outlook, Gmail, Google Calendar |
After configuration, run a scoped read-only task, such as listing file names in a specified folder. Check the returned data against its source to verify the connection for this task.
In the interface, adding one takes three steps: review the resource in 【Explore】, confirm the add, then complete the external authorization.
For a Connector that requires credentials, enter and submit them in the authorization form on its detail page.
Adding, enabling, and authorizing are separate states. Complete the configuration on the detail page, then check the result of an actual task.
Three Gates: Exists, Open to You, Authorized
| Gate | Who decides | What you observe |
|---|---|---|
| Resource | Whether the platform provides this Connector | The whole category is absent from the list |
| Openness | Whether an administrator has published it and opened it to your account | The category exists, but you cannot see or add it |
| Authorization | Whether you completed the required configuration or authorization | The card reads "Unauthorized" or "Needs reauthorization" |
Only the third gate is yours to resolve. The first two require your administrator — connecting an external system means data moves, and that gatekeeping is normal governance in an enterprise environment.
Not in the Directory: A Four-Step Request
| Who | What they do | What you provide |
|---|---|---|
| You | Describe the business case | Which system, which problem, which data |
| You | State the access scope | Read only or read and write; any sensitive data involved |
| Administrator | Assess and open it to your account | Compliance material if required |
| You | Return to 【Explore】, authorize, and check the query result | Follow the card's prompts |
State the system name, the account to authorize, and the data you need to read or write.
Select a Connector in a Task
Open 【New Chat】 and use 【Add context】 → 【Choose connectors】 to select an added resource. Check its tag before sending. If a Skill is also needed, specify it and the data source in the task.
Complete configuration or authorization when the task requests it. The 【Enabled】 switch controls whether the resource is enabled; it does not replace account authorization.
Authorization During a Task
For completing requested information, authorizing a service, and continuing the original task, see Task Requests and Authorization.
Authorization does not only happen in 【Explore】. If a running task needs a service that is not yet authorized, or needs more information, the page pauses and shows a prompt. The sequence is fixed:
- Click the action button in the prompt.
- Fill in the form on the page, or complete the external sign-in.
- Return to the task; it continues automatically — you do not need to resend the message.
The difference from configuring in 【Explore】 is timing: setting it up in advance suits long-term, repeated use; authorizing inside a task suits a one-off access.
Maintain a Connection
Open the resource detail page from 【Explore】 and use its configuration or authorization options to maintain the account. Use the enabled switch to disable the resource, or 【Remove】 on the detail page to remove it. These are separate actions.
Summary
A Skill supplies the method; a Connector supplies the channel. Prepare the channel by adding and enabling it, completing the required authorization, and checking an actual query — and whether you can see it at all depends on the platform, your administrator, and you.
The next lesson covers Apps. They are also added from 【Explore】, but they open a business page rather than adding a capability to the agent.
1.6 Work: Combine Several Skills Into One Work Package
A single Skill covers one class of task. A full business chain needs several, and Work fixes that combination in place.
1.8.1 Library: So the Agent Can Read Your Files
Your files sit on your laptop, in your inbox, in SharePoint — and the agent can see none of them. Library fixes that.