When cancelled user booking in Skedda, sync it to Seam.
When a user booking is cancelled in Skedda, revoke smart lock access via Seam.
4.9/5 on G2·
Google for Startups Accelerator
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.
Skedda Explore Skedda →
TriggersFires when a new booking or appointment is made in Skedda.
Fires when a booking in Skedda is changed or canceled.
Fires when a new customer books for the first time in Skedda.
Creates a new booking or appointment in Skedda.
Cancels or moves a booking in Skedda.
Creates or updates a customer record in Skedda.
Adds a booking from Skedda to a connected calendar.
Seam Explore Seam →
TriggersFires when a lock managed by Seam is unlocked.
Fires when Seam grants someone access to a space.
Fires when a visitor or guest checks in via Seam.
Creates a new access code or key via Seam.
Revokes a guest's or employee's access in Seam.
Registers a visitor or guest in Seam.
Common questions
Can Knit build “When cancelled user booking in Skedda, sync it to Seam.” between Skedda and Seam?
Yes — describe it in the box above and Knit's Integrations Agent researches Skedda and Seam'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.