DEV Community: Valentin Kivachuk

Postmark, Python, and Perfect Parsing: Simplifying Inbound Emails

Valentin Kivachuk — Sat, 07 Jun 2025 21:35:11 +0000

What I Built

Managing inbound emails efficiently is a common challenge, especially when working with Postmark's Inbound API. Parsing raw JSON responses can quickly become overwhelming, leading to unnecessary complexity. To tackle this, I built postmark-models—a lightweight library designed to structure and validate Postmark inbound messages using Pydantic models.

With postmark-models, developers can seamlessly extract relevant email data, enforce schema validation, and minimize manual parsing efforts, making Postmark integration much more manageable.

Demo

Since this is a library, the best way to test it is through code. Here's a simple demonstration:

$ poetry add postmark-models # pip install postmark-models

from postmark_models import MessageInbound, example_message

message = MessageInbound.model_validate(example_message)

print(f"From: {message.from_}")
print(f"Subject: {message.subject}")
print(f"Text Content: {message.text_body}")

This example shows how easily an inbound email can be structured using postmark-models. Developers can incorporate this library into their applications to improve Postmark message handling.

Code Repository

The complete project is available on GitHub. Feel free to explore the repository, try out the library, and contribute to its development!

How I Built It

This project leverages Pydantic for model validation and type safety. The key highlights include:

Pydantic for structured data validation – Ensuring well-formed email messages.
Simplified parsing of Postmark inbound emails – No need to manually process JSON responses.
Enhanced debugging capabilities – Easily catch inconsistencies in inbound emails.

Building postmark-models was a great learning experience, allowing me to optimize email workflows with Postmark while making message parsing intuitive and accessible for developers.

Absolutely! Here are more examples showcasing how postmark-models can be used to process inbound email messages effectively.

More Practical Examples

Example 1: Extracting Attachments

Handling attachments from inbound emails can be tricky, but postmark-models simplifies it by providing structured access to the attached files.

# Iterate through attachments
for attachment in message.attachments:
    print(f"Attachment: {attachment.name}, Type: {attachment.content_type}, Size: {attachment.attachment.content_length}")

This makes it easy to filter specific file types, store attachments, or process them further.

Example 2: Extracting Header Information

Postmark inbound messages include headers that may contain useful metadata. postmark-models provides a clean way to access them.

header_value = message.get_header("X-Custom-Header")
print(f"Custom Header Value: {header_value}")

This is great for applications that need to analyze custom headers for authentication or routing purposes.

Example 3: Detecting Email Replies

Many applications rely on email-based communication, and distinguishing between original messages and replies is crucial.

if message.is_reply():
    print("This is a reply email!")
else:
    print("This is a new email.")

With this approach, you can automate responses differently based on whether the message is a reply or a fresh email.

Example 4: Extracting Plain Text vs HTML Content

Sometimes, applications need to decide whether to process the plain text body or the HTML body of an inbound email.

if message.text_body:
    print("Processing plain text body:")
    print(message.text_body)
elif message.html_body:
    print("Processing HTML body:")
    print(message.html_body)

This is useful for applications that prioritize plain text responses while still supporting rich HTML content.

Example 5: Auto-Forwarding Emails Based on Conditions

With postmark-models, you can automatically forward certain emails based on predefined conditions.

if "urgent" in message.subject.lower():
    forward_email(message, recipient="support@example.com")

This ensures critical emails are routed to the right team or system without manual intervention.

Final Thoughts

These examples highlight the versatility of postmark-models when working with Postmark inbound messages. Whether handling attachments, filtering headers, processing replies, or routing emails, this library simplifies email parsing and enhances workflow automation.

Feel free to explore the GitHub repository, try out these examples, and see how they fit into your project!

Postmark + n8n: No Code, No Limits

Valentin Kivachuk — Wed, 28 May 2025 18:08:40 +0000

This is a submission for the Postmark Challenge: Inbox Innovators.

TL;DR

Receive postmark inbound webhooks with no effort

The Challenge

Experimenting with Postmark’s Inbound Email functionality often requires a tedious setup—writing HTTP request handling code, deploying it to a server, configuring DNS, managing firewalls, and more. Before you even start, the frustration kicks in.

Wouldn’t it be great if there was just a single button to deploy everything effortlessly? That’s exactly what this project offers: a one-command solution to simplify Postmark webhooks testing.

Demo & Setup

To get started, ensure you have Docker installed.

Project Structure

Your setup includes the following essential files:

❯ tree -a -I .git
.
├── docker-compose.yml  # Core functionality
├── .env                # Optional environment variables (credentials, server URL)
├── LICENSE  
└── n8n_node.json       # Pre-configured n8n example


1 directory, 4 files

Deployment

Run the following commands to get started:

git clone https://github.com/vk496/docker-postmark-n8n
cd docker-postmark-n8n
docker compose up -d
docker compose logs lt

Configuring Your Webhook

Once deployed, confirm that your public endpoint is test-server (thanks to LocalTunnel):

Your full webhook callback URL is now:

https://test-server.loca.lt/webhook/postmark-inbound

Update your Postmark Inbound Stream settings, test your webhook, and observe the results:

Now, access your n8n instance via:

Local http://localhost:5678
Public Tunnel https://test-server.loca.lt/

Default login credentials:

Username: admin@example.com  
Password: Admin123

Track executions to confirm webhook activity:

What’s Next?

Now that you’ve received the callback, you can leverage it in countless ways!

Forward data to an API endpoint
Transcribe content using AI
Translate with external services
Scan for malicious attachments

With n8n, automation possibilities are endless. Take inspiration from n8n workflows templates:

⚠️ Important: No Persistent Storage

Ensure you export your workflow before restarting or removing the Docker container. This project is not intended for production operations

Code Repository

https://github.com/vk496/docker-postmark-n8n

How I Built It

Working with n8n inside Docker presented unique challenges, such as initializing default credentials and preloading workflows without direct environment variables. Creativity and workarounds were key to making this project possible.

Feel free to explore and adapt ideas from the docker-compose.yml file!