Email Provider Order in Sparkforge: How Sending Is Routed

Sparkforge sends every outbound email through one provider, chosen by a defined priority chain. Knowing the order lets you predict which Mailgun key, sending domain, or SMTP path will fire — and how to override it for a specific sub-account.

The provider order

1. Sub-account default provider — set inside the sub-account view.
2. Email Settings for Locations — set in agency view, applied to a specific location.
3. Agency default provider — set in app.sparkforge.com/settings/email_services.
4. Sparkforge Email — the platform fallback when nothing else is configured.

If no default provider is selected at the location level, Sparkforge falls back to the provider configured in agency view.

Setting up Mailgun per location

Each location can use its own Mailgun account or share yours. You have four valid patterns:

• Same Mailgun API and same domain across multiple locations.
• Same Mailgun API, different domains or subdomains per location.
• Different Mailgun API and different domains per location.
• A unique domain or subdomain per location to capture cold inbound email.

Setting up Sparkforge Email per location

If you add a custom domain at the agency level, every sub-account inherits it until a sub-account sets its own. Sub-account settings always take priority once configured.

Agency default in Email Services

Open Settings → Email Services in agency view to set the default Mailgun API key. New locations inherit this key, and Sparkforge uses it to send verification codes.

Sparkforge Email fallback

When nothing is configured anywhere in the chain, Sparkforge Email sends from a system-managed subdomain. This works out of the box but does not build sending reputation on your own domain.

High-volume export

Email service settings now support a download. Use it when you manage many sub-accounts and need to audit which Mailgun key, domain, and provider is wired to each location.