Skip to main content
Konimbo is an Israeli store platform with a public API and webhooks you can register through that API. Senderz uses both. You paste one API token, Senderz registers the store webhooks for you, imports your existing customers and recent order history, and then keeps up in near real time as orders come in. Konimbo has its own connect form in Senderz. It is not the generic paste-a-key route that some connectors use.

​
What is live today

Customer and order sync

Live. Existing customers and 60 days of order history import on connect, then webhooks keep it current.

Storefront popups

Live. One snippet in your theme footer serves every popup you publish.

Coupons created in your store

Live, but only if you add a Couponimbo API key. Without it the code stays in Senderz and is never created in Konimbo.

Product catalog sync

Not built. Senderz does not import your Konimbo product catalog.
Three storefront features that work on other platforms do not work on Konimbo, and they are covered honestly in Storefront popups below: web push, cart targeting rules, and cart activity tracking.

​
Before you start

  • You need owner or admin access to the Senderz workspace. Connecting a store is workspace-admin work.
  • You need access to your Konimbo admin to generate an API token.
  • Have your Konimbo store domain ready, for example your-store.konimbo.com.
Enter the exact domain your store is connected under. The storefront snippet reports the address the visitor is browsing, and Senderz matches that against the domain you enter here. If they do not match, popups never load. If your live storefront runs on a custom domain, see Storefront popups for the override.

​
Connecting

1

Create an API token in Konimbo

In your Konimbo admin, open Settings → API → Users and generate a token. The connect form links straight to the Konimbo API setup guide if you need the walkthrough.
2

Open the connect form in Senderz

Go to Settings → Integrations, find Konimbo, and click Connect.
3

Fill in the two required fields

Konimbo store domain and API token. There is a third, optional field for a Couponimbo API key. You can leave it blank and add it later by reconnecting.
4

Click Connect

Senderz verifies the token against the Konimbo API, registers the store webhooks, and starts importing your customers in the background. The confirmation panel tells you how many webhooks registered automatically.

​
What the connect form asks for

​
required
For example your-store.konimbo.com. Scheme and trailing slash are stripped, so pasting the full URL is fine.
​
required
Generated in Konimbo under Settings → API → Users. Stored as a secret, never shown back to you.
​
optional
Only needed if you want Senderz to create discount codes in your store when you build a coupon. See Coupons.

​
If the connection is rejected

​
If webhooks did not register automatically

Senderz registers the webhooks through the Konimbo API. If some or all of them fail, the confirmation panel says so and shows you the manual steps with the exact URL and token to copy. Follow them rather than guessing at the URL.
1

Open the webhook screen in Konimbo

Konimbo admin → Settings → Advanced → Webhooks.
2

Add a webhook and pick the event

Click Add webhook and choose one event, for example order_created.
3

Paste the callback URL

Copy the delivery URL from the Senderz panel. It is the same URL for every event.
4

Append the event name and your token

Add ?event=order_created&token=YOUR_TOKEN to the end, using the token shown in the panel. Senderz tells the events apart by that query string, and the token proves the call came from your store.
5

Repeat for each remaining event

Same URL, different event= value each time.
The token in that URL is what authenticates the webhook. A call without it, or with the wrong one, is rejected. Copy it from the panel while it is on screen. Reconnecting the store issues a new one and you would have to update every webhook URL.

​
What syncs

Customers

On connect, Senderz reads your last 60 days of orders and creates a contact per unique email address. New buyers and new store accounts arrive by webhook after that.

Orders

Order history back-fills on connect. Live orders arrive by webhook and record revenue, fill the contact’s activity timeline, start automations, and fire your outbound webhooks.
The customer import is built from orders, not from a customer list, and it skips rows with no email address. A Konimbo customer who has never ordered, or who ordered with a phone number and no email, does not arrive through the initial import. Live order webhooks do create contacts from a phone number alone, so phone-only buyers appear from that point onward.
The initial import covers 60 days of orders. Order history back-fill stops at 25,000 orders and the customer import stops at 50,000 rows. Historical orders are recorded as revenue and timeline entries but deliberately do not start automations. A two-year-old order is not a reason to send someone an abandoned-cart email today.
Only paid orders back-fill as revenue. Senderz reads the Konimbo payment status and skips anything still pending, failed, cancelled or refunded, so your historical revenue total counts real sales rather than every order row.

​
Which Konimbo events become which Senderz triggers

Senderz registers five webhooks. Four of them drive something:
Status changes are matched on the wording of your Konimbo status, in Hebrew or English. Senderz recognises shipping, delivery, cancellation and refund wording. A status that matches none of them is ignored rather than guessed at. If your store uses unusual status names, contact support and the mapping can be set for your workspace.
Placing an order automatically removes the buyer from cart-recovery automations, so they stop getting reminders. See Automation triggers. The inventory webhook is registered but nothing in Senderz acts on it yet. It is harmless to leave in place.
Konimbo tells Senderz about email consent only. It comes from the newsletter opt-in on the order, and it is only ever read as an opt-in. Konimbo never sends Senderz SMS or WhatsApp consent, so contacts synced from Konimbo start unsubscribed on those channels until they opt in somewhere else.
A Konimbo sync can only ever add consent. It never unsubscribes anyone, and it never overturns an opt-out someone made through your preference center or by replying STOP. Every change is written to the consent log with Konimbo recorded as the source, so you can show where an opt-in came from. To collect SMS or WhatsApp consent from Konimbo shoppers, use a storefront popup with the relevant field, or an embedded form. See Consent and suppression.

​
Storefront popups

Konimbo popups are served by one snippet you paste into your theme. Add it once and every popup you publish afterwards appears without touching the theme again. Paste this into your theme footer, under Settings and custom scripts:
If your live storefront runs on a custom domain but you connected a different address in Senderz, name the connected address explicitly:
The full install walkthrough, including how to confirm a popup is actually serving, is in Installing popups on your store.

​
What works and what does not

Web push needs a service worker served from your own domain, and cart rules need a cart your site exposes to the browser. Konimbo provides neither, so Senderz hides the cart rules control rather than shipping a rule that can never match, and a push subscribe block renders but does nothing. Everything else in the popup builder behaves normally.
Product view tracking reads the structured product data your theme already publishes on a product page. If your theme publishes none, no product views are recorded. Checkout and cart page views are still recognised from the page address.

​
Coupons

Senderz can create a discount code in your Konimbo store, but only through Couponimbo.
1

Add your Couponimbo API key

Reconnect Konimbo from Settings → Integrations and fill in the Couponimbo API key field.
2

Create the coupon in Senderz

On the Coupons screen choose Create coupon in store. One code that you choose, and every customer uses the same one.
3

Check the store status

The coupon detail panel shows a Store status row. It reads “Creating in store”, then “In store” once Konimbo confirms it.
Without a Couponimbo API key the coupon still saves in Senderz, but nothing is created in your store and the store status never reaches “In store”. The code will not work at checkout. Add the key before you send it to anyone.
What Senderz can and cannot create in Konimbo: If your workspace has more than one store connected, Senderz creates the coupon in the first one it finds, checking Shopify, then WooCommerce, then Konimbo. See Coupons.

​
Filing synced customers into a list

On the Konimbo integration page, the Customer sync list card lets you pick a list that every customer synced from this store joins.
Joining a list is not consent. What you may actually send a contact is still decided by their own email and SMS opt-in.

​
Checking that data is arriving

The per-event Recent data counters panel is only shown for Shopify and WooCommerce today. It is not rendered on the Konimbo integration page, so do not go looking for it there.
To confirm Konimbo data is landing:
  • Open Contacts and look for recently created contacts with Konimbo as the source.
  • Open a contact who has ordered recently and read the activity timeline. You should see their order and its products.
  • Check the Historical data card on the Konimbo integration page. It shows when the last import ran.

​
Re-syncing

The Historical data card has a Re-import button. Use it after the first install, or after a long disconnection, to pull customers and recent order history again. It also re-runs the order back-fill. Senderz re-imports Konimbo customers automatically once a day on top of that. Nothing is duplicated: orders and contacts already recorded are matched, not created again.

​
Disconnecting

Disconnecting from the integration page stops the sync and deletes the stored API token. Your contacts and historical data are kept.
Disconnecting does not remove the webhooks from your Konimbo store. Senderz has no way to delete them once the token is gone. Open your Konimbo admin, go to Settings → Advanced → Webhooks, and delete the Senderz entries yourself. If you leave them, your store keeps calling Senderz and the calls are rejected.

​
One store, one workspace

A Konimbo store belongs to exactly one Senderz workspace. If you connect the same store domain in a second workspace, the first workspace is disconnected and shown this message:
This store was connected to another workspace. Reconnect it here to resume syncing.
This is deliberate. Two workspaces syncing the same store would double-count orders and split the contact record in half. See Workspaces.

​
Current limits

Senderz does not import your Konimbo product catalog. Product details in email templates and coupons that target specific products both depend on that catalog, so neither is available for Konimbo stores. Products a customer actually bought still appear on their timeline, because those come from the order.
The initial import is built from order history and keys on the email address. Phone-only buyers are picked up later from live order webhooks, not from the initial import.
All three need something Konimbo does not provide. See Storefront popups above.
Delete them in your Konimbo admin. See Disconnecting.