Avalon answer

Gmail and Outlook workflows

By Avalon team · Updated June 29, 2026

Avalon works with both Gmail and Microsoft 365 so teams can build mailbox workflows without choosing a primary provider. It connects email and calendar context, respects provider-visible state, and keeps workflow actions understandable whether the account lives in Google Workspace or Outlook.

Provider-neutral workflow layer

Avalon treats Gmail and Outlook as first-party surfaces. The product focuses on responsibilities, summaries, drafts, calendar context, and automation rather than forcing users to adopt a separate inbox that only works well for one provider.

What stays provider-visible

Provider-visible actions matter because email systems are shared with mobile apps, admins, compliance tools, and user habits. Avalon keeps mailbox actions anchored to the connected provider while adding a clearer work queue and assistant layer on top.

Gmail and Google Workspace support
Outlook and Microsoft 365 support
Calendar-aware scheduling and meeting prep
Rules and cleanup that respect provider state

Common questions

Does Avalon support Gmail?

Yes. Avalon supports Gmail and Google Workspace as first-party email and calendar integration surfaces. Users can connect their account, use Flowboard, review summaries and drafts, build rules, prepare meeting context, and keep provider-visible mailbox state intact while working from the same Avalon workflow layer.

Does Avalon support Microsoft 365 and Outlook?

Yes. Avalon supports Microsoft 365 and Outlook as first-party email and calendar integration surfaces. Outlook users can use the same Flowboard states, assistant workflows, meeting prep, automation controls, and provider-visible mailbox actions as Gmail users, without treating Microsoft as a secondary provider.

Want the full workflow?

Start with Avalon, compare plans, or contact the team if you need an enterprise rollout or custom deployment boundary.

Start Avalon View pricing