Skip to main content
Out of the box, your mail goes out through InstantCampaign’s platform provider. You can instead connect your own sending account, so mail goes out under your account and reputation. Connecting a provider is available on every plan. Three things work together:
  • Providers (Settings → Integrations → Email sending) are the accounts that can deliver your mail.
  • Delivery routes (Settings → Send policies) are the ways mail can leave the workspace: through a connected provider, or through the platform.
  • Send policies (Settings → Send policies) are named bundles of kind (marketing or transactional), sender profile and delivery route. A send picks a policy.
Only owners and administrators can connect and change providers. Delivery routes and send policies can be changed by anyone whose role has the Settings: write permission.

​
Supported providers

Credentials are stored encrypted. When you edit a provider, leave a secret field blank to keep the saved value.

​
Connect a provider

1

Open Email sending

Go to Settings → Integrations. Under Email sending, click Connect a provider (or Connect another provider).
2

Enter credentials

Pick the provider, give the connection a name, fill in the fields and click Connect and test. A cheap authenticated call confirms the credentials. The card then shows Connection OK or the error.
3

Register delivery webhooks

Click Register webhooks. This asks the provider to report deliveries, bounces and complaints back to InstantCampaign. The card shows Registered, Manual setup (copy the secret URL into your provider yourself) or Not available (SMTP has no event feed).
4

Check verified senders

Open Senders to see the domains and addresses the provider will accept mail from. Sender profiles must match one of these. Verification happens in the provider’s own dashboard.
5

Route mail through it

Go to Settings → Send policies and point a delivery route (and the policies that use it) at the new provider.
SendGrid: on accounts that support only one event webhook, registering replaces your existing event webhook. If you already use SendGrid’s event webhook elsewhere, set it up manually instead.
Use Test at any time to re-check the connection, and Make default to mark the Default provider. The default carries a new workspace’s default policies and is pre-selected when you create a route.

​
Removing a provider

When you remove a provider, mail routed through it falls back to the platform provider until you point the route somewhere else. Webhooks registered at the provider stop being accepted. The provider stops calling them after a while, or you can delete them in its dashboard.

​
What delivery events do

Once webhooks are registered, events from every provider are applied the same way: You can see these per message in the Message Log and manage bounced contacts in Bounce Management. See Email analytics.

​
Send policies and delivery routes

Settings → Send policies has two lists. Delivery routes. Each route is one way mail leaves the workspace: a connected provider, or Platform default (InstantCampaign). Mark one route as default to pre-select it for new policies. You can’t delete a route while a policy uses it. Send policies. Each policy has a Name, Description, Kind, Sender profile (or Workspace default sender) and Delivery route. The name becomes a key, such as newsletter-eu, that the API can use. There’s always exactly one default policy per kind, and sends that don’t name a policy use the default of their kind. The kind decides the rules: Transactional mail (receipts, password resets) is owed to the recipient even if they unsubscribed from marketing. Don’t use a transactional policy for promotional content.
A policy’s kind can’t be changed after it’s created. To send a different kind of mail, create a new policy. A default policy can’t be deleted. Make another policy the default first.

​
Choosing a policy when you send

Campaigns and journey email steps let you pick a policy. Transactional API calls can name one with the sendPolicy field (key or id). An unknown policy is refused rather than silently replaced. If a queued send’s policy is deleted before it goes out, the send uses the default policy for its kind.

​
Troubleshooting

Re-check the credentials and the permissions listed above. For Mailgun and SparkPost, make sure the region matches your account.
Verify a domain in the provider’s console first. Some keys, such as a Postmark server token without an account token or a Resend send-only key, can’t list senders. In that case, verify the domain under Settings → Domain Authentication so sender profiles can use it.
Make sure webhooks show Registered. For Manual setup, copy the secret webhook URL from the card into your provider’s webhook settings.