Linx Commerce Make integrationAutomate Linx Commerce with Make.
Can your store's customer list feed the rest of your tools on its own? The Linx Commerce Make integration offers 8 modules: 1 scheduled trigger, 6 actions and 1 search. This page walks an ecommerce team through the connection and a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Linx Commerce Make integration do?
The Linx Commerce Make integration links your Linx Commerce account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger, an action or a search. You pick the bricks, Make runs them in order, and customer or catalog data moves without copy and paste.
Customer sync to a CRM or a sheet. Watch Customers picks up customers on the scenario's schedule, and each one travels to the next module as a bundle, meaning one item passed along the chain. From there you can drop the customer into a spreadsheet, a mailing tool or a CRM of your choice.
Product lookups for a support or sales flow. When another app hands you a product reference, Get a Product or Get a SKU pulls the matching record from Linx Commerce so the rest of the scenario can use it, for example in a reply to a customer or a stock check.
One clean customer record, whatever the source. Upsert a Customer creates the customer if it does not exist and updates it if it does, which keeps a form or a marketplace from filling the store with duplicates. Search Customers helps you check first when you need to branch.
Know the limits before you build. Make's own documentation for Linx Commerce is flagged as limited, because little public information about the app exists, so the exact fields of each module are best discovered in the editor with a test run. The Make troubleshooting guide helps when a module returns something unexpected.
The same app often has an n8n node too. If you are weighing both tools, read n8n vs Make, and check Make pricing before you plan several active scenarios.
How do you connect Linx Commerce to Make?
- 01
Add a Linx Commerce module
In a scenario, add any Linx Commerce module, then click Create a connection. A connection is your Linx Commerce account linked to Make once, and every module of the app reuses it afterwards.
- 02
Name it and authorize Make
Give the connection a name if you like, such as the store it belongs to. Then either approve Make on the Linx Commerce page that opens, or paste the key Linx Commerce gives you, depending on what the connection window asks for.
- 03
Save and check the fields
Click Save. Back in the module, Make can now read your account and offers what it finds, so fill the fields from those lists rather than typing values by hand.
Your first scenario with Linx Commerce
GoalWhen your signup form receives a new contact, Make creates or updates the matching customer in Linx Commerce.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the big + to place the first module. Pick the trigger of your form tool here: it decides when the whole scenario starts.
- 02
Add Upsert a Customer
Click the + on the right of the form module, search for Linx Commerce and pick Upsert a Customer. Click Create a connection if you have none yet.
- 03
Map the form answers
Fill the module fields with the answers coming from the form module. Map only what the visitor typed reliably, since an update replaces what the store already holds.
- 04
Test with Run once
Send yourself a test entry, then click Run once. Make shows the bundles each module received, which is the best way to learn the real fields here.
- 05
Schedule and switch on
Open the clock on the first module and set the schedule; a new scenario runs every 15 minutes by default. Then switch the scenario on so it keeps working without you.
What starts a Linx Commerce scenario
1 module starts a scenario when something happens in Linx Commerce. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Linx Commerce as soon as it happens.
Watch Customers
triggerIn the docs onlyWatch Customers gives you a steady feed of customers from Linx Commerce, each arriving as its own bundle, so the rest of the scenario can act on them one by one. It works as a scheduled trigger; that type is inferred from its name, since the documentation adds nothing more.
What the Linx Commerce modules can do
Linx Commerce gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Get a Customer
ActionIn the docs onlyGet a Customer brings back one customer record you already know how to point to, so a later module can reuse its details. It is the right pick when a single known customer matters, not a list.
Get a Product
ActionIn the docs onlyGet a Product fetches one product from your Linx Commerce catalog, handing its data to the next module so it can quote, compare or display it. Reach for it when the flow already carries a product reference.
Get a SKU
ActionIn the docs onlyGet a SKU reads a single SKU, the stock-keeping unit that names one exact variant of a product, and passes it along. It is narrower than Get a Product and fits flows built around one precise item.
Make a Search
ActionIn the docs onlyMake a Search lets you run a query against Linx Commerce when no dedicated module matches what you are looking for. Its type (action) is inferred from its name and the documentation says nothing about its options, so treat it as a flexible lookup to explore.
Make an API Call
ActionIn the docs onlyMake an API Call opens the rest of the Linx Commerce API to your scenario, reusing the connection you already created, so you are not blocked by the short list of modules. Any endpoint of the app's API can be called from here.
Search Customers
SearchIn the docs onlySearch Customers tells you whether matching customers exist and returns each one as a separate bundle, from zero up to several. That makes it the module to place before a decision in your flow.
Upsert a Customer
ActionIn the docs onlyUpsert a Customer saves you from checking first: it creates the customer when none exists and updates the existing one otherwise. You end up with one record per person instead of duplicates.
Need help automating Linx Commerce with Make?
A person reads every message.
