Skip to main content
Integrations bring your customers, orders and on-site behaviour into Senderz, and push Senderz events back out to other tools. Open Integrations from the left sidebar. It is a top-level page, not a settings section. Every tile shows its live status, and clicking one opens a detail page for that connection.
This page is the honest catalogue. Where something is specced but not finished, it says so instead of implying it works. If a connector is not listed here, it does not exist yet. Use Request integration at the top of the Integrations page to tell us what you need.

Store platforms

These four appear as tiles on the Integrations page and sync customers, orders and revenue.

Shopify

OAuth or App Store install. Customer and order back-fill, live webhooks, storefront pixel, popups through a theme app embed.

WooCommerce

Guided connect that mints your store API keys, plus the Senderz WordPress plugin for on-site features.

Konimbo

Dedicated connect flow with webhooks and a storefront snippet.

Magento 2

Paste an integration access token. Orders reconcile by polling, because Magento Open Source has no native outbound webhooks.
Wix is not connectable yet. Senderz can receive and understand Wix webhooks, but there is no way for you to connect a Wix store from the app. There is no Wix tile on the Integrations page and no connect flow behind one. See Wix for the current status.

WordPress

WooCommerce runs on WordPress, so Senderz treats a site as one connection with two halves.
  • Store data is the WooCommerce side: customers, orders, products, revenue.
  • Website features is the Senderz plugin side: forms, popups, web push, checkout consent, cart activity, back-in-stock requests and registered-user sync.
On the Integrations page these show as a single tile called WooCommerce & WordPress, and the detail page walks you through both steps with a status for each. A WordPress site with no shop connects the plugin half only, and the tile guide WordPress or WooCommerce? points you at the right one. The plugin is published on WordPress.org as Senderz Marketing Connect. Install it, open Settings → Senderz in your WordPress admin, and start the connection from there. WordPress sends you into Senderz to approve it, where you pick the workspace the site belongs to. Approving is what hands the site its credentials, so nothing reaches Senderz before you press Connect site. Once connected, the detail page also exposes Marketing consent (which unchecked opt-in boxes appear at checkout and the wording beside each) and Site activity (cart and checkout tracking, back-in-stock requests, registered-user sync).
Every checkout opt-in box is unticked by default, as Israeli law requires. A customer who leaves it unticked is still stored as a contact and is never sent marketing. See Consent and Israeli compliance.

Reviews and loyalty apps

These are live and appear as tiles under the Reviews and Loyalty categories. Connecting one lets review and loyalty activity start automations and feed segments.

Judge.me

Paste your shop domain and private API token. Senderz configures the review webhooks in Judge.me for you.

Loox

Senderz gives you a webhook URL and a signing secret to paste into Loox.

Yotpo Reviews

Senderz gives you a webhook URL and a signing secret to paste into Yotpo.

Yotpo Loyalty & Referrals

Points, tiers, redemptions and referrals arrive as events on the contact.

Rivo

Points, tiers, redemptions and referrals arrive as events on the contact.
For every vendor except Judge.me, connecting is two steps: connect in Senderz to get the URL and secret, then add that webhook in the vendor’s own dashboard. Until you finish the second step nothing arrives.

Payments and invoicing

These have no tile on the Integrations page yet. The connect endpoints are live in the API, and the invoicing choice is live in Settings → Invoicing, but there is nothing to click on the Integrations page to connect them. Treat them as API-only for now. Contact support if you need one wired up.
Settings → Invoicing is where you pick which of iCount, Green Invoice or EZcount issues a VAT-compliant tax invoice and receipt for each subscription renewal and SMS pack purchase. Choosing Off means Senderz issues nothing and you reconcile VAT yourself. A provider that is not connected is labelled Not connected on that screen.

Messaging providers

SmartSend

Paste your SmartSend API key to send WhatsApp from Senderz. The key is verified live at connect time by loading your WhatsApp templates, so a wrong key fails immediately instead of at send time.
SMS carriers are not something you connect. Senderz runs the carrier accounts and bills you in SMS credits, so what you set up is a Sender ID rather than a provider key. See SMS and Sender IDs.

Import sources

Google Sheets

Import contacts straight from a spreadsheet in your Google Drive. Open Contacts → Import, choose Import from Google Sheets, connect your Google account and pick a file.
Senderz only gets read access to the specific spreadsheet you pick in the file picker. Your other Drive files stay private. There is no paste-a-link field, because a sheet you have not picked is not readable. Google Sheets import depends on workspace configuration, so if the option does not appear it is not enabled for you yet. CSV, Excel and tab-delimited uploads work everywhere. See Importing contacts.

Ad audiences

Outbound ad audience sync is not available. Neither Meta Custom Audiences nor Google Customer Match can be connected today. There is no tile, no connect flow and no sync running. Both pages explain the current status and how to move a segment across by hand in the meantime.

Meta audiences

Not available. Manual export only.

Google Customer Match

Not available. Manual export only.

Automation and no-code

Make.com

Build scenarios that read and write Senderz through the public API. Triggers, actions and a universal API-call module.

AI

AI provider

Add your own Claude, Gemini or OpenAI key, or a compatible custom endpoint, from Settings → AI provider. You pay your provider directly. Senderz never resells tokens.

MCP server

Connect Claude, ChatGPT, Cursor or another MCP client to one workspace over OAuth, from Settings → MCP · AI access.
A connected AI assistant acts as you, scoped to one workspace. It cannot bypass consent, quiet hours, the SMS wallet or campaign approvals. Those still enforce on every send.

Developer surfaces

These live under Settings, in the Developers group.

API Tokens

Create keys for the public API, event ingest and embedded forms. A key is shown once at creation, so copy it then.

Webhooks

Subscribe an endpoint of yours to Senderz events and receive signed deliveries. Also reachable from the Integrations page.

Embedded Forms

Paste a subscribe form onto any site, and restrict which websites may submit it.

Attribution

Choose the touch model and look-back window used to credit revenue to campaigns and automations.
Inbound traffic is covered separately in Inbound webhooks, which explains how store and provider events reach Senderz, how each one is verified, and why a redelivery never double-counts. Custom events from your own application go through Events.

How store sync works

Every store connector follows the same shape.
1

Connect

OAuth, a guided key exchange, or a pasted token, depending on the platform.
2

Back-fill

Existing customers import through the same importer a CSV uses. Order history back-fills so lifetime value, RFM and predictive scores have something to work with on day one.
3

Stay in sync

New customers and orders arrive by webhook, or by polling on Magento. On top of that, every connected Shopify, WooCommerce, Konimbo, Magento and Stripe connection is re-synced automatically once a day at 04:00.

How far back order history goes

60 days by default. Shopify restricts older order history unless the app holds the read-all-orders grant for your store. With that grant, Senderz runs a bulk export covering the last two years instead.
Two years. WooCommerce places no equivalent restriction on order history.
60 days.
A back-fill run is capped at 25,000 orders. If a store has more than that in the window, the run stops at the cap and is recorded as incomplete in your workspace log rather than failing quietly, so you can see that it was truncated. You can re-run a back-fill at any time from the Historical data card on the connection’s detail page. Use it after a first install or a long disconnection.

What a connection’s detail page shows

Click any connected tile to open it. Depending on the platform you get:

Customer sync list

The Customer sync list card lets you pick one Senderz list that every customer synced from that store joins. It is available for Shopify, WooCommerce, Konimbo, Magento, Stripe and the WordPress plugin.
Joining a list is not consent. What you may send someone is still decided by their own email and SMS opt-in, not by list membership.

One store account belongs to one workspace

A given store account can be connected to exactly one Senderz workspace at a time. This applies to Shopify, WooCommerce, Konimbo, Magento, Wix and WordPress sites. Connecting a store that is already attached to another workspace moves it. The old workspace’s connection is switched off, its stored credentials for that provider are deleted, and the new workspace takes over. The old workspace keeps its contacts and history, it just stops receiving new data from that store. This is deliberate. Authorising the connection proves you control the store, so the reconnect is treated as the answer rather than as a conflict.
Reconnecting to move a store between your own workspaces is safe and expected. If you did not mean to move it, connect it back from the original workspace.

Where credentials live

Store tokens, provider API keys, webhook signing secrets and AI keys are held in a secrets manager, keyed by workspace and provider. They are never written to the database, to logs, or to disk. Reading a connection back over the API returns whether a credential is present, never the credential itself.
Two things follow from that:
  • A secret shown to you once is shown once. Senderz API keys are displayed at creation and never again. Copy the key before closing the dialog.
  • Disconnecting deletes the stored credential. Reconnecting means pasting or authorising again. Revoke the key in the provider’s own dashboard too if you are cutting access off entirely.

Who can connect

Connecting, reconnecting, disconnecting, syncing and changing an integration’s settings are owner and admin actions. Anyone in the workspace can view the Integrations page and see connection status. Building something of your own? GET /integrations returns every provider and its status for the current workspace, so you can read connection state without scraping the page. See the API reference.

Request an integration

Use Request integration at the top of the Integrations page. Give the service name, an optional website, and at least 10 characters explaining what you would use it for. Requests appear under Integration requests on the same page with a Pending or In review status.