i-Reserve Salla

When updated customer in i-Reserve, sync it to Salla.

When customer details change in i-Reserve, update the customer record in Salla.

Try:

See all i-Reserve + Salla integrations or talk to a human

Trusted by teams already building on Knit·4.9 out of 5 stars4.9/5 on G2·GoogleGoogle for Startups Accelerator
prismforceHackerearthIsotopes AIInfojobsPayoneerOutsolveSkuadPayworksItiliteOnsurityRazorpayXMultiplierPeoplestrongScrutCeipal

How Knit builds this workflow

The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.

i-Reserve Explore i-Reserve →

Triggers
New booking made

Fires when a new booking or appointment is made in i-Reserve.

Booking rescheduled or canceled

Fires when a booking in i-Reserve is changed or canceled.

New customer

Fires when a new customer books for the first time in i-Reserve.

Actions
Create a booking

Creates a new booking or appointment in i-Reserve.

Cancel or reschedule a booking

Cancels or moves a booking in i-Reserve.

Create or update a customer

Creates or updates a customer record in i-Reserve.

Add the booking to a calendar

Adds a booking from i-Reserve to a connected calendar.

Salla Explore Salla →

Triggers
New order

Fires when a customer places a new order in Salla.

Order status changed

Fires when an order in Salla is paid, fulfilled, refunded or disputed.

New customer

Fires when a new customer account is created in Salla.

Cart abandoned

Fires when a customer abandons their cart before completing checkout in Salla.

Actions
Create or update product

Creates or updates a product or listing in Salla.

Update order

Updates an order's status or fulfillment details in Salla.

Make a custom API request

Sends a custom API request to Salla for actions not covered by a dedicated action.

Sync new booking customers with store records When a new customer or booking is created in i-Reserve, send a custom API request to Salla to establish their buyer profile. See details
Prepare booking slots for abandoned shopping carts When a cart is abandoned in Salla, automatically create or update a customer profile in i-Reserve so support can schedule a sales consultation. See details
Process affiliate attribution upon booking cancellation When a booking is rescheduled or canceled in i-Reserve, make a custom API request to Salla to adjust partner commission records. See details

See all i-Reserve + Salla integrations →  ·  Browse the full workflow library →

Enterprise-grade security

SOC 2 certified GDPR compliant ISO 27001 certified
Visit our Security Center Review the DPA
FAQ

Common questions

Can Knit build “When updated customer in i-Reserve, sync it to Salla.” between i-Reserve and Salla?

Yes — describe it in the box above and Knit's Integrations Agent researches i-Reserve and Salla's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.

How long does it take to build?

Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.

How do new booking clients get added as store contacts?

When a new booking or customer is recorded in i-Reserve, you can make a custom API request to Salla to store their commerce account profile.

Can abandoned carts trigger follow-up booking consultations?

Yes, when a customer abandons a cart in Salla, you can automatically create or update a customer record or prepare a booking link in i-Reserve.

Put Integrations on Autopilot. Talk to Experts.

Knit is loved by customers across the globe due to our seamless product and white glove support. You'll love us too!

Talk to a Human