Integrating with Zapier

Zapier is a no-code automation platform that connects thousands of apps through simple trigger-action workflows called Zaps. You can connect MigoSMTP and Telnxo to Zapier to automate email and SMS sending based on events in other tools — CRMs, e-commerce platforms, forms, spreadsheets, and hundreds more — without writing any code.

What You Can Automate with Zapier

Connecting MigoSMTP to Zapier

Prerequisites

• A Zapier account (free plan supports up to 5 Zaps with 100 tasks/month).
• A MigoSMTP API key with send scope — generated from Dashboard → API Keys.
• At least one verified sending domain in MigoSMTP.

Setup Steps

1. Log in to Zapier and click Create Zap.
2. Set up your Trigger app (e.g. Google Sheets, HubSpot, WooCommerce).
3. For the Action step, search for MigoSMTP or use the Webhooks by Zapier action to call the MigoSMTP API directly.
4. If using Webhooks by Zapier — select POST as the method and enter:
   • URL: https://api.migosmtp.com/v1/email/send
   • Headers: Authorization: Bearer YOUR_API_KEY and Content-Type: application/json
   • Data: JSON body with from, to, subject, and html fields mapped from your trigger data
5. Test the Zap by clicking Test & Review — Zapier fires a test payload and shows the MigoSMTP response.
6. Verify the test email arrived in your inbox.
7. Click Publish Zap to make it live.

Connecting Telnxo to Zapier

Prerequisites

• A Telnxo API key with sms:send or whatsapp:send scope.
• A registered Sender ID (for SMS) or approved WhatsApp template.

Setup Steps

1. In your Zap's Action step, use Webhooks by Zapier → POST.
2. Enter the Telnxo API endpoint:
   • SMS: https://api.telnxo.com/v1/sms/send
   • WhatsApp: https://api.telnxo.com/v1/whatsapp/send
3. Set Headers: Authorization: Bearer YOUR_TELNXO_API_KEY and Content-Type: application/json
4. Map the JSON body fields from your trigger data (phone number, message text, Sender ID).
5. Test and publish.

Zapier Request Body — MigoSMTP Email

{
  "from":    "hello@yourdomain.com",
  "to":      "{{trigger_email}}",
  "subject": "Welcome, {{trigger_first_name}}!",
  "html":    "<p>Hi {{trigger_first_name}}, thank you for signing up.</p>"
}

Zapier Request Body — Telnxo SMS

{
  "from":    "YOURBRAND",
  "to":      "{{trigger_phone}}",
  "message": "Hi {{trigger_name}}, your order #{{trigger_order_id}} is confirmed."
}

Tips for Reliable Zapier + Rackwave Integrations

• Validate phone numbers — use Zapier's Formatter tool to clean phone numbers to E.164 format (+91XXXXXXXXXX) before passing to Telnxo, as raw numbers from CRMs often lack country codes.
• Handle empty fields — use Zapier's filter step to skip the action if critical fields (email, phone) are empty, preventing API validation errors.
• Monitor Zap history — check Zapier's Task History regularly for failed runs. Failed tasks show the API error response from MigoSMTP/Telnxo to help you diagnose issues.
• Use multi-step Zaps — add a Paths step to send email for some trigger conditions and SMS for others, creating a conditional multi-channel notification from one trigger.

Next Steps

• API authentication — bearer token guide
• Send email API — endpoint reference
• SMS Send API — endpoint reference