All integrations

Run agents with Outlook

Connect Outlook once, and every run that names it works in Outlook on the account you connected.

Connect OutlookOpens Settings → Connections in the console.

What an agent can do in Outlook

Read and send mail, and read contacts.

Jobs on Rush that use Outlook

Agents that use Outlook

How Outlook connects

Outlook is a built-in app: you sign in with your Microsoft account on its own page, through Rush's own app, so you register no OAuth app. The sign-in asks only for the scopes listed below, and the run's token reaches graph.microsoft.com, Microsoft Graph mail and contacts.

Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.

After that, a run that names outlook in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.

Scopes the sign-in asks for:

  • openid
  • profile
  • email
  • offline_access
  • https://graph.microsoft.com/User.Read
  • https://graph.microsoft.com/Mail.Read
  • https://graph.microsoft.com/Mail.Send
  • https://graph.microsoft.com/Contacts.Read
POST https://api.phoenix.so/me/connections

{
  "type": "app",
  "name": "outlook"
}

Whose Outlook account the agent uses

Your Outlook connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Outlook, and a run started with an API key uses the Outlook of the member who created the key.

To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own Outlook, and that agent's runs use their account and nothing else: never yours, never another user's.

More Productivity integrations

Frequently asked questions

How do I connect Outlook to Rush?

Open Settings → Connections in the console and connect Outlook, or send POST /me/connections with {"type":"app","name":"outlook"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.

Does every run get my Outlook account?

No. A run gets your Outlook connection only when it names it in connections ("connections": ["outlook"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.

What can an agent do in Outlook?

Read and send mail, and read contacts. 4 published jobs use it; this page lists them.

Can an agent only read Outlook?

Yes. A saved agent can name Outlook with an access level: read asks for reading alone, and send adds sending. An agent made from it signs in, and every run of it is refreshed, for that level alone.

Keep reading