Inbound Route

Overview

Inbound Route configuration allows you to automatically forward incoming email replies to either a specified email address or webhook URL. This feature helps centralize email management, improve tracking efficiency, and enhance team collaboration.

Before setting up an Inbound Route, ensure you have:

MX Record Configuration: Configure the domain's MX record first to enable email routing
Domain Access: Administrative access to your domain settings
Email Verification: Access to the email address you want to use for forwarding (if using email method)

How Inbound Routes Work

When you create an Inbound Route, Aurora SendCloud will:

Monitor incoming emails to your specified address pattern
Automatically forward these emails using your chosen method
Process replies and route them according to your configuration

Note: Emails sent directly to the configured address will not be forwarded by default. Only be processed when the recipient replies to the email you sent.

Configuration Methods

Method 1: Forward to Email Address

This method forwards incoming replies directly to a specified email inbox.

Setup Steps:

Choose Domain: Select the domain for your inbound route
Inbound Route: Enter the Inbound Route prefix together with Domain to form an email address
Email Verification:
- Enter your target email address
- Click "Get Verification Code"
- Check your inbox for the verification email
- Enter the verification code to confirm
Select API_USER: Choose the API_USER that will handle the email forwarding

Benefits:
- Simple setup and management
- Direct integration with existing email workflows
- No additional infrastructure required

Advanced Configuration

Email Address Patterns

Configure flexible email patterns using prefixes and regex:

Simple Prefix

Use a simple prefix like mail to create addresses like [email protected]

Regex Patterns

Use regex patterns like .* to match any prefix: [email protected]

Examples

Pattern	Matches	Example
`support`	`[email protected]`	Customer support emails
`reply-.*`	`[email protected]`	Campaign reply tracking
`.*`	Any email to your domain	Universal catch-all

Implementation Timeline

New routes take effect within 10 minutes of configuration.

During this time:

DNS propagation occurs
Route rules are activated
Email processing begins

Monitor your first few test emails to ensure proper routing.

Best Practices

Test Your Setup: Send test emails to verify routing works correctly
Monitor Performance: Check that your webhook endpoints respond quickly
Secure Your URLs: Use HTTPS for webhook URLs when possible
Plan for Volume: Ensure your systems can handle expected email volumes

Troubleshooting

Route Not Working:

Verify MX records are properly configured
Check that 10 minutes have passed since configuration
Ensure email verification is complete

Webhook Issues:

Confirm URL is accessible and returns proper status codes
Check server logs for incoming requests
Verify endpoint can handle POST requests with email data

Missing Emails:

Check spam/junk folders for forwarded emails
Verify the email pattern matches incoming addresses

Next Steps

After configuring your Inbound Route:

Send Test Emails: Verify the routing works as expected
Monitor Performance: Track email processing and delivery
Integrate Systems: Connect forwarded emails with your existing workflows
Scale Configuration: Add additional routes as needed for different email types