Skip to content
nofeb

SendGrid Inbound Parse to an agent inbox

Endpoint: POST /v1/inbound/sendgrid/{token}

In SendGrid's Inbound Parse settings, add your host with your nofeb SendGrid URL as the destination and tick "POST the raw, full MIME message". nofeb parses the raw message, routes it by recipient to the right inbox and tells the agent by webhook, the event feed or wait_for_email.

Checked against the engine on .

How do I connect SendGrid Inbound Parse to nofeb?

  1. Copy inbound.webhook_urls.sendgrid from GET /v1/me.
  2. Point the receiving host's MX at SendGrid, as its Inbound Parse setup requires.
  3. In Settings → Inbound Parse, add the host and paste the nofeb URL as the destination.
  4. Tick "POST the raw, full MIME message". Without it SendGrid posts parsed fields, which nofeb does not use.
Your SendGrid destination URL
GET https://api.nofeb.com/v1/me
→ { "inbound": { "cloudflare_token": "…",
    "webhook_urls": { "raw": "…/v1/inbound/raw/{token}", "postmark": "…/v1/inbound/postmark/{token}",
                      "mailgun": "…/v1/inbound/mailgun/{token}/mime", "sendgrid": "…/v1/inbound/sendgrid/{token}" } } }

How does the agent get the message?

The same three ways as any other inbound mail. Subscribe a webhook to message.received, pull the event feed, or block on wait_for_email until it arrives:

The same over REST
curl -X POST https://api.nofeb.com/v1/inboxes \
  -H "Authorization: Bearer $NOFEB_API_KEY" -H 'content-type: application/json' \
  -d '{"local_part": "signup-bot", "ttl_seconds": 3600}'

curl "https://api.nofeb.com/v1/inboxes/$INBOX_ID/wait?has_otp=true&timeout=60" \
  -H "Authorization: Bearer $NOFEB_API_KEY"
# → { "message": { "subject": "Your code", "otps": [{ "code": "482913", "source": "body" }], … } }

What does nofeb add to SendGrid's payload?

  • The same parsing as every other inbound path, from the raw message: reply_text, safe_body, codes, links and attachment text.
  • Duplicates from SendGrid's retries are delivered once.
  • A security verdict is recorded only for mail nofeb's own server receives; for SendGrid-routed mail, SendGrid's own spam check, if enabled, is what ran.

What should I know about SendGrid itself?

From SendGrid's own documentation, checked .

  • Inbound Parse setup requires an MX record for the receiving host pointing to mx.sendgrid.net with priority 10. source: twilio.com
  • By default the webhook posts parsed fields, and an option posts the raw, full MIME message instead. source: twilio.com
  • The total message size limit, including attachments, is 30MB. source: twilio.com
  • Failed POSTs that return 5XX are retried, and messages that cannot be delivered after 3 days are dropped. source: twilio.com
  • Only authenticated domains may be used with Inbound Parse, and the webhook does not follow redirects. source: twilio.com
  • The pricing page lists the Inbound Parse Webhook on Pro (from $89.95 a month) and Premier, and not on Essentials. source: twilio.com
The nofeb inbound pipeline Two entry points, nofeb's own MX and provider webhooks authenticated by an inbound token, feed the same pipeline: sender authentication and spam and virus checks at the MX, routing by envelope recipient, the inbound.resolve hook, an injection score, sender trust and typed decisions, then sender lists, the inbound.pre_deliver hook and rules, delivery to the inbox, Junk or quarantine, then a message.received event by webhook or event feed, and access over REST or MCP for the agent. Ways in nofeb MX Any mail server delivers STARTTLS offered Recipient checked at RCPT Provider webhooks Cloudflare Email RoutingPostmark inbound streamMailgun routeSendGrid Inbound ParseAny raw POST /v1/inbound/…/{token} At the door Checks before 250 OK SPF · DKIM · ARC · DMARC Spam and virus scan Refuse, accept, or Junk Pipeline One pipeline Route by envelope recipient Delivered once, even if resent inbound.resolve hook Scored and triaged injection score, sender trust decisions on every message sender lists inbound.pre_deliver hook rules quarantine, reject or file Parsed for the model reply_text · safe_body codes, links, attachments extracted metadata security verdict Inbox Agent inbox Inbox, Junk or quarantine Typed metadata on the thread Raw message kept byte-exact The agent hears message.received webhook, event feed or stream wait_for_email long-poll until it arrives Agent: REST, SDK or MCP
Mail from any sending server reaches nofeb's MX; mail already handled by Cloudflare Email Routing, Postmark, Mailgun or SendGrid is passed on with your inbound token. Both join the same pipeline, where each message is scored for injection, labelled and triaged before your sender lists, hooks and rules decide its fate, and the agent hears about it by webhook, the event feed, the stream, REST or MCP.

Frequently asked questions

Why is SendGrid Inbound Parse retrying or dropping messages?

SendGrid retries a POST that fails with a 5XX and drops the message after three days. nofeb answers only once the message is stored, and a redelivered message is delivered once, so retries are safe.

Why tick "POST the raw, full MIME message"?

nofeb parses the raw message so the agent gets the same fields from every path, plus the byte-exact original. The parsed-fields format is not used.

Can I stop using SendGrid for inbound entirely?

Yes. Point the domain's MX at nofeb instead, and nofeb's own server receives the mail with sender authentication and spam and virus checks.

Status of everything on this page

Every capability named above, with its status as reconciled against the engine.

CapabilityWhat it doesStatus
Inbound from the provider you already use Receive through Cloudflare Email Routing with an Email Worker on your own zone, a Postmark inbound stream, a Mailgun route, SendGrid Inbound Parse, or any service that can POST a raw message. Each path is authenticated by your organization's inbound token, which you can rotate at any time, and delivers only to your own inboxes and verified domains. Shipped
Inbound routed by envelope recipient Mail is delivered to the inbox named in the SMTP envelope, not the To: header, whichever way it arrives, and redelivery is idempotent. Shipped
Reply extraction Each message carries its new text with quoted history and signature removed. Shipped
safe_body for untrusted mail The message's new text with zero-width and direction-altering characters, hidden HTML and forgeable quoted history removed, wrapped in a provenance header that tells the model whose words these are. Shipped
One-time code and link extraction Verification codes and classified links are pulled out of every message and returned as fields. Shipped
Attachment text Attachments are listed with their extracted text and can be downloaded byte-exact. Shipped
Wait for an email Long-poll an inbox for up to a minute until a message matching sender, subject or has-a-code arrives. Shipped
Signed webhooks with required scope Standard Webhooks signatures, retries and a delivery log. Scope (organization, pod or inbox) is required, so a subscription never silently widens to everything. Shipped
HTTPS hooks in the pipeline Signed HTTPS callouts that change what happens: create or reject an inbox for an unknown recipient, accept, reject or quarantine a message before delivery, and allow, deny or hold a send, each with a timeout and a fail-open or fail-closed mode. Shipped