> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conduit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Receiving emails in Conduit

> Set up email forwarding to receive your company emails directly in your Conduit inbox

## Overview

Forward your company email addresses to Conduit so every conversation lands in one inbox, ready to track, tag, and reply to.

* **What you forward from**: any address on your connected domain, such as help@, support@, or sales@
* **What you forward to**: your workspace's inbound address, ending in `@inbound.postmarkapp.com`
* **Where to find your inbound address**: **Settings > Email**, then **Configure** next to your domain, section 3, Receiving emails
* **After forwarding is live**: tick **Inbound email forwarding is set up** in that same section

Works with Google Workspace, Microsoft 365, or any other provider.

<Note>
  This forwarding setup is required for Booking.com guest messages, even when your company mailbox is hosted by Gmail or Google Workspace. Forwarding the messages to the `@inbound.postmarkapp.com` address lets Conduit match them to the reservation and place them in the guest conversation. A connected Gmail mailbox does not support this Booking.com routing. See [Booking.com guest messages](/setup/channels/email/connect-email#bookingcom-guest-messages) for the complete processing flow and setup.
</Note>

## Google Workspace (Gmail)

<Info>
  This assumes you use Google Workspace (formerly called Google Apps) to manage your domain's emails.

  If your email provider is not Google, you can still set up email forwarding in different ways, such as with your domain registrar (e.g. [DNSimple](https://support.dnsimple.com/articles/email-forwarding/)) or your email provider (e.g. [Microsoft 365](https://learn.microsoft.com/en-us/microsoft-365/admin/email/configure-email-forwarding))
</Info>

1. Navigate to **Settings > Email** under Channels
2. Add your email with a business domain
3. Go to your Gmail routing configuration
   * You can find this here: **admin.google.com**
4. Add a new rule
   * Under [Default routing](https://admin.google.com/ac/apps/gmail/defaultrouting) select **Configure** or **Add Another Rule**
5. Set the recipient
   * In the dropdown, select **Single recipient** and type your support email address under **Email address**
6. Choose how inbound mail should be delivered. The two options behave differently, and only one of them uses the envelope recipient setting.

   <AccordionGroup>
     <Accordion title="Replace recipient: Conduit becomes the only destination">
       Check **Change envelope recipient**, then choose **Replace recipient** and enter your Conduit inbound address. Inbound emails will arrive in Conduit only, not in your existing Gmail inbox.
     </Accordion>

     <Accordion title="Also deliver to: Conduit is an additional destination">
       Select **Also deliver to** and add your Conduit inbound address. Leave **Change envelope recipient** unchecked. Inbound emails will arrive in both your existing Gmail inbox and Conduit.
     </Accordion>
   </AccordionGroup>
7. Set the members the rule will apply to. Scroll further down and choose **Perform this action on non-recognised and recognised addresses**
8. Click **Save**

<Info>
  If you have existing email routing rules they can sometimes conflict with ones you add for Conduit. For optimal reliability always reorder the Conduit ones to apply first.
</Info>

## Microsoft Outlook / Office 365

### Option 1: Admin Center Mail Flow Rules (Recommended for Organizations)

This method allows admins to set up forwarding for shared mailboxes or any user in the organization.

1. Go to the **Microsoft 365 Admin Center** at [admin.microsoft.com](https://admin.microsoft.com)
2. Navigate to **Admin centers** > **Exchange**
3. Select **Mail flow** > **Rules**
4. Click **+ Add a rule** > **Create a new rule**
5. Name your rule (e.g., "Forward to Conduit")
6. Under **Apply this rule if**, select **The recipient is** and choose your support mailbox
7. Under **Do the following**, select **Redirect the message to** and enter your Conduit inbound address (ending in @inbound.postmarkapp.com)
8. Optionally, to keep a copy in the original mailbox:
   * Click **+** to add another action
   * Select **Bcc the message to** and enter the original mailbox address
9. Click **Next**, configure any exceptions if needed
10. Click **Next**, then **Finish** to create the rule

### Option 2: Outlook Web App (Individual Users)

For individual users who want to forward their own mailbox:

1. Go to [outlook.office.com](https://outlook.office.com) and sign in
2. Click the **Settings** gear icon in the top right
3. Select **View all Outlook settings**
4. Go to **Mail** > **Forwarding**
5. Check **Enable forwarding**
6. Enter your Conduit inbound address (ending in @inbound.postmarkapp.com)
7. Optionally check **Keep a copy of forwarded messages** to retain emails in Outlook
8. Click **Save**

<Note>
  Some organizations disable user-controlled forwarding for security reasons. If you don't see the forwarding option, contact your IT administrator to set up forwarding via mail flow rules.
</Note>

### Option 3: Outlook Desktop App (Personal Rules)

1. Open Outlook and go to **File** > **Manage Rules & Alerts**
2. Click **New Rule**
3. Select **Apply rule on messages I receive** and click **Next**
4. Set conditions (or leave blank to forward all messages) and click **Next**
5. Check **redirect it to people or public group**
6. Click **people or public group** and enter your Conduit inbound address
7. Click **Next**, add any exceptions if needed
8. Name the rule and click **Finish**

<Warning>
  Desktop rules only run when Outlook is open. For reliable forwarding, use the Admin Center or Outlook Web App methods instead.
</Warning>

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Do I need to set up forwarding again for each address?">
    Yes. Every address you connect needs its own forwarding to Conduit, using the inbound address shown for that domain.
  </Accordion>

  <Accordion title="Do I need forwarding for a Gmail account?">
    No. Individual Gmail accounts connect through the **Gmail accounts** section of your email settings, authorized directly with Google. Forwarding applies to connected domains only.
  </Accordion>

  <Accordion title="Will emails still arrive in my existing inbox?">
    That depends on the option you choose. In Google Workspace, **Replace recipient** makes Conduit the only destination and requires **Change envelope recipient** to be checked. **Also deliver to** keeps mail arriving in your existing inbox as well, and does not use the envelope recipient setting at all. In Microsoft 365, add a **Bcc the message to** action pointing at the original mailbox to keep a copy.
  </Accordion>

  <Accordion title="Where do I find my inbound address?">
    Go to **Settings > Email**, click **Configure** next to your domain, and look under section 3, Receiving emails. It ends with `@inbound.postmarkapp.com`. The same inbound address is shown for every domain, so set up forwarding to it for each company email address.
  </Accordion>

  <Accordion title="Forwarding is set up but nothing is arriving in Conduit">
    Existing routing rules are the usual cause. If you already had rules in place before adding the Conduit one, they can intercept messages first. Reorder the Conduit rule so it applies before the others.
  </Accordion>

  <Accordion title="I cannot find the forwarding option in Outlook">
    Some organizations disable user-controlled forwarding for security reasons. Ask your IT administrator to set forwarding up through Exchange mail flow rules instead.
  </Accordion>

  <Accordion title="My email provider is not Google or Microsoft">
    Forwarding still works. Set it up through your domain registrar or your own email provider, pointing at the same Conduit inbound address.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.