Skip to content
nofeb

Postmark inbound webhook to an agent inbox

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

Set the inbound stream's webhook URL to your nofeb Postmark URL and turn on "Include raw email content in JSON payload". nofeb reads the raw message from that payload, routes it by recipient to the matching inbox, and the agent hears about it by webhook, the event feed or wait_for_email.

Checked against the engine on .

How do I connect Postmark inbound stream to nofeb?

  1. Copy inbound.webhook_urls.postmark from GET /v1/me (an organization-level key).
  2. In Postmark, open the server's inbound message stream and set it as the webhook URL.
  3. Enable "Include raw email content in JSON payload"; nofeb needs the raw message, not only the parsed fields.
  4. Make sure the recipient is one of your nofeb inboxes or an address on a verified nofeb domain.
Your Postmark webhook 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 Postmark's payload?

  • nofeb parses the raw message itself, so every message carries the same fields whatever path it took: reply_text, safe_body, extracted one-time codes and classified links, and attachment text.
  • Messages are threaded into the inbox's conversations and can carry typed metadata, so the agent keeps state on the thread.
  • Postmark's retries are harmless: nofeb delivers a redelivered message once.

What should I know about Postmark itself?

From Postmark's own documentation, checked .

  • Each Postmark server has an inbound message stream with an address in the format hash@inbound.postmarkapp.com. source: postmarkapp.com
  • When RawEmailEnabled is on, the raw email is included in the inbound webhook payload under the RawEmail key. source: postmarkapp.com
  • Each Inbound Message Stream has one webhook URL. source: postmarkapp.com
  • Total cumulative size for all inbound attachment files may not exceed 35 MB. source: postmarkapp.com
  • If the webhook does not return 200, Postmark retries 10 times with intervals growing from 1 minute to 6 hours, and a 403 response stops retries. source: postmarkapp.com
  • Postmark's StrippedTextReply field is populated only for replies, and only for English text replies. source: postmarkapp.com
  • Inbound processing is included on the Pro and Platform plans and not on Free or Basic. source: postmarkapp.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 does nofeb need the raw email from Postmark?

So that a message from Postmark is parsed exactly like one received by nofeb's own MX: the same reply text, safe_body, codes, links and attachment text, and a byte-exact original you can download.

Can I keep Postmark for sending?

Yes. The inbound stream is independent of how you send; nofeb only receives what the stream forwards.

What if my token leaks?

Rotate it with POST /v1/inbound-token/rotate. Every earlier token stops working at once, so update the webhook URL in Postmark straight after.

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