Salla Make integrationAutomate Salla with Make.
Can your Salla store handle its routine work on its own? The Salla Make integration gives you 47 modules, including 28 instant triggers for orders, carts and customers. This page walks store owners through the connection and a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Salla Make integration let you automate?
The Salla Make integration links your Salla store to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, creates, updates or searches something. Salla events like a new order start the scenario, and Make carries the data to your other apps.
Win back abandoned carts. Watch Abandoned Cart hands Make every checkout left unpaid. Add Search Customers, then your email tool, and each lost cart gets a reminder without anyone exporting lists.
Publish a catalog from a spreadsheet. Your team prepares items in a sheet. Create a Product turns each row into a product, and Attach Image To Product adds its picture. Every row is one bundle, the item that flows from one module to the next.
Hear about every review. Watch Review Added posts each new review where your care team works, so no unhappy buyer waits for an answer.
What the list does not include: no module creates or edits an order, and every trigger is instant, which means Salla calls Make by webhook (a web address Make listens on) instead of Make checking on a timer. For anything missing, Make an API Call reaches the Salla API. Check what each run costs on the Make pricing page, and if you are also looking at n8n, the n8n vs Make comparison lays out the differences. Stuck on a broken run? Make troubleshooting covers the usual errors.
How do you connect your Salla store to Make?
- 01
Prepare your Salla Partners app
Make needs a verified Salla Partners developer account and an active app linked to your store. In the Partners dashboard, open Apps, pick your app and copy the Client ID and Client secret shown there.
- 02
Add a Salla module in Make
In your scenario, add any Salla module and click Create a connection. A connection is your store linked to Make once, then reused by every Salla module. Give it a clear name in Connection name if you manage several stores.
- 03
Paste the credentials and authorize
Enter the Client ID and Client secret you copied, or follow the instructions on screen. If Salla asks for a callback URI, use
https://www.integromat.com/oauth/cb/salla2. Save, and the connection appears in the module.
Your first scenario: put stock back when an order is cancelled
GoalWhen an order is cancelled in Salla, Make finds the products and puts their quantity back in stock.
- 01
Create the scenario
On the Scenarios page, create a new scenario and click the big +. Search for Salla and pick Watch Order Cancelled.
- 02
Set up the trigger
Click Create a webhook, then Create a connection with your Salla Partners credentials. From now on, each cancelled order is sent to this scenario.
- 03
Find the products
Click the + on the right and add Search Products. Map the product reference the order bundle carries (check it with Run once first), so Make finds the matching product in your catalog.
- 04
Put the quantity back
Add Update Product Quantity and map the product found in the previous step. Set the new quantity from the data Make shows you in the earlier modules.
- 05
Test with Run once
Click Run once, then cancel a test order in Salla. Open each module's bubble to read the bundles it received and check the stock in your store.
- 06
Switch it on
Save and switch the scenario on. Since the trigger is instant, it runs each time Salla reports a cancellation, with no timer to set.
Which Salla events can start a scenario?
28 modules start a scenario when something happens in Salla. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Salla as soon as it happens.
Custom Webhook
Instant triggerIn Make“Webhooks simplify the way apps communicate with each other, as you get to be notified whenever your app receives payload/data from another app.”
Make gives you a webhook address of your own, and whatever data reaches it starts your scenario. Think of it as the generic entry point, next to the named Watch modules listed below.
Watch Abandoned Cart
Instant triggerIn Make“Triggers when there is an abandoned cart.”
A shopper fills a cart and leaves without paying: this trigger hands you that cart as soon as Salla flags it. It is the starting point for any recovery flow, from a reminder email to a note in your CRM.
Watch Brand Created
Instant triggerIn Make“Triggers when a brand was created.”
Every time someone on your team adds a brand in the Salla dashboard, Make receives it and your scenario can react. Handy when brands live in more than one place, like a supplier sheet or a marketing calendar.
Watch Brand Deleted
Instant triggerIn Make“Triggers when a brand is deleted.”
When a brand disappears from your store, this trigger lets the rest of your tools know. It keeps side lists honest: the brand stops showing up in reports, sheets or supplier trackers that still reference it.
Watch Brand Updated
Instant triggerIn Make“Triggers when a brand was updated.”
A brand gets renamed or its details change in Salla, and this trigger passes the new version to your scenario. You stop copying edits by hand into the tools that mirror your catalog.
Watch Category Created
Instant triggerIn Make“Triggers when a category is created.”
New category in the store, new run of your scenario. The trigger gives you the category the moment it exists, so the tools around your shop can prepare for the products that will land in it.
Watch Category Updated
Instant triggerIn Make“Triggers when a category is updated.”
Whenever a category changes in Salla, this trigger sends its fresh version to Make. It keeps navigation labels, feeds and internal docs aligned with what shoppers actually see.
Watch Coupon Applied
Instant triggerIn Make“Triggers when a coupon is applied.”
A customer types a coupon at checkout and your scenario hears about it right away. That gives you a live view of which codes work, instead of waiting for a report at the end of a campaign.
Watch Customer Created
Instant triggerIn Make“Triggers when a customer is created.”
Each new customer account in your Salla store becomes a bundle in Make, ready to be copied wherever you follow your clients. It is the cleanest way to feed a CRM or a welcome sequence.
Watch Customer Login
Instant triggerIn Make“Triggers when a customer login.”
This trigger tells Make each time a customer signs in to your store. It turns a quiet signal into something you can act on, such as spotting returning buyers or keeping a simple activity log.
Watch Customer Otp Request
Instant triggerIn Make“Triggers when a customer request an Otp.”
An OTP is the one-time code a customer asks for to sign in. This trigger reports every such request to Make, which gives you a trace of sign-in attempts outside the Salla dashboard.
Watch Customer Updated
Instant triggerIn Make“Triggers when a customer is updated.”
When a customer edits a profile or your team changes it in Salla, the new version lands in your scenario. Your CRM stops drifting away from the store.
Watch Order Cancelled
Instant triggerIn Make“Triggers when an order is cancelled.”
An order is cancelled and this trigger tells Make on the spot. You can undo the side effects of that order in other tools: a shipping label request, a stock reservation, a sales task.
Watch Order Coupon Updated
Instant triggerIn Make“Triggers when an order coupon is updated.”
This trigger follows the coupon attached to an existing order. If a code is added, swapped or removed after the order is placed, your scenario gets the new state.
Watch Order Created
Instant triggerIn Make“Triggers when an order coupon is created.”
The most common start for a Salla scenario: a new order arrives and Make receives it. From there you can notify the team, prepare shipping in another tool or update a sales dashboard.
Watch Order Customer Updated
Instant triggerIn Make“Triggers when an order customer is updated.”
Sometimes the buyer details on an order change after it is placed. This trigger passes that change to Make so the order in your other tools shows the right person.
Watch Order Deleted
Instant triggerIn Make“Triggers when an order is deleted.”
When an order is removed from the store, this trigger warns your scenario so the order does not live on in other tools. It keeps your reports free of orders that no longer exist.
Watch Order Payment Updated
Instant triggerIn Make“Triggers when an order payment is updated.”
Money is the moment that matters. This trigger fires when the payment side of an order changes, so you can wait for it before starting anything costly like shipping.
Watch Order Products Updated
Instant triggerIn Make“Triggers when an order products is updated.”
If items are added to or removed from an existing order, this trigger sends the new content to Make. The picking list in your other tools stays in line with what the customer will receive.
Watch Order Refunded
Instant triggerIn Make“Triggers when an order is refunded.”
A refund goes through and your scenario hears about it straight away. It is the hook for everything that follows a refund: an accounting entry, a note in the CRM, a restock.
Watch Order Updated
Instant triggerIn Make“Triggers when an order is updated.”
This one is the wide net for orders: any change on an order starts your scenario. Use it when you want a single place to follow order life, not one scenario per event.
Watch Product Available
Instant triggerIn Make“Triggers when a product is available.”
A product comes back to being available, and Make is told at once. It is the natural start for back-in-stock alerts, both for customers and for your own team.
Watch Product Created
Instant triggerIn Make“Triggers when a product is created.”
Each new product in your Salla catalog reaches Make the moment it is saved. Your other channels, sheets and teams can then pick it up without a manual export.
Watch Product Deleted
Instant triggerIn Make“Triggers when a product is deleted.”
When a product leaves the catalog, this trigger tells the rest of your tools. A sheet, a feed or an ads tool can stop pointing to an item shoppers can no longer buy.
Watch Review Added
Instant triggerIn Make“Triggers when a review is added.”
A new customer review appears on your store and Make gets it right away. You can answer faster and keep a record of what buyers say, product by product.
Watch Special Offer Created
Instant triggerIn Make“Triggers when a special offer is created.”
Special offers are the promotions you set up in Salla. This trigger passes each new one to Make so the people who talk about your store know it exists.
Watch Special Offer Updated
Instant triggerIn Make“Triggers when a special offer is updated.”
When an existing special offer is edited, this trigger sends the new version to Make. Promotions announced elsewhere keep matching what the store really applies.
Watch Store Tax Created
Instant triggerIn Make“Triggers when a storetax is created.”
This trigger fires when a new tax is set up in your Salla store. It is a quiet but useful signal for whoever handles bookkeeping outside Salla.
What can Make do in your Salla store?
Salla gives you 19 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Attach Image To Product
ActionIn Make“Attaches an Image to a product.”
Gives a product its picture without opening the Salla dashboard. The image comes from an earlier module of the scenario, like a file from your storage app, and ends up on the product page.
Create a Brand
ActionIn Make“Creates a new brand.”
Adds a new brand to your store from Make. Useful when brand names start in another tool, such as a supplier list, and you are tired of typing them twice.
Create a Brand (v2)
ActionIn Make“Create-brand-v2”
A second version of the brand creation module, listed next to the first one in Make. It also creates a brand in your Salla store, from data coming from earlier modules.
Create a Category
ActionIn Make“Creates a new category.”
Opens a new section in your Salla catalog straight from a scenario. Categories can then follow the plan written in your planning tool instead of being rebuilt by hand.
Create a Product
ActionIn Make“Creates a new product.”
Turns data from another app into a real product in your store. It is the heart of any catalog import built with Make, one bundle becoming one product.
Delete a Brand
ActionIn Make“Deletes a brand.”
Removes a brand from your Salla store through a scenario. It keeps the store in step with a master list maintained elsewhere, where brands get retired.
Delete a Category
ActionIn Make“Deletes a category.”
Takes a category out of your catalog automatically. Handy for seasonal sections that you open and close from a planning tool.
Delete a Product
ActionIn Make“Deletes a product.”
Removes a product from the store from inside a scenario. It is the cleanup step for items discontinued in your supplier or inventory tool.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
The escape hatch: it calls any endpoint of the Salla API with the connection you already set up. Anything the listed modules do not cover can still be reached.
Update a Brand
ActionIn Make“Updates a brand.”
Edits a brand that already exists in your store. You keep brand details in one reference tool and let Make push the changes into Salla.
Update a Category
ActionIn Make“Updates a category.”
Changes an existing category from a scenario, so labels shown to shoppers follow the plan your team writes elsewhere.
Update Product
ActionIn Make“Updates a product.”
Edits a product that is already in your catalog. It is how a scenario keeps product pages in step with the source where your team writes content.
Update Product Quantity
ActionIn Make“Updates a product quantity.”
Sets the stock of a product in Salla from a scenario. Your store shows the quantity that your warehouse or inventory tool actually holds.
Your Custom Action
ActionIn Make“A custom action made for you.”
Make lists this module as a custom action made for the Salla app. The documentation says nothing more about what it does, which fields it asks for or what it returns.
Search Brands
SearchIn Make“Searches for brands.”
Finds brands in your store and passes them on to the next modules. It is the lookup step before you update or delete a brand you only know by name.
Search Categories
SearchIn Make“Searches for categories.”
Looks up categories in your Salla catalog. Your scenario gets the category it must work on, instead of guessing.
Search Customers
SearchIn Make“Searches for customers.”
Pulls customer records from your store into the scenario. It adds context to an event, such as a cart or an order, when the trigger bundle is not enough.
Search Products
SearchIn Make“Searches for products.”
Finds products in your catalog and hands them to the next step. It is the bridge between a name or reference in another tool and the product in Salla.
Update Bulk Quantities (Beta)
ActionIn the docs onlyA beta module with no official description. Its name points to updating the stock of several products in one go, which the brief cannot confirm.
Need help automating Salla with Make?
A person reads every message.
