Receiving email in Omnifox: webhook and forwarding
Connect your email as a channel and route inbound messages into the Inbox using Omnifox's webhook plus your provider's forwarding.
What you'll get
The Email channel turns every inbound message into a conversation inside the Omnifox Inbox, just like a WhatsApp or webchat message. For that to happen, your email provider has to forward incoming mail to the inbound webhook URL that Omnifox generates for you.
This guide is for anyone who already owns an email domain and wants customer replies to land in one place.
Requirements
- An Email channel created in Omnifox (with From Email and From Name set).
- An account with an inbound parse provider: SendGrid Inbound Parse or Mailgun Routes (the two Omnifox parses natively).
- Access to your receiving domain's DNS, or to your mailbox forwarding rules.
Steps
- Open Channels in the side menu and click Connect channel.
- Pick Email (SMTP / IMAP) from the channel list.
- Leave Provider as
SMTPand fill in the outbound details: SMTP Host, Port (usually587), Username, Password and Encryption (TLS). Set From Email and From Name — that address is the one that will receive mail. - Copy the Inbound Webhook URL shown on screen. It looks like
https://omnifox.io/api/webhooks/email. - Save the channel.
- In your inbound provider, point incoming mail at that URL:
- SendGrid: Settings → Inbound Parse → Add Host & URL. Enter the receiving subdomain (e.g.
inbox.yourdomain.com), paste the webhook URL, and add the MX record SendGrid gives you. - Mailgun: Receiving → Create Route → Forward action pointing to the webhook URL.
- SendGrid: Settings → Inbound Parse → Add Host & URL. Enter the receiving subdomain (e.g.
- If you only want to forward an existing mailbox (Gmail, Outlook), create an auto-forwarding rule to your provider's parse address.
How to verify
Send a test email to your receiving address. Within a few seconds a new conversation should open in the Inbox carrying the subject and body. The sender is stored as a contact.
If it doesn't work
- Nothing arrives: confirm the MX record points to your provider and that the receiving address exactly matches the channel's From Email. Omnifox routes inbound mail by the recipient address.
- It reaches SendGrid/Mailgun but not Omnifox: double-check the webhook URL for typos and that the domain resolves over HTTPS.
- Empty body: some forwards send HTML only; Omnifox prefers plain text when present, so enable "include plain text" at your provider.
Tips
- Use a dedicated subdomain (e.g.
support.yourdomain.com) so you never touch your primary mail MX. - Running several mailboxes? Create one Email channel per address and let each route by its own recipient.
Related articles
Related articles
-
WhatsApp (Meta) error codes: what they mean and what to do
A table of the most common Meta error codes when sending on WhatsApp (131026, 131047, 131049, 130497, 141006, 131031, 131056, 132000, 190, 368…) and how to fix each one.
-
How to connect Telegram
Connect a Telegram bot to your Omnifox inbox in minutes using BotFather.
-
Instagram and Facebook comments: reply and moderate from Omnifox
See and answer comments on your Facebook and Instagram posts and ads, publicly or privately, and set up automatic replies.
-
Sending and receiving videos on each channel: formats and size limits
Which videos you can send and receive on WhatsApp, Instagram, Messenger, Telegram, web chat and email, the real size limits, and what to do with a large video.
-
Move from WhatsApp QR to Coexistence or Cloud API
Once you're done testing with the QR code, move your number to the official connection: no caps, with templates and broadcasts, and no volume-based ban risk.