SendPulse is not a single-channel ESP with a plugin list bolted on. Its own marketplace enumerates 60+ native apps across ecommerce, CMS, CRM, pop-up builders, payments and telephony; the Zapier app reaches roughly 9,000 other services through 3 triggers and 5 actions; and underneath both sits a REST platform with 16 documented service surfaces — bulk email, SMTP relay, SMS, web push, CRM, Automation 360, Courses and seven messenger channels — all authorised by one OAuth2 token. SendPulse also runs an official MCP server at mcp.sendpulse.com/mcp, which puts it ahead of most mid-market ESPs on AI-agent access. The caveat that shapes everything else: the SMTP relay and Email Marketing are separate products with separate quotas, so an integration that feeds a mailing list does not touch your transactional capacity.
Read those as three different buying signals. The native list is what you wire up in an afternoon with no code. The Zapier figure is what is reachable but event-shaped and narrow. The API surface count is what an engineering team can build against — and it is the number separating SendPulse from list-only tools such as MailerLite or Moosend, which carry no chatbot, CRM or course surfaces under the same credential.
The 26 connectors below have published SendPulse documentation or a first-party marketplace listing, grouped by what they do rather than by marketing category. Full listings live at the SendPulse integrations marketplace and the app directory knowledge base. Tags mark how each connects: NATIVE is a first-party connector configured in the dashboard, API is listed as supported but has no first-party setup guide, and ZAPIER runs through the Zapier app.
Official WhatsApp Business API channel with template management, carousel messages and, since August 2026, voice calls inside the 24-hour service window.
Visual bot builder with flow automation, bulk campaigns and a dedicated REST surface under the /telegram/ prefix.
Instagram Direct chatbot covering comment-to-DM automation and story reply handling.
Messenger bot builder with flow automation and subscriber segmentation shared with the email audience.
Viber chatbot channel plus a separate Viber broadcast campaign API for one-to-many sends.
TikTok messaging chatbot channel, shipped with its own OpenAPI specification alongside the other messengers.
Website chat widget sharing the same operator inbox and dialog API as every messenger bot, so human handoff behaves identically across channels.
Syncs customers and order events so one audience drives email, pop-up, web push and SMS automation.
Pushes store customers and order data into SendPulse mailing lists and the built-in SendPulse CRM.
Official module that keeps PrestaShop customer records in step with SendPulse mailing lists.
Official plugin adding subscription forms and wiring the site to SendPulse email marketing and the SMTP relay.
SendPulse module for Drupal sites that collects subscribers straight into mailing lists.
Email marketing module for OpenCart storefronts.
Exports Pipedrive contacts into SendPulse mailing lists so deal-stage audiences can be mailed directly.
Drives personalised SendPulse campaigns from Creatio CRM records and workflow state.
Connects Binotel cloud telephony to the SendPulse CRM so inbound and outbound calls create and update deals.
Listed as a supported integration for syncing Salesforce contacts into campaigns, with no dedicated first-party setup guide.
Sends Typeform responses straight into SendPulse mailing lists without an intermediate automation step.
Exports OptinMonster opt-in contacts into SendPulse if you prefer its targeting rules to the built-in pop-up builder.
Accepts card payments inside SendPulse landing pages, online courses and chatbot checkout flows.
Payment acceptance for SendPulse storefronts, courses and bot-driven checkout.
Official MCP endpoint letting Claude, ChatGPT, Cursor, VS Code Copilot and Devin drive chatbots, CRM, Courses, email and SMTP.
The reverse direction: a SendPulse chatbot acts as MCP client and calls your own backend or CRM mid-conversation, with Bearer or custom-header auth.
Official SendPulse nodes for n8n, plus reverse triggers that start an n8n workflow after a successful SendPulse payment.
SendPulse modules for Make, plus a generic API-call module reaching any endpoint the documented modules miss.
Connects SendPulse subscriber events to roughly 9,000 apps, but only through 3 triggers and 5 subscriber-level actions.
Two entries there deserve separate reading, because a search for “SendPulse MCP” returns both and they answer opposite questions. mcp.sendpulse.com/mcp is SendPulse acting as an MCP server, so an assistant can list your bots or launch a campaign. The chatbot MCP integration is SendPulse acting as an MCP client, so your bot queries your own order system mid-conversation. Only the first matters when evaluating agent access to your stack.
Two rows are thinner than a marketplace listing implies. Salesforce and HubSpot both appear on the SendPulse integrations page without a dedicated setup guide, which usually means delivery through Zapier or Make — verify the mechanism before scoping a migration around either. And Zapier itself carries only 3 triggers and 5 actions, so anything richer needs the REST API. For deeper first-party catalogues on the pure email side, compare Brevo and GetResponse.
Two separate connectors. The WordPress plugin adds subscription forms and points the site at SendPulse email and SMTP; the WooCommerce integration pushes store customers and order data into mailing lists and the SendPulse CRM. If the goal is transactional delivery rather than list building, relay through smtp-pulse.com on port 465 or 587 using the login and password from SMTP settings › General.
Yes. The connector syncs customers and order events, and those events start an Automation 360 flow covering email, web push, SMS and chatbot steps. Abandoned-cart mail runs against your Email Marketing quota, not your SMTP relay quota — the two are billed and throttled separately.
Both are native channels in the chatbot builder, not third-party add-ons. Telegram connects with a BotFather token; WhatsApp runs on the official Business API and needs Meta-approved templates, which SendPulse submits for review through POST /whatsapp/templates. Since August 2026 WhatsApp bots also support voice calls inside the 24-hour service window.
All three, with different ceilings. n8n and Make have first-party modules, and Make exposes a generic API-call module reaching any endpoint. Zapier connects to roughly 9,000 apps but only through 3 triggers and 5 subscriber-level actions. For campaigns, templates, CRM deals or transactional sending, call the REST API directly.
Pipedrive, Vtiger, Creatio and Uspacy have first-party connectors that export contacts into SendPulse mailing lists. Salesforce and HubSpot are listed as supported but have no dedicated setup guide, so they are most likely delivered through Zapier or Make — confirm before committing. SendPulse also ships its own CRM with a REST surface at /crm, often simpler than syncing an external one on a lightweight pipeline.
Open Bot settings › Integrations › MCP servers, paste the external server URL, authenticate with a Bearer token or custom headers, then click Get tools to discover its commands. The bot calls those tools live during a conversation. This is the inbound direction and is unrelated to the official server at mcp.sendpulse.com/mcp, which you register in Claude, ChatGPT or Cursor to drive your account from outside.
This review follows our email infrastructure testing methodology. We disclose affiliate relationships in our editorial independence policy.