Lynk.id Integration
Connect your Lynk.id store to Konektor. Konektor saves each successful Lynk.id payment and links it 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 to Purchase.
- Run closing flows: thank-you messages from your WhatsApp number.
- Send one Purchase event for each order to your ad platforms (optional, off by default).
Lynk.id sends only successful payments. So each order from Lynk.id reaches Konektor already paid.
Who this is for
Use this integration if you sell on Lynk.id and close sales on WhatsApp. It works on all Lynk.id plans. You do not change your Lynk.id product pages.
Prerequisites
- A Lynk.id account.
- 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 Lynk.id
The setup has three steps. Open two tabs: Konektor and Lynk.id.
Lynk.id keeps one webhook address
Lynk.id keeps one webhook address for each account. If another tool uses that address, that tool stops getting data from Lynk.id after you paste the Konektor address. First check if another tool uses your Lynk.id webhook.
Step 1: Create the webhook address in Konektor
- Open Settings > Store & orders.
- Click Connect a store, then choose Lynk.id.
- Enter a Store name, then click Create address.
- Click Copy to copy the webhook address.
Step 2: Add the address in Lynk.id
- In Lynk.id, open Settings > Integrations > Webhook.
- Paste the address from Konektor in the URL Webhook field, then click Save URL. After you save, Lynk.id shows the Merchant Key on the same page. You need it in step 3.
- If Lynk.id shows a choice of event types, choose successful payment.
- Go back to Konektor, then click I pasted it.
- In Lynk.id, click Test URL.
- Konektor waits up to 5 minutes for the test. When the test arrives, the page shows "The test from Lynk.id arrived." and goes to step 3.
If the test does not arrive in 5 minutes, make sure Lynk.id saved the address. Then click Check again.
Step 3: Paste the Merchant Key
- In Lynk.id, copy the Merchant Key. Lynk.id shows it on the Webhook page after you save the address.
- In Konektor, paste the key in the Merchant Key field, then click Save.
- In Lynk.id, click Test URL once more.
- In Konektor, click Done.
- Look at the store card. Reload the page if needed. If the card does not show Needs a check, the key is right.
Without the Merchant Key, Konektor does not process orders from Lynk.id. Konektor shows only the last 4 characters of the saved key.
Keep the address and Merchant Key private
Do not share your webhook address or your Merchant Key. If the address leaks, click Create new address on the store card. The old address stops at once. Then paste the new address in Lynk.id.
What happens when the buyer pays
- Lynk.id sends the payment data to Konektor.
- Konektor saves the order as Paid and links it to the lead with the same WhatsApp number. If the lead does not exist, Konektor creates it.
- Konektor changes the lead status to Purchase.
- Flows with the trigger Payment is received run.
- If Send Purchase to ad platforms is on, Konektor sends one Purchase.
The store settings decide if Konektor creates leads, changes the lead status, and sends Purchase. See The three store settings.
Konektor takes the buyer name, the WhatsApp number, the email, the product, and the total from the Lynk.id data. Konektor does not process refunds. If you refund a payment in Lynk.id, the order in Konektor stays paid.
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 to Purchase when the payment arrives. |
| Send Purchase to ad platforms | Off | Sends one Purchase for each order. |
Turn on Purchase only when needed
If you install a Meta pixel in Lynk.id, Lynk.id can also send Purchase to that pixel. If both systems send to the same pixel, Meta can count one sale two times. Turn this setting on only when Lynk.id does not send Purchase to the same pixel.
The Purchase value equals the total that the buyer pays. If Lynk.id does not send that total, Konektor uses the amount that you receive after the Lynk.id fees. Konektor sends one Purchase for one order, and only for an order that has a lead. Lynk.id does not send ad click data. The Purchase uses the ad data that the lead already has.
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.
Closing flows for Lynk.id orders
A closing flow sends WhatsApp messages, changes the lead status, adds tags, and writes notes when something happens to an order.
- Open Conversations > Automation Rules, then choose the Orders tab.
- Click Create flow, or pick the example Thank you after payment in Start from an example.
- Set the message and the sender WhatsApp number, then click Save flow.
Only the Owner and Admins can create flows. One workspace can have up to 20 flows. The Closing flows list shows all your flows. For all options, see Order flows.
Lynk.id sends one trigger only: Payment is received. Other triggers, such as A new order is created and A checkout is abandoned, never run for Lynk.id stores. If you choose one of them, the flow editor shows a warning.
The example Thank you after payment fits Lynk.id. Konektor sends a thank-you message and adds the tag buyer. The other examples do not fit Lynk.id.
Message keywords
Write a keyword with two curly brackets. Konektor fills it from the order.
| Keyword | Value | If empty |
|---|---|---|
{{name}} | First name of the buyer | Replaced by Kak |
{{order_id}} | Order reference number from Lynk.id | The action is skipped |
{{total}} | The total, for example Rp72.000 | The action is skipped |
{{product}} | First product, plus the number of other products | The action is skipped |
{{payment_link}} | None. The order is already paid when it arrives | The action is skipped |
{{payment_method}} | Lynk.id does not send the payment method | Empty |
{{store}} | Store name in Konektor | Empty |
Do not use {{payment_link}} for Lynk.id orders. A Lynk.id order has no payment link, because it is already paid. The Lynk.id reference number can be long. If you do not want to show it, remove {{order_id}} from the example message. Konektor refuses a message that uses another keyword.
Stop rule and quiet hours
A flow stops by itself when the buyer replies. This rule is on by default. A step with a delay waits until quiet hours end. The default is 21:00 to 08:00 in the workspace time zone. A step with no delay does not wait.
Choose the sender WhatsApp number in the Send WhatsApp action. That number must be active in the Konektor Inbox.
An official number needs a template
An official WhatsApp number can send free text only within 24 hours after the buyer last replied. Outside that time, choose an approved template in the send action. Without a template, Konektor skips the action. See WhatsApp Templates.
Check that it works
- Create a test order in Lynk.id with a cheap product and your own WhatsApp number, then pay it.
- 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 |
|---|---|
| Merchant Key needed | The address is set, but you did not save the Merchant Key. |
| Waiting for orders | The store is ready, but no order arrived from Lynk.id yet. |
| Active | Orders arrive and Konektor processes them. The card shows the time of the last order. |
| Paused | Konektor does not accept orders from Lynk.id. |
| Needs a check | There is a problem. The card shows the message, for example "The data from Lynk.id 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 Lynk.id was rejected
The Merchant Key in Konektor is different from the one in Lynk.id. The store card shows Needs a check and the message "The data from Lynk.id was rejected. Copy the Merchant Key from Lynk.id again."
- In Lynk.id, copy the Merchant Key again from the Webhook page.
- In Konektor, open the store card, then click Settings.
- Paste the key in the Merchant Key field, then click Save.
- In Lynk.id, click Test URL. Reload the page if needed. If the message on the card goes away, the key is right.
The Merchant Key is not saved
The store card shows Merchant Key needed and the text "Copy the Merchant Key from Lynk.id to finish the setup." Lynk.id already sent data, but you did not save the Merchant Key. Without the key, Konektor does not process orders.
Open Settings on the store card, paste the Merchant Key, then click Save.
No orders arrive
- Make sure the store is Active or Waiting for orders, not Paused. Click Resume if needed.
- Make sure you saved the Merchant Key. Without it, Konektor does not process orders.
- In Lynk.id, open Settings > Integrations > Webhook. Make sure the address is the same as the Konektor address. Click Show address to see it.
- Lynk.id keeps only one webhook address for each account. If another tool replaced that address, paste the Konektor address again, then click Save URL.
- If you created a new address, paste that new address in Lynk.id, then click Save URL.
- In Lynk.id, open the Webhook History page. It shows the status of each delivery that Lynk.id sent.
- Remember: Lynk.id sends only successful payments. Lynk.id does not send unpaid checkouts.
- Konektor skips payment data that arrives more than 3 days after Lynk.id sent it. The event shows Skipped with the reason "This data from Lynk.id is old."
The data from Lynk.id could not be read
The store card shows this message when the payment data is not complete or the format is not known. If the message keeps coming, open Help > My tickets. Include the store name and the time of the event. Do not attach the Merchant Key or the webhook address.
An order arrives, 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 closing 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
- Make sure the flow is on and the store is Active.
- Make sure the sender WhatsApp number is active in the Inbox.
- For an official number, choose a template if the buyer did not reply in the last 24 hours.
- Look at the result in the Store orders section of the lead. For example: "The order has no payment link." means the message uses
{{payment_link}}. Remove that keyword from the message.
Pause and delete a store
- Pause: click Pause on the store card. Konektor stops accepting orders from Lynk.id for that store. Flows that run for that store stop too. Your settings and old data stay. Konektor does not process orders that Lynk.id sends while the store is paused. 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. After that, remove the webhook address in Lynk.id.
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.
