Use SMTP2GO with GetFluxly

Connect SMTP2GO to GetFluxly and run behavior-triggered lifecycle email through a long-running ESP with strong free-tier economics. GetFluxly captures product events, builds unified customer profiles, and triggers automations on your rules SMTP2GO handles delivery, DKIM signing, and per-domain reputation. Your sender reputation stays in your SMTP2GO account.

When to use SMTP2GO

Pick SMTP2GO when you want production-grade SMTP delivery on a generous free tier (1,000 emails/month) with no credit card to get started. SMTP2GO suits indie SaaS, side projects, and early product teams that want to validate a lifecycle email program before they pick the long-term sending stack. Setup is simple: verify the domain, mint credentials, paste them into GetFluxly.

Requirements before connecting

An SMTP2GO account, a domain you can publish DNS records on, and send-scoped credentials (either an SMTP user or an API key). On the GetFluxly side: a project, a workspace API key (gf_live_…), and access to Settings → Email providers.

Verify your sending domain

In the SMTP2GO dashboard, open Sending → Verified Senders → Add Domain and enter the apex domain you want to send from (for example yourdomain.com). SMTP2GO generates SPF and DKIM records and watches them for verification once they propagate, the status flips to Verified.

Add SPF, DKIM, and DMARC

These records live on your domain's DNS, not on GetFluxly. They tell receiving mailboxes that SMTP2GO is allowed to send on your behalf and what to do when alignment fails.

SPF

Type:   TXT
Host:   yourdomain.com
Value:  v=spf1 include:spf.smtp2go.com -all

DKIM

SMTP2GO issues two CNAME records under the _domainkey subdomain. Copy the host and value pairs exactly as the dashboard displays them.

Type:   CNAME
Host:   s2go1._domainkey.yourdomain.com
Value:  s2go1._domainkey.smtp2go.net

Type:   CNAME
Host:   s2go2._domainkey.yourdomain.com
Value:  s2go2._domainkey.smtp2go.net

DMARC

Type:   TXT
Host:   _dmarc.yourdomain.com
Value:  v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com; fo=1

Create SMTP2GO credentials

GetFluxly speaks two SMTP2GO dialects: SMTP (with an SMTP user) and the SMTP2GO HTTPS API (with an API key). Pick the path that matches your network policy.

Option A SMTP user (recommended for SMTP path)

In SMTP2GO, open Settings → SMTP Users → Add SMTP User. Pick a username, set a strong password, and lock the user to your verified sending domain. Use these credentials with the GetFluxly Custom SMTP connector pointed at mail.smtp2go.com on port 587 with STARTTLS.

Option B API key (recommended for HTTPS API path)

In SMTP2GO, open Settings → API Keys → Add API Key. Limit the key to the email/send scope only, never use a full-access key for production sending. Copy the key (it starts with api-); SMTP2GO only displays it once.

Connect SMTP2GO in GetFluxly

Open Settings → Email providers, click Add provider, and choose SMTP2GO for the HTTPS API path or Custom SMTP for the SMTP path.

HTTPS API path:

curl -X POST https://api.getfluxly.com/v1/projects/PROJECT_ID/email-providers \
  -H "Authorization: Bearer gf_live_REPLACE_ME" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "smtp2go",
    "display_name": "SMTP2GO Production",
    "from_email": "hello@yourdomain.com",
    "from_name": "Acme",
    "api_key": "api-..."
  }'

SMTP path (Custom SMTP connector):

curl -X POST https://api.getfluxly.com/v1/projects/PROJECT_ID/email-providers \
  -H "Authorization: Bearer gf_live_REPLACE_ME" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "smtp",
    "display_name": "SMTP2GO Production",
    "from_email": "hello@yourdomain.com",
    "from_name": "Acme",
    "smtp_host": "mail.smtp2go.com",
    "smtp_port": 587,
    "smtp_secure": "starttls",
    "username": "SMTP_USER",
    "password": "..."
  }'

Handle bounces and complaints

SMTP2GO webhooks deliver bounce, spam-complaint, and delivery events. Wire them to GetFluxly so the suppression list updates automatically.

1. In GetFluxly, copy the project webhook URL from Settings → Webhooks → SMTP2GO, it looks like https://api.getfluxly.com/v1/webhooks/smtp2go/<project_id>.
2. In SMTP2GO, open Settings → Webhooks → Add Webhook and paste the URL.
3. Subscribe to bounce, spam_complaint, and delivered events. GetFluxly verifies the project token before any suppression list update.

Test your first lifecycle email

Hit the verify endpoint to dispatch a one-shot message through SMTP2GO. If it lands, your wiring is good and you can point an automation at this provider record.

curl -X POST https://api.getfluxly.com/v1/email-providers/PROVIDER_ID/test \
  -H "Authorization: Bearer gf_live_REPLACE_ME" \
  -H "Content-Type: application/json" \
  -d '{ "to": "you@yourdomain.com" }'

Common errors

SMTP2GO returns 401 invalid_api_key. The key was deleted or rotated. Mint a fresh send-scoped key in SMTP2GO and update the GetFluxly record.

sender not verified. The address in from_email isn't on a verified SMTP2GO domain. Confirm DKIM is green in the SMTP2GO dashboard.

SMTP authentication failed. The SMTP user was scoped to a different domain than from_email, or the password was rotated. Recreate the SMTP user with the right scope and update the GetFluxly record.

Mail going to spam. Confirm DMARC is published on _dmarc.yourdomain.com and ramp send volume gradually over the first two weeks.

FAQ