How to Set Up Mailgun Replies in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

Mailgun replies route into Sparkforge through a Catch All receiving route pointed at the platform's inbound webhook. Set the route, verify the API key, and replies sync into the conversation thread automatically.

Mailgun replies need a receiving route configured so inbound email lands in the right Sparkforge conversation. This article walks through verifying the route, building it from scratch if needed, and resetting the API key when integrations break.

Check your receiving route in Mailgun

Log in to Mailgun.
Click the Receiving tab.
Confirm the existing webhook route matches the configuration shown in this article.
If it does not match — or if extra routes are present — remove them and rebuild the route from scratch.

Create the receiving route

If no webhook route is configured, click Create Route in Mailgun and set:

Expression Type: Catch All
Forward URL: the Sparkforge inbound webhook URL provided in your subaccount's email integration screen
Priority: 99
Description: Sparkforge Route

Click Save. Mailgun applies the route immediately.

Whitelabel forward link

If your client uses their own Mailgun account and you need the forward link whitelabeled, request the whitelabel webhook URL from Sparkforge support and use it instead of the default.

Reset the Mailgun API key

If replies stop syncing, the API integration is the most common culprit. Reset it:

Open the agency view.
Go to Settings > Email Services > Location Settings.
Edit the Mailgun API integration for the affected subaccount.
Type Delete to confirm removal.
Re-integrate by entering a fresh Mailgun API key.
Refresh the Mailgun Receiving page to confirm the route was recreated.

Why replies might still not arrive

Domain authentication is incomplete in Mailgun (SPF, DKIM, or DMARC failing).
Multiple conflicting receiving routes are present — remove duplicates.
The forward URL has a typo or is missing the path.
The Mailgun API key in Sparkforge does not match the one in the Mailgun account.

Frequently Asked Questions

What is the difference between Mailgun replies and regular email replies?

Mailgun replies route through the Mailgun API and a webhook into Sparkforge so they land in the matching conversation. Regular email replies hit a standard inbox without the automation hookup.

Can I set up automatic responses to specific replies?

Yes. Use Sparkforge workflows to trigger on Customer Replied with a Reply Channel filter for email, then send your automated response from there.

Why are my email replies not appearing in Sparkforge?

Check Mailgun receiving routes for duplicates, verify domain authentication (SPF, DKIM, DMARC), confirm the forward URL is correct, and reset the Mailgun API key in Sparkforge if integration looks broken.

Do I need a Catch All route or can I use a specific match?

Catch All with priority 99 is the supported configuration. Specific match expressions work in Mailgun but can miss reply addresses Sparkforge generates dynamically.

What priority should the Sparkforge Mailgun route use?

Set the route priority to 99 so it evaluates last and acts as the catch-all for replies that no higher-priority route claims.