
Selzy documents around 30 native integrations, ships a Zapier app that reaches 9,000 other apps through just 2 triggers and 2 actions, and leaves everything else to a flat REST API capped at 1,200 requests per 60 seconds. There is no marketplace page and no headline number, the real directory is the integration section of the Selzy help center, where each connector has its own setup article. Counted there, the catalogue is roughly 12 CRM and helpdesk connectors, 5 e-commerce, 3 CMS, 4 form builders and a tail of data, ads and automation services.
Read the shape before committing: these are almost all contact-in connectors. They move people and field values from a CRM, store, form or spreadsheet into a Selzy list so campaigns can target them. They are not two-way data platforms, and only one documented pair (Facebook Lead Ads in, Ads Manager out) sends data back. Transactional sending is a separate product with its own account and hosts, see SMTP settings. For a deep bidirectional e-commerce sync compare Brevo; on no-code breadth for a small list, MailerLite and Sender.net are the closer peers.
The 26 connectors below are the ones most buyers shortlist, each with its own Selzy setup article, grouped the way a buyer evaluates them rather than the way the help center files them. Several need API access switched on first-Settings › Integration and API, then re-enter your account password to reveal the key. Full index: the Selzy integration help center. Building your own listed connector? Read the integration guidelines first: they impose a mandatory platform parameter on every API call.
Two documented directions: new HubSpot contacts into a Selzy list, then later field updates pushed across.
Connects Salesforce leads and contacts to Selzy lists so sales-captured records become subscribers.
Syncs Zoho CRM contacts and leads into Selzy lists for campaign targeting.
Pushes Pipedrive persons and deal-stage changes into Selzy lists so lifecycle emails fire off pipeline movement.
The most granular CRM connector Selzy documents: three triggers, covering new contacts and both directions of a deal-status change.
Connects Bitrix24 CRM records to Selzy subscriber lists.
Turns Zendesk users and ticket contacts into Selzy subscribers for follow-up campaigns.
Sends Freshdesk contacts into Selzy lists so support conversations feed automation.
Syncs Shopify customers into Selzy lists so store activity can drive campaigns and automation scenarios.
Passes WooCommerce customer and order data into Selzy lists. Filed under CMS in the help center, not e-commerce.
Latin-American storefront sync, and a genuine differentiator: few European senders document one.
Selzy’s own PHP plugin builds subscription forms and posts contacts to a list with your API key. Distributed from the help center and selzy-dev on GitHub, not wordpress.org.
Connects Wix site forms and contacts to Selzy subscriber lists.
Maps Typeform answer fields onto Selzy contact fields; each submission creates or updates a subscriber.
Sends Jotform submissions into Selzy lists with per-field mapping.
Passes Marquiz quiz leads into Selzy lists, with quiz answers available as contact fields.
Spreadsheet as contact source or destination. The pragmatic bridge for any system with a CSV export.
Syncs Airtable base records to Selzy contacts, for teams whose CRM is really a base.
Adds UTM and GA tracking to campaign links. Campaign tracking only, not an audience sync.
Collects Facebook lead-form submissions into Selzy contact lists as they arrive.
Exports Selzy leads to Ads Manager for retargeting: the only documented outbound audience push.
Official app: 2 triggers (New Subscriber, New Unsubscriber) and 2 actions (Add a New Contact, Unsubscribe a Contact). Campaigns, templates and stats are out of scope.
Second documented iPaaS bridge, for when Zapier per-task pricing does not suit the volume.
Generate a catcher URL, post any JSON at it, then map inbound fields onto Selzy contact fields. Trigger-only: it cannot be used as an action.
Selzy’s own chatbot channel: create a Telegram bot, connect it, then build flows in Selzy’s builder.
The Selzy team’s own SMTP relay and Email API, on smtp.eu1.unione.io or smtp.us1.unione.io. Separate signup, credentials and domain verification.
Roughly 30 connectors with their own setup articles: 12 CRM and helpdesk tools (HubSpot, Salesforce, Zoho, Pipedrive, Kommo, Bitrix24, Zendesk, Freshdesk and more), 5 e-commerce platforms, 3 CMS and site builders, 4 form builders, Google Sheets, Airtable, Facebook in both directions, Zapier, Pabbly Connect and a generic incoming webhook. Selzy publishes no official total and its /en/integrations/ page is a stub, so treat the count as an enumeration of the help center, not a vendor claim.
Use the native Shopify connector. It authorises against your store and syncs customers into a chosen Selzy list, which then feeds campaigns and automation scenarios. Watch the direction of travel: it is a customer sync, not a full order-and-product feed, so cart logic driven by line-item data needs the REST API or an iPaaS step. WooCommerce uses a separate connector, filed under CMS.
Yes, written by Selzy, but not on the wordpress.org directory: it comes from the help center and the selzy-dev GitHub account, is a small PHP repository with no tagged releases, and needs a Selzy API key. It builds subscription forms and posts contacts into a list. Making WordPress send its own transactional mail is a different job: point an SMTP plugin at UniOne on smtp.eu1.unione.io or smtp.us1.unione.io, port 587 with STARTTLS, per the SMTP settings tab.
Yes, with a deliberately narrow app: 2 triggers (New Subscriber, New Unsubscriber) and 2 actions (Add a New Contact, Unsubscribe a Contact). Enough to wire a form, store or CRM into a list across roughly 9,000 apps; not enough to create campaigns, manage templates or pull statistics. Anything beyond contact-level work goes through the REST API or Pabbly Connect.
Enable API access under Settings › Integration and API, reveal the full key (your account password is requested again), then set up the native HubSpot connector: new contacts land in a Selzy list and later field updates propagate. For a one-off backfill of an existing database, call importContacts rather than looping subscribe, which is capped at 300 requests per 60 seconds.
Use the incoming webhook connector: Selzy generates a catcher URL, you paste it into the sending service, fire a test payload, then map the inbound JSON onto contact fields. It is trigger-only, so it receives but never sends, outbound events are registered with setHook, and your receiver must answer HTTP 200 within 3 seconds or Selzy retries every 10 minutes for 24 hours, then marks the hook stopped.
This review follows our email infrastructure testing methodology. We disclose affiliate relationships in our editorial independence policy.