SendX Integrations: Native, Zapier, and API
SendX approaches integrations from the marketing side: a curated partner directory covering six categories, an officially maintained Zapier app reaching 9,000+ apps, and one REST surface at api.sendx.io/api/v1/rest wrapped by six official SDKs. What it lacks is a relay: no SMTP hostname, port or credential is issued to SendX accounts, so every integration here is a hosted connector, a Zapier hop, or an HTTPS call.
The stack is narrower and deeper than the marketplaces of Brevo or MailerLite: first-party connectors for the systems that feed a contact list — storefront, CMS, payments, CRM — and everything else through Zapier or your own code.
At a glance
In short: a small native tier, breadth outsourced to Zapier, anything bespoke written against the REST API. Full API access ships on every paid plan, so the developer column is live from $9.99/month for 1,000 contacts. The one real paid gate is the Transactional Email add-on: $10/month for 3,000 emails, then $0.003 each.
Integrations directory
The 25 entries below are grouped the way you shop for them: what SendX hosts, what you reach through Zapier, and what you build. Partner listings sit at the SendX integrations directory; triggers and actions are on the Zapier app page. Where an official per-app deep link could not be confirmed, the card points at the parent directory, not a guessed URL.
Native & partner
Zapier
Developer & API
SDKs
Native & partner (5)
Connectors SendX hosts and supports itself. You authenticate in the SendX UI, sync runs server-side, and no Zapier task quota sits in the path.
Official plugin for embedding forms and syncing blog subscribers. It captures contacts — it does not route your site’s outbound mail.
Feeds customers and order activity into lists and automations — what abandoned-cart and post-purchase sequences run on.
Headline e-commerce connector syncing customers into contacts so purchase data drives campaigns, tags and segments.
Brings customers and payment activity in so revenue-aware flows — failed payment, upgrade, churn — fire without webhook glue.
Keeps CRM records and SendX audiences aligned so sales-owned contacts and marketing-owned lists do not drift apart.
Forms & lead capture (4)
SendX ships its own form and popup builder, so this tier is for when the capture surface lives elsewhere. Each entry rides the Zapier app, so every submission burns a task and inherits Zapier latency.
Turns submissions into contacts, with answers mapped onto tags or custom fields for segmentation.
Feeds respondents and their scored segments in as tagged contacts.
Pushes landing-page opt-ins straight into lists, keeping page builder and ESP decoupled.
Routes popup and sticky-bar captures in as tagged contacts, useful when the bar is already deployed site-wide.
Automation & no-code (4)
Where SendX gets its advertised breadth. The official app exposes three triggers (Contact Created, Get Tags, Get List) and three actions (Create or Update Contact, Add Tag to Contact, Remove Tag From Contact). Read that carefully: every action is a contact or tag operation. Nothing sends a campaign, builds a template or fires a transactional message, so anything past list hygiene drops to the REST API. Integrately and Zoho Flow carry SendX connectors too.
Three triggers and three contact-and-tag actions, connectable to 9,000+ destination apps.
The most-featured SendX Zapier pairing: pushes purchasers into lists and tags them at checkout.
Creates or updates contacts from rows and logs events back to a sheet. The pragmatic fallback for one-off imports.
Used during migration to mirror an audience into SendX before cutover. Re-verify DKIM before switching sending.
Developer & API (6)
Everything without a tile is reachable here. Base URL https://api.sendx.io/api/v1/rest, auth a single X-Team-ApiKey header over HTTPS. Two constraints: the reference states the API has no bulk updates, so a 50,000-contact sync is 50,000 calls; and no rate limit is published, so you size concurrency empirically with backoff.
The v1 surface: contacts, lists, tags, campaigns, senders, templates, segments, webhooks, events, reports, tracking. IDs are opaque strings.
Metered POST /send/email for receipts and app mail. Needs a paid plan, an explicit toggle and a verified domain. API only.
Outbound event delivery to your own endpoint, exposed in every SDK. The way to get data out without polling.
Ties an anonymous visitor to a known contact so on-site behaviour drives automations.
Records custom and revenue events against a contact, which is what makes revenue reporting work outside the native tier.
Sibling product from the same parent company, marketed as Email API + SMTP Relay — the relay SendX lacks. Separate signup, demo-gated.
Official SDKs (6)
SendX regenerated its whole client set in late 2025: five languages on September 8, 2025, JavaScript on December 23, 2025. All MIT licensed. One trap: the org still hosts a dormant generation named sendx-api-{lang}, last touched 2016 to 2020. Install the sendx-{lang}-sdk series instead.
npm install sendx-javascript-sdk. Freshest of the six and the de facto reference implementation.
pip install sendx, needs Python 3.9+. A legacy PyPI listing under a differently cased name also exists.
composer require sendx/sendx-php-sdk. Natural fit for a WordPress or Laravel codebase.
Added via Maven or Gradle per the repo README. Part of the September 8, 2025 wave.
gem install sendx-ruby-sdk. Generated from the same spec as the other five.
go get github.com/sendx/sendx-go-sdk. Not the org’s Go SMTP server libraries, which are MTA parts.
Frequently asked questions
What integrations does SendX support natively?
SendX publishes a partner directory in six categories: Communication, CRM, E-Commerce Platforms, Email Marketing, Marketing Automation and Payment Processing. The ones people actually use are Shopify and WooCommerce, Stripe for payments, HubSpot for CRM, and the WordPress plugin for forms and blog subscribers. No exact native count is published, so treat any number quoted elsewhere as unverified.
How do I connect SendX to Shopify or WooCommerce?
Both are native connectors configured inside SendX, not through Zapier. Shopify syncs customers into contacts; WooCommerce feeds customers and order activity into lists and automations, which abandoned-cart and post-purchase sequences run on. Authenticate the store once and the sync runs server-side, consuming no Zapier tasks. Confirm your sending domain is verified first — an unverified domain blocks sends regardless.
Does SendX work with Zapier, and what triggers and actions are available?
Yes, and Zapier is where the 9,000+ app reach comes from. The official app exposes three triggers (Contact Created, Get Tags, Get List) and three actions (Create or Update Contact, Add Tag to Contact, Remove Tag From Contact). Every action is a contact or tag operation. None sends a campaign, builds a template or fires a transactional email, so anything beyond list hygiene goes through the REST API.
Is there an official SendX WordPress plugin?
Yes, maintained in the company’s GitHub org, for embedding capture forms and syncing blog subscribers. Be clear on what it is not: a mail router. You cannot point WP Mail SMTP, Easy WP SMTP or WooCommerce transactional mail at SendX, because no SMTP hostname, port or credentials are issued. If WordPress system mail needs an authenticated relay, pair SendX with a self-serve one such as Brevo, Postmark or Amazon SES, each on its own subdomain.
How do I sync Stripe customers into SendX?
Use the native Stripe integration, which pulls customers and payment activity in so revenue-aware automations fire without custom webhook glue. For anything it misses — a plan change, a trial milestone — the Events API is the escape hatch: POST a custom or revenue event against the contact and segment on it. There are no bulk endpoints, so a backfill is one call per contact; use conservative concurrency and exponential backoff, since no numeric rate limit is published.
How do I migrate from Mailchimp to SendX?
Export the audience, then import it in the SendX UI or mirror it with the Mailchimp-to-SendX Zapier pairing during a parallel run. What breaks migrations is DNS, not data. Mailchimp hands you CNAME records that delegate DKIM; SendX does the opposite and requires a TXT record at host sp-dkim._domainkey with a per-domain key copied from the dashboard. Creating a CNAME there is the most common SendX misconfiguration. You add nothing for SPF either: SendX states SPF is handled on its side, so do not paste an invented include string. Worth pricing the move against MailerLite, EmailOctopus and Sender too, since contact-based pricing rewards different list shapes.
This review follows our email infrastructure testing methodology. We disclose affiliate relationships in our editorial independence policy.
