Are my products synced between Salla and my platform?

No. You pick the product on your platform in the enrolment step, and filter by the Salla product in the event's condition when you want different behaviour per product.

What happens when an order is refunded in Salla?

Whatever you built. Connect the refund event to a remove-enrolment step for access to be withdrawn, because it is not withdrawn on its own.

Is a welcome email sent to the buyer?

Only if you add an email step. The connection creates the trainee and writes to them nothing by itself.

Is a developer needed?

No. The connection uses keys from your Salla Partners dashboard, and the automation is built in a visual editor inside your own dashboard.

Can more than one event be connected?

Yes. Each event can have one automation or several, and each automation has its own conditions and steps.

Integrations Salla (سلة)

Connecting Salla to your platform

Salla is a store platform. Once connected, an event in your Salla store reaches your platform, and you decide what follows it: enrolling the buyer in a course, adding them to a segment, or sending them an email.

The connection runs on automations you build. You pick the Salla event, the condition that filters it, and the steps that run after it.

From the Growth plan

Free trial Plans and pricing

Salla (سلة) on your platform

The buyer becomes a trainee
An order from Salla creates the buyer as a trainee on your platform by email, and the steps of your automation then run on them.
More than orders
An order, a payment, an order status, an abandoned cart, a new customer, a coupon and a review can each start an automation.
A condition before anything runs
Filter the event by the Salla product, the order total, its status or its payment method, so the steps run only on the orders you meant.

With the rest of your platform

Steps you choose
Enrol in a product, remove that enrolment, add to a segment, send an email, wait, generate a coupon, call a webhook, or branch on a condition.
Every message is verified
Each message from Salla has its signature checked before a single step runs, and one that does not carry a valid signature is refused.
A record of every run
Each delivery and each run keeps its own status, and a step that fails does not stop the ones after it.

Before you switch it on

The connection only receives. Your platform reads from Salla and sends nothing back, so products and orders are not synced the other way.
A buyer is matched by email alone, and an event that carries no email runs without a trainee, so the enrolment and segment steps are skipped.
Withdrawing access on a refund is an automation you build, by connecting the Salla refund event to a remove-enrolment step.

The connection steps are in the help centre

Salla is connected from the Apps page of your dashboard, with the keys from your Salla Partners app, and the webhook address your platform shows is registered in Salla. The help centre covers the steps.

Open the help centre

Common questions

Are my products synced between Salla and my platform?: No. You pick the product on your platform in the enrolment step, and filter by the Salla product in the event's condition when you want different behaviour per product.
What happens when an order is refunded in Salla?: Whatever you built. Connect the refund event to a remove-enrolment step for access to be withdrawn, because it is not withdrawn on its own.
Is a welcome email sent to the buyer?: Only if you add an email step. The connection creates the trainee and writes to them nothing by itself.
Is a developer needed?: No. The connection uses keys from your Salla Partners dashboard, and the automation is built in a visual editor inside your own dashboard.
Can more than one event be connected?: Yes. Each event can have one automation or several, and each automation has its own conditions and steps.