One connection per service — write descriptions that lean on this
1 min
If your description uses Outlook for both reading AND sending, the wizard binds ONE Microsoft connection for everything email.
The wizard's consolidation pass collapses splits the user didn't ask for. Saying "read my Outlook unread email" and later "email me the summary" both bind to your single Microsoft connection — you don't get prompted for a second SMTP connector.
When DO you get a multi-provider plan? When you explicitly name two: "Read from my Gmail and send via SMTP for compliance." That's a deliberate split — the wizard respects it.
Similar logic across domains: "List my Google Calendar events and email me the schedule" binds Google for both calendar AND email (one Google grant covers both surfaces). Same for Microsoft (Outlook + Microsoft Calendar).
Live recipes need the desktop
This article is a static preview. The in-app Help sidecar inside Avery NXR can fire each step against your live project — install the desktop to use it interactively.