Setup · Non-Gmail email hosts

Use SideQuest if your team runs Microsoft 365 or Outlook.

SideQuest reads incoming POs from Gmail. If your team is on Microsoft 365, Outlook.com, or Exchange, you don't have to migrate. Forward your orders inbox to a dedicated Gmail account, label the forwarded mail, and configure Gmail to send replies from your real domain. About 10 minutes start to finish.

Why a workaround at all

SideQuest's Gmail integration uses the official Gmail API with a narrow scope (gmail.modify). A native Microsoft 365 integration via the Graph API is on the v0.10+ roadmap, but until then forwarding gets you the same end result with a 10-minute setup. The reply your buyer receives still comes from [email protected], not from a Gmail address.

The flow at a glance

1

Outlook forwards

A new PO lands in your orders@ inbox on Microsoft 365. Outlook auto-forwards a copy to a dedicated free Gmail you create for this.

2

Gmail labels

A Gmail filter applies the purchase-orders label to anything that came from the forwarded address. SideQuest watches that label.

3

Send mail as

When SideQuest drafts the reply, Gmail's "Send mail as" feature sends it FROM [email protected]. Buyers see a normal email from your real address.

Before you start

Step 1 Create a dedicated Gmail for SideQuest

Don't reuse a personal Gmail. Create a fresh one specifically for SideQuest so the label rules and forwarding don't tangle with your personal mail.

  1. Go to accounts.google.com/signup and create a free Gmail. Pick a name like [email protected] — it's an internal address, no customer will ever see it.
  2. Sign in to the new Gmail. Click the gear icon, then See all settings.
  3. Under the Labels tab, click Create new label. Name it purchase-orders (exactly that, lowercase, with a hyphen). Save.

Step 2 Turn on forwarding in Microsoft 365 / Outlook

Microsoft 365 ("classic Outlook on the web") and Outlook.com use the same forwarding UI.

  1. Sign in to outlook.office.com (for Microsoft 365) or outlook.live.com (for personal Outlook.com).
  2. Click the gear icon (top right) → View all Outlook settingsMailForwarding.
  3. Tick Enable forwarding.
  4. Paste the dedicated Gmail address from Step 1 into the Forward my email to field.
  5. Tick Keep a copy of forwarded messages. (You want a record on Outlook's side too.)
  6. Click Save.

If you're on the legacy Exchange Admin Center instead, the path is Recipients → Mailboxes → pick the mailbox → Manage email forwarding → Forward all messages.

Step 3 Add a Gmail filter to apply the purchase-orders label

Without a filter, forwarded mail lands in Gmail's inbox unlabeled and SideQuest never sees it.

  1. Open the dedicated Gmail. Click the gear icon → See all settingsFilters and Blocked Addresses.
  2. Click Create a new filter.
  3. In the To field, enter your dedicated Gmail address (e.g., [email protected]).
  4. Click Create filter.
  5. Tick Apply the label and pick purchase-orders.
  6. (Optional) Also tick Skip the Inbox if you don't want forwarded POs cluttering the Gmail inbox view.
  7. Click Create filter.

If only some incoming mail is real POs (some is internal noise, support emails, etc.), narrow the filter using From (your buyer domains) or Has the words (e.g., "purchase order"). Tightening the filter is far easier than fixing a mis-labeled PO after the fact.

Step 4 Set up "Send mail as" so replies come from your real domain

This is the step that makes the buyer's reply look professional. SideQuest drafts the reply in Gmail; this setting controls what email address that reply appears to come from.

  1. In the dedicated Gmail, click gear → See all settingsAccounts and Import.
  2. Next to Send mail as, click Add another email address.
  3. In the popup, enter your real customer-facing name (e.g., "Acme Distribution — Orders") and the real address (e.g., [email protected]). Untick Treat as an alias. Click Next Step.
  4. Enter the SMTP server settings:
    • SMTP Server: smtp.office365.com
    • Port: 587
    • Username: your full Microsoft 365 mailbox address (e.g., [email protected])
    • Password: the mailbox password. If your account has multi-factor auth on, generate an app password in Microsoft 365 instead of using your real password.
    • Secured connection: TLS
  5. Click Add Account. Gmail sends a verification code to that address. Open Outlook, grab the code, paste it back into Gmail's prompt.
  6. Back on the Accounts and Import page, find the When replying to a message setting and pick Reply from the same address the message was sent to.

Step 5 Connect SideQuest to the dedicated Gmail

Same flow as any other SideQuest install — just point it at the dedicated Gmail instead of a personal one.

  1. Run the SideQuest install. Install prompt walks you through it.
  2. When the Gmail OAuth step asks you to sign in, sign in with the dedicated Gmail you created in Step 1.
  3. The GMAIL_PO_LABEL in your .env should already be purchase-orders. If you used a different label name in Step 1, change it here.

Step 6 Test the full round trip

  1. Have a colleague or test account send a PO to your real [email protected] address.
  2. Wait 15-30 seconds for the forward to propagate.
  3. Check the dedicated Gmail. The message should appear with the purchase-orders label.
  4. In Claude Desktop, ask "list my incoming POs". The PO should appear.
  5. Ask Claude to draft the reply. Open the resulting draft in Gmail — confirm the From field shows [email protected] and NOT the dedicated Gmail.
  6. Send the reply. The buyer receives it from your real domain.
One subtle gotcha. Gmail's "Send mail as" requires your domain's SPF, DKIM, and DMARC records to allow Gmail to send on its behalf. Microsoft 365 mailboxes usually have SPF + DKIM set up by default, so this works without changes. If buyers report that your replies are landing in spam, the fix is a one-line addition to your SPF record: include _spf.google.com alongside your existing Microsoft 365 SPF entry. Ask your IT / domain admin or email [email protected] for the exact record syntax for your registrar.

FAQ

Will buyers see anything that gives away the Gmail in the middle?

No. With Send mail as configured, the From, Reply-To, and visible sender all show your real address. The Gmail account is invisible to the buyer.

What if my Microsoft 365 admin has blocked external forwarding?

That's common in regulated industries. Two options. (1) Ask the admin to whitelist forwarding to the one dedicated Gmail address — most will accept a single-recipient exception. (2) Use a Microsoft 365 mailbox rule that copies inbound mail to the Gmail address without flagging it as a forward. The Outlook UI calls this "Redirect" instead of "Forward." Functionally identical for SideQuest.

Can I use this with a shared mailbox in Microsoft 365?

Yes. Shared mailboxes in Microsoft 365 support forwarding the same way. The Send mail as step needs SMTP credentials for the shared mailbox — your admin can generate an app password.

Do attachments get forwarded?

Yes by default. PDFs, scanned images, EDI exports — all fine. Some Microsoft 365 attachment-scanning policies strip files over a size limit (usually 25 MB). If you process very large attachments (rare for POs), check your tenant's policy.

What about replies that need to thread with the buyer's original?

Gmail preserves the In-Reply-To and References headers when you reply, so the buyer's email client threads the reply correctly. SideQuest's draft uses the same headers as the original incoming PO, so threading works the same way it would for any reply.

Can I do this with a Microsoft 365 group inbox?

Group inboxes don't support external forwarding by default. Easiest fix: convert the group inbox to a shared mailbox, or set up a rule that auto-copies inbound group mail to the dedicated Gmail. Talk to your admin.

I'm not on Microsoft 365 — I'm on Gmail with a custom domain via Google Workspace. Do I need this at all?

No. Workspace is Gmail under the hood. SideQuest connects directly without any forwarding. Use the regular quick-start guide instead.

On cPanel / GoDaddy / Bluehost hosting?

The flow is similar but the forwarding UI is different. See the cPanel/GoDaddy/Bluehost walkthrough.