Set up Email with SendGrid or Mailgun (API key)
How to connect the Email channel using a SendGrid or Mailgun API key, and when that beats plain SMTP.
What you'll set up
The Omnifox Email channel lets you send and receive email as just another conversation in your Inbox. You can connect it two ways: with an API provider or with traditional SMTP. This guide covers the API key option.
The Provider dropdown offers exactly three choices: SMTP, SendGrid, and Mailgun.
API key or SMTP — which should you pick?
- API key (SendGrid or Mailgun): you paste a single key. Good deliverability, no ports to open. It's the simplest way to send at scale.
- SMTP: asks for host, port, username, password, and encryption. Pick it if you already have a corporate mailbox, or if your provider isn't one of the two above.
API providers require a verified sending domain. Channels using their own authenticated SMTP are exempt, because your own server already authenticates the sender.
Requirements
- A SendGrid or Mailgun account.
- Your domain verified with that provider, with SPF and DKIM set up.
- An API key generated in the provider's dashboard.
Steps
- In the side menu, open Channels and click Connect New Channel.
- Choose Email as the channel type.
- Enter the Channel Name — it's required before you can continue.
- Under Sending (outgoing mail), open the Provider dropdown and pick SendGrid or Mailgun.
- Paste your key into the API Key field.
- Fill in From Email (the sending address, e.g.
[email protected]) and From Name (the name customers see, e.g.Support). - Click Continue to save the channel.
The From Email address must belong to a domain verified with your provider. Otherwise SendGrid or Mailgun will reject the send.
Receiving email
Receiving is configured separately, under Receiving (incoming mail), with its own credentials. There are two methods:
- Webhook — your provider forwards messages to an Omnifox URL. Copy the Inbound Webhook URL shown in the form and paste it into your provider's inbound section: Inbound Parse in SendGrid, Routes in Mailgun.
- IMAP — Omnifox connects to a mailbox and pulls the messages in.
Verifying
- From the channel you just created, send a test email to one of your own addresses.
- Reply to it from your personal inbox.
- The reply should show up in the Omnifox Inbox.
If it doesn't work
- Nothing goes out: check that the API Key is correct and has send permissions.
- Messages land in spam or get rejected: the domain isn't verified (SPF/DKIM), or the From Email doesn't match the verified domain.
- You get a verified-sending-domain warning: with SendGrid or Mailgun that requirement is mandatory. Verify the domain, or use a channel with your own SMTP.
- Replies never arrive: the inbound webhook URL isn't set up correctly at the provider, or your MX records don't point to the inbound service.
Tips
- Use a dedicated address like
support@orhello@instead of someone's personal email, so all support stays in one place. - If you'd rather not depend on an external provider, the SMTP option works with any corporate mailbox.
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.