ZeptoMail

ZeptoMail — integration guide (3Sigma CRM)

Overview

Add ZeptoMail to 3Sigma to send transactional and marketing emails from your CRM, manage verified senders, and track delivery. This integration follows 3Sigma’s standard integrations pattern (API key + host + sender list) used across other connectors.

---

Who this is for

Admins or users with admin-level access who want to:

• Send email campaigns and transactional messages from 3Sigma

• Use ZeptoMail as the email provider for sequences, templates and notifications

• Manage multiple verified senders for different campaigns

---

Prerequisites

1. A ZeptoMail account with Mail Agent access.

2. Admin access to your 3Sigma organization (to add or disconnect integrations).

3. One or more verified sender email addresses in ZeptoMail.

---

What you’ll enter in 3Sigma

• API Key — the token generated in ZeptoMail (used as zeptoMailApiKey).

• Host (API URL) — ZeptoMail API URL / Mail Agent API endpoint (used as host).

• Senders — array of sender objects { name, email } (one or more verified senders).

These fields map directly to the 3Sigma integration payload: { zeptoMailApiKey, host, senders }. Use the same fields when calling the integration API.

---

Step-by-step: Get credentials from ZeptoMail

1. Sign in to ZeptoMail.

2. Open Mail Agents, select the mail agent you want to use.

3. Go to Setup Info → SMTP / API.

4. Copy the API URL (this is the host value for 3Sigma).

5. Click Generate New Token (or Manage API Tokens) and copy the token — this is your zeptoMailApiKey.

6. Ensure your sender email(s) are verified in ZeptoMail; note their display names and email addresses.

---

Step-by-step: Connect in 3Sigma

1. In 3Sigma, go to Integrations → ZeptoMail.

2. Paste the API Key into ZeptoMail API Key.

3. Paste the Host into Host (example: https://mail.yourdomain.com or the API endpoint shown in ZeptoMail).

4. Add one or more Sender entries (Name + Email).

5. Click Connect.

6. 3Sigma will validate the key and host; on success the integration becomes active and the UI shows connection status and recent logs.

The integration screen requires zeptoMailApiKey and host. Sender emails must be valid and preferably verified in ZeptoMail to avoid delivery issues.

---

UI / fields validation (what 3Sigma enforces)

• zeptoMailApiKey — required, non-empty.

• host — required, non-empty, must be a valid URL/endpoint string.

• senders — at least one sender required. Each sender needs:

  • name — non-empty

  • email — valid email format (server-side and client-side validation) If validation fails, the UI displays a clear error (for example: “Invalid email format for sender 1”).

The 3Sigma React component maps these fields into the payload used by the createUserIntegration('zeptomail', payload) call.

---

Testing the integration

1. After Connect, send a test email (3Sigma provides a “Send test” action in integrations).

2. Check ZeptoMail logs for the API call and delivery status.

3. Verify the “From” header matches a verified sender and the message lands in inbox (or spam — see troubleshooting).

4. Confirm that 3Sigma records the integration log entry and shows connection timestamps in the integration details.

---

Common troubleshooting

• Invalid API Key / 401 errors — regenerate token in ZeptoMail and update zeptoMailApiKey in 3Sigma.

• Host / endpoint errors (404 / timeout) — ensure the host value is the exact API URL ZeptoMail shows under Mail Agent → Setup Info.

• Unverified sender bounce — verify the sender in ZeptoMail (unverified senders often bounce).

• Emails landing in spam — confirm SPF/DKIM/DMARC are set for the sending domain used by ZeptoMail.

• Integration not appearing — refresh integrations list or re-open integration screen; network errors may temporarily block calls.

If issues persist, collect the integration logs shown in 3Sigma integration details and ZeptoMail API logs and open a support ticket.