primitive

What

Primitive Beta appears to be a developer-focused email ingestion service that turns inbound email into structured JSON webhooks. It is designed for teams that want to receive emails across domains and aliases in code, rather than managing a traditional mailbox workflow.

Based on the page, the core workflow is: point MX records to the service, receive email events at a webhook endpoint, validate the webhook with the provided SDK, and process parsed email content in an application. Its positioning is likely an infrastructure layer or API primitive for developers building email-driven products, automations, or back-end systems.

Features

• Single MX record setup: The page says one MX record can route emails, which simplifies initial DNS configuration for inbound email handling.
• Webhook delivery for inbound email: Emails are sent immediately to a webhook, enabling event-driven processing in applications and back-end workflows.
• Structured JSON payloads: The service exposes email data as JSON, including headers, SMTP envelope fields, parsed body content, and metadata for easier programmatic handling.
• Support across domains and aliases: The page states it works across all domains and aliases, which is useful for centralized ingestion and routing logic.
• SDK-based webhook verification: The example shows a handleWebhook helper and error handling, suggesting a standard way to validate incoming webhook requests.
• Raw content and attachment access: The sample payload includes base64 raw content, downloadable raw message data, parsed attachments, and attachment download URLs for deeper processing when needed.

Helpful Tips

• Validate parsing quality before production use: The sample shows parsed text, HTML, and attachments, but a full range of email edge cases is not described on the page.
• Plan storage and retention deliberately: Since raw email content and attachments may be included or downloadable, teams should define how much data to keep and for how long.
• Use clear routing rules by domain and alias: If multiple domains feed one webhook pipeline, establish deterministic handling for support, sales, transactional, and automated inbound messages.
• Treat spam scoring as supplemental only: The sample payload includes a SpamAssassin score, but the page does not explain policy controls or filtering behavior in detail.
• Review operational dependencies carefully: The page shows webhook-based delivery, so reliability will depend on endpoint availability, retry handling, and internal queue design.