Outlook
On this page
Purpose
Outlook runs actions from a Composio-connected Microsoft 365 account. Agent Core can use the enabled Outlook tools, or a normal flow can run one selected action.
When to use it
- Search or send email.
- Read or manage calendar information.
- Work with contacts or tasks when the connected toolkit offers those actions.
Required setup
- Create a Composio project API key in Composio Dashboard > Platform > your project > Settings > API Keys. Follow Create a Composio API Key for the required permissions. Add it in the component or select a saved Arkus Credential. Never put it in prompts, examples, or images.
- Use the component authorization flow to connect the Outlook account. This provider grant is separate from the Composio key, and it is what lets the actions actually run. The auth config chooses OAuth or API-key authentication and the scopes requested.
- The Composio key loads the toolkit's actions and their fields, so you can review and select them. Selected actions become separate Agent tools. The Outlook toolkit page shows the catalog beyond this guide. The examples below are not exhaustive.
- Missing actions? Check the Composio key and its permissions first, then reconnect or refresh the account.
How to use it
Tool Mode
- Add Outlook, select the saved Composio Credential, and complete the account connection.
- Enable Tool Mode, keep only the Actions the Agent needs, and connect the tool output to Agent Core.
- Test a read-only action before enabling changes to mail, calendars, contacts, or tasks.
Normal mode
- Choose one Action and provide its inputs.
- Connect the DataFrame output to the next step.
Configuration
| Setting | What it controls | Recommended starting point |
|---|---|---|
| Composio API Key | Connects Arkus to Composio and loads the action schema. | Select a saved Credential. |
| Action | Chooses one available Outlook action in normal mode. | Start with a read action. |
| Auth Mode | Appears once the toolkit's authentication options are known. | Use the mode required by the authorized account. |
| Actions | Selects loaded actions that become separate Agent tools in Tool Mode. Builder can curate any relevant subset. Without a selection or component default, Arkus starts with the first five fetched actions. | Review the initial set and keep only the actions the Agent needs. |
| Entity ID | Falls back to naming the Composio user when your Arkus sign-in cannot identify one. A deployed flow always uses the owner's account. | Leave default in normal Builder use. |
Expected result
Tool Mode gives Agent Core the enabled Outlook tools. Normal mode returns a DataFrame. A deployed flow requires a saved owner Composio Credential and exactly one active owner account. If the account is missing, disabled, or ambiguous, Arkus asks the owner to reconnect before execution. Authorization failures during an action return a provider error.
Reference details
Attachment fields appear only when the selected live action schema supports an upload. Keep Agent permissions narrow, especially for send, delete, and calendar-changing actions.