Skip to main content
Route incoming emails to different handlers based on the recipient address, subject line, content, or custom rules. This allows you to build sophisticated email processing workflows.

Routing by Recipient

The most common routing pattern is based on the recipient email address:

Variable Address Routing

Use variable addresses (plus addressing) to encode data in the email address:

Common Variable Address Patterns

Routing by Subject

Route emails based on subject line keywords or patterns:

Routing by Sender Domain

Route based on the sender’s domain for B2B workflows:

Content-Based Routing

Route based on email content analysis:

Multi-Criteria Routing

Combine multiple routing criteria for complex workflows:

Routing with Priority Queues

For high-volume applications, use priority queues:

Catch-All Addresses

Handle any address on your inbound domain:
Catch-all addresses can receive a lot of spam. Consider implementing spam filtering before processing catch-all emails.

Forwarding Emails

Forward received emails to another address:

Error Handling

Implement proper error handling in your routing logic:

Webhooks

Set up webhook endpoints

Reply Tracking

Track and thread email replies

Spam Filtering

Filter spam from inbound emails

Best Practices

Inbound best practices