Inbound Parsing allows you to receive, process, and manage replies from your email recipients. By configuring specific rules and webhooks, you can automate how your application handles incoming communication and attachments.

Inbound Parsing transforms your outgoing email stream into a two-way conversation. It allows you to:

• Receive Replies: Automatically capture responses from your recipients.
• Automate Workflows: Trigger specific actions or webhooks based on the content of the reply.
• Handle Attachments: Receive files sent by users directly at your set email address or via a configured webhook.

Prerequisites

Before you can create an Inbound Parse, your domain must be prepared to receive mail through Netcore:

Netcore Email API can only process replies if the domain used for receiving them has its MX (Mail Exchange) record pointed to Netcore Email API servers.

Configuration Steps

Step 1: Configure Your Domain

To allow Netcore to "listen" for incoming emails, follow these steps to set up your DNS:

1. Log in to your Netcore Email API dashboard.
2. Navigate to Settings -> Sending Domains.
3. Click Add a Domain.
4. Scroll down to the domain settings page to locate the specific MX Record details provided by Netcore.
5. Add this MX record to your domain's DNS Provider settings (e.g., GoDaddy, Cloudflare, AWS Route 53).
6. Once the DNS propagates, return to the Netcore panel and click Verify.

Step 2: Create Inbound Parse

Once your domain is verified, you can set up the parsing logic:

1. Navigate to Settings > Inbound Parsing.
2. Click the 'Create an Inbound Parse' button.
3. Select the Domain you verified in Step 1.
4. Add Conditions (Optional): Click 'Add conditions' to filter specific types of replies.
5. Set the Action: Define where the data should go. If you choose a Webhook, you must provide a destination URL.

Conditional Parsing

Conditional Parsing allows for a sequential filtering mechanism. This ensures that replies are handled by the right logic based on:

• Subject Line
• Recipient Domain
• Email Headers

How it Works:

• Sequential Check: When a reply arrives, Netcore checks it against your configured conditions in order.
• Global Condition: If a reply does not satisfy any of your custom filters, it will be processed according to the "Global Condition" (your default fallback setting).

If your Inbound Parse shows as 'Unverified', it is usually related to your Webhook configuration.

• The Cause: For security and functional reasons, Netcore requires you to authenticate the Webhook URL before activating the parse.
• The Fix: Ensure the URL you provided is active and reachable. Click the Verify button next to the URL in your settings. Once the URL is authenticated, the status will change to Active.