Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    SendPulse Transactional Email (SMTP)

    1

    Send transactional email via SendPulse SMTP API or relay: setup, SPF/DKIM, bounces and deliverability fixes.

    Free

    1 useSecurity scanned
    SendPulse Transactional Email (SMTP)

    SendPulse Transactional Email (SMTP)

    Example session with this skill installed

    Send an order confirmation email via SendPulse from my Node.js app when an order is paid.

    • Read your context and instructions
    • Compiled the sendpulse transactional email

    Order confirmation via SendPulse SMTP API

    Summary: before sending, confirm 4 things in SendPulse, then drop in this function.

    Checklist

    #CheckWhere
    1SMTP account activated (profile filled, moderation passed, up to 24h)SMTP → Settings
    2Sender verified, on your own domain (not gmail.com)SMTP → Settings
    3SPF and DKIM added to your domain DNSSMTP → Settings
    4API key created, stored in SENDPULSE_API_KEYSettings → API

    Code (Node.js 18+)

    export async function sendOrderConfirmation(order) {
      const html = `<h1>Thanks, ${order.name}!</h1><p>Order #${order.id} is confirmed.</p>`;
      const res = await fetch('https://api.sendpulse.com/smtp/emails', {
        method: 'POST',
        headers: {
          Authorization: `Bearer ${process.env.SENDPULSE_API_KEY}`,
          'Content-Type': 'application/json',
        },
        body: JSON.stringify({
          email: {
            subject: `Your order #${order.id} is confirmed`,
            from: { name: 'My Shop', email: 'noreply@myshop.com' },
            to: [{ name: order.name, email: order.email }],
            html: Buffer.from(html).toString('base64'),
            text: `Thanks, ${order.name}! Order #${order.id} is confirmed.`,
          },
        }),
      });
      const data = await res.json();
      if (!data.result) throw new Error(`SendPulse error: ${JSON.stringify(data)}`);
      return data.id; // store it to check delivery status later
    }
    

    Why it's written this way

    • html is Base64-encoded, raw HTML fails.
    • A plain-text version is included for better deliverability.
    • to is an array even for one recipient.
    • The returned id lets you check status via GET /smtp/emails/{id}.

    Next steps

    1. Process bounces daily: GET /smtp/bounces/day.
    2. Check the unsubscribe list before sending: GET /smtp/unsubscribe/search?email=....
    3. Need a nicer email design? Use sendpulse-template-skill.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Teaches your AI agent to send transactional email through SendPulse: order confirmations, password resets, notifications, invoices. One email per app event, triggered by your code.

    What it does

    • Picks the right transport: REST API (POST /smtp/emails, recommended) or SMTP relay (smtp-pulse.com:465) for PHPMailer, nodemailer, WordPress and other SMTP-only apps
    • Walks you through the 4 prerequisites before any code: activated SMTP account, verified sender on a corporate domain, SPF and DKIM, API credentials
    • Writes working send code with the rules that break most integrations: Base64 html, plain-text version, to as an array, storing the message id
    • Builds good-sender habits in: unsubscribe checks, daily bounce processing, domain warm-up, 429 backoff
    • Diagnoses "email not sending / in spam" with a step-by-step checklist

    Why this beats prompting it yourself

    Generic models send raw HTML instead of Base64, forget that free mailbox domains (gmail.com etc.) are rejected as senders, and skip the SMTP account moderation step. This skill checks all of that first.

    Works with

    • SendPulse REST API: cURL, PHP, Python, Node.js examples
    • SendPulse MCP server for account checks from chat (senders, stats, unsubscribes)

    Install via CLI

    npx skills add sendpulse/sendpulse-skills --skill sendpulse-smtp-skill

    Official skill by SendPulse. Source: https://github.com/sendpulse/sendpulse-skills

    Learn more: https://sendpulse.com/features/smtp?utm_source=agensi&utm_medium=skill-directory&utm_campaign=ai-skills&utm_content=sendpulse-smtp-skill

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.

    These are SendPulse rules the skill handles for you: the SMTP account must pass moderation (usually up to 24h) before it sends; the sender must be verified and on a corporate domain (gmail.com and other free domains are rejected); SPF and DKIM are needed to avoid spam. Not for newsletters to a list (use sendpulse-email-skill) or HTML email design (use sendpulse-template-skill).

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 27 days ago

    • Free with an Agensi account

    Accounts
    Smtp PulseSendPulse account
    SendPulse API key
    orSMTP login
    Software
    Git

    Activate the SMTP service in your SendPulse account. The SMTP login is for relay.

    Permissions

    Terminal / Shell
    Read Files
    Network Access
    Environment Variables

    Allowed Hosts

    api.sendpulse.com
    smtp-pulse.com

    Network access is used only to call the SendPulse API (api.sendpulse.com) or SMTP relay (smtp-pulse.com). Credentials are read from environment variables and never hardcoded.

    Listed28 days ago
    Updated27 days ago

    What's inside

    Frequently Asked Questions

    This skill automates the complex configuration required for SendPulse transactional delivery, specifically handling Base64 HTML encoding and corporate domain validation to prevent silent delivery failures.

    Yes, the skill is designed to work across any environment that supports HTTP or SMTP, including specific implementations for Python, Node.js, PHP, and WordPress.

    The skill focuses exclusively on transactional email delivery via SMTP and REST API; it does not include tools for managing bulk marketing campaigns, A/B testing, or list segmentation.

    You will receive the logic for transport routing, authentication handling (including OAuth2 refresh logic), payload validation structures, and deliverability auditing protocols.

    The skill requires an active SendPulse account and a verified corporate domain, as the SendPulse API rejects transactional emails sent from free mailboxes like Gmail or Yahoo.

    This skill is compatible with AI agents and platforms that support MCP (Model Context Protocol) or standard API integration layers for interactive account management.

    SMTP is for one email per app event (order confirmation, password reset). Campaigns are for sending one newsletter to a whole list. For campaigns use sendpulse-email-skill from the same repo.

    Yes. The skill covers both the REST API and the SMTP relay (smtp-pulse.com, port 465, SSL) for apps that only speak SMTP.

    SendPulse rejects free mailbox domains as senders. Use an address on your own domain and add SPF and DKIM records, the skill shows you how.

    New in APIs & Backend

    Free