Scalev Integration
Connect your Scalev store to Konektor. Each Scalev order is saved in Konektor and linked to the lead with the same WhatsApp number.
After you connect, Konektor can:
- Create a new lead for a buyer who is not in your list yet.
- Change the lead status: Invoice Sent when the order is created, Purchase when the order is sold.
- Run order flows: confirmation messages, payment reminders, checkout recovery, and thank-you messages from your WhatsApp number.
- Send one Purchase event for each sold order to your ad platforms (optional, off by default).
Who this is for
Use this integration if you sell on Scalev and close sales on WhatsApp. You do not change your Scalev order pages.
Prerequisites
- A Scalev account on the Basic plan or higher. Scalev webhooks do not work on a lower plan. Scalev shows a notice about the plan on its Webhooks page.
- Owner access to the Konektor workspace.
- For automatic messages: at least one WhatsApp number connected to the Konektor Inbox.
Owner only
Only the workspace Owner can create, change, pause, and delete stores. Other roles do not see the Store & orders menu.
Connect Scalev
The setup has three steps. Open two tabs: Konektor and Scalev.
Step 1: Create the address in Konektor
- Open Settings > Store & orders.
- Click Connect a store, then choose Scalev.
- Enter a Store name, then click Create address.
- Click Copy to copy the webhook address. You can see it again with Show address on the store card.
Step 2: Add the address in Scalev
- In Scalev, open Settings > Developers > Webhooks.
- Click Add Endpoint, then paste the address from Konektor in Webhook Endpoint URL.
- Tick the events that you want to send to Konektor:
- Order Created, Order Updated, Order Status Changed, and Order Payment Status Changed.
- Order E-Payment Created.
- Payment Received and Payment Failed.
- Checkout Intent Abandoned and Checkout Intent Completed (for checkout recovery).
- Switch the endpoint to Active. A new endpoint is Inactive, and Scalev sends nothing until you switch it on.
- Click Save Endpoint. When you save an active endpoint, Scalev sends one test message to the address.
- Go back to Konektor, then click I pasted it. The page waits up to 5 minutes for the test message, then shows "The test from Scalev arrived."
Konektor does not use Shipment Status Updated, Subscription, and WhatsApp Message. Do not tick them. Shipped, completed, and returned status arrive through Order Status Changed.
Scalev allows up to 3 webhook endpoints for each business. Your other tools keep their endpoints. Add the Konektor address as a new endpoint.
Step 3: Paste the Signing Secret
- In Scalev, copy the Signing Secret of your business. It shows on the same Webhooks page. One Signing Secret serves your whole business.
- In Konektor, paste it in the Signing Secret field, then click Save.
- Click Done. The store card shows Waiting for orders until the first order arrives. After that, it shows Active and the time of the last order.
Keep the address and Signing Secret private
A person who has both can send fake orders to Konektor. If the address leaks, click Create new address on the store card. The old address stops at once. Then change the address of the endpoint in Scalev.
Scalev API key (optional)
You can paste a Scalev API key in the store settings. Konektor uses it only to read one order again from Scalev, for example to get a missing payment link, total, or phone number.
- Create the key in Scalev, under Settings > Developers > API Keys. Use a secret key, or a restricted key that can read and list orders.
- Without an API key, a message with
{{payment_link}}is skipped when the order has no payment link. - Click Check to test the API key. The result is valid, not valid, or Scalev is not reachable.
- Konektor shows only the last 4 characters of a saved key.
The three store settings
Open the store card in Store & orders, then click Settings.
| Setting | Default | What it does |
|---|---|---|
| Create leads from orders | On | An order from a new number creates a new lead. The daily lead limit of the workspace still applies. |
| Update the lead status | On | The lead status moves forward only: Invoice Sent, then Purchase. A cancelled order sets the status to Lost only when the lead is still Invoice Sent and has no other open or sold order. |
| Send Purchase to ad platforms | Off | Sends one Purchase for each sold order. |
Turn on Purchase only when needed
Scalev can also send Purchase to your pixel. If both systems send to the same pixel, Meta can count one sale two times. Turn this setting on only when Scalev does not send Purchase to the same pixel.
When an order counts as sold
- Non-COD order: at the first confirmed payment.
- COD order: when Scalev marks the order completed.
The Purchase value equals the total that the buyer pays. Konektor sends one Purchase for one order. A repeat order from the same buyer sends a new Purchase. A checkout record never sends a Purchase.
Konektor sends a Purchase only for an order with a known total. Some Scalev events hold no total. In that case, Konektor waits up to 1 hour for the next event of that order. If you saved a Scalev API key, Konektor reads the total from Scalev. If the total stays unknown, Konektor skips the Purchase.
The Purchase uses your event mapping for the Closed won status in Conversion Settings. The Leads page calls the same status Purchase. Konektor sends it to every active ad platform.
Check that it works
- Create a test order in Scalev with your own WhatsApp number.
- In Store & orders, click Recent events on the store card. The list shows the event type, the time, and the result. It shows no buyer data.
- Open Leads and click the lead with that number. The order shows in the Store orders section. The flow results show under the order.
Store states that you can see:
| State | Meaning |
|---|---|
| Signing Secret needed | The address is set, but you did not save the Signing Secret. |
| Waiting for orders | The store is ready, but no order arrived from Scalev yet. |
| Active | Orders arrive and Konektor processes them. The card shows the time of the last order. |
| Paused | Konektor does not accept orders from Scalev. |
| Needs a check | There is a problem. The card shows the message, for example "The data from Scalev was rejected". |
Results that you can see in the event list:
| Result | Meaning |
|---|---|
| Processed | Konektor processed the event. |
| Waiting to retry | Konektor waits, then tries again by itself. The reason shows under the event. |
| Skipped | Konektor changed nothing. The reason shows under the event. |
| Failed | Konektor stopped trying. The reason shows under the event. |
Common problems
The data from Scalev was rejected
The store card shows Needs a check and the message "The data from Scalev was rejected. Copy the Signing Secret from Scalev again." The Signing Secret in Konektor is different from the one in Scalev. Copy the Signing Secret again from Scalev, paste it in the store settings, then click Save.
Scalev does not save the endpoint
Scalev sends a test when you save an active endpoint. If Konektor does not answer, Scalev reports that the test failed and does not save the endpoint.
- Make sure the store in Konektor is not Paused. Click Resume if needed.
- Make sure you pasted the newest address. An old address stops working after you click Create new address.
- Save the endpoint again.
The test does not arrive
The page in Konektor shows "The test has not arrived" after 5 minutes.
- Make sure your Scalev plan is Basic or higher.
- Make sure the endpoint is Active and that you clicked Save Endpoint.
- Compare the address in Scalev with the address in Konektor.
- In Konektor, click Check again.
No orders arrive
- Make sure the store is Active or Waiting for orders, not Paused. Click Resume if needed.
- In Scalev, make sure the endpoint is Active, its address is the same as the Konektor address, and the order events are ticked.
- If you created a new address, change the address of the endpoint in Scalev.
- Make sure you saved the Signing Secret. Without it, Konektor accepts only the test message.
- Konektor skips events that it does not use, such as WhatsApp messages and subscriptions. They do not show in Recent events.
Orders arrive, but there is no lead
- Check the Create leads from orders setting. If it is off, an order from a new number does not create a lead.
- The daily lead limit of the workspace can be full. Konektor still saves the order, but order flows do not run for an order without a lead.
- Konektor cannot match an order without a valid WhatsApp number to a lead.
Messages are not sent
See Order flows. An official number needs a template for messages outside 24 hours. The Store orders section of the lead shows why a step did not send.
Spam orders
Konektor ignores orders that Scalev marks as spam.
Pause and delete a store
- Pause: click Pause on the store card. Konektor stops accepting orders from Scalev for that store. Flows that run for that store stop too. Your settings and old data stay. Click Resume to continue.
- Delete: click Delete, then Delete store. Konektor stops accepting orders from that store, and flows that run for that store stop. Also remove the endpoint in Scalev.
One workspace can have up to 5 stores from all platforms.
Next steps
Need More Help?
Our team is ready to help you maximize ad tracking and business attribution.
Wulan answers your questions and sends tutorial videos. Session scheduling is available through Wulan if you still need it.
© 2026 Konektor. All rights reserved.
