Mark cancellations
When a booking is cancelled in Limo Anywhere, update the row in Grid.
See all Limo Anywhere + Grid integrations or talk to a human
Google for Startups AcceleratorHow 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.
Limo Anywhere Explore Limo Anywhere →
TriggersFires when a new booking or appointment is made in Limo Anywhere.
Fires when a booking in Limo Anywhere is changed or canceled.
Fires when a new customer books for the first time in Limo Anywhere.
Creates a new booking or appointment in Limo Anywhere.
Cancels or moves a booking in Limo Anywhere.
Creates or updates a customer record in Limo Anywhere.
Adds a booking from Limo Anywhere to a connected calendar.
Grid Explore Grid →
TriggersFires when a row is added to a sheet in Grid.
Fires when a row or column changes in Grid.
Fires when a new spreadsheet or worksheet is created in Grid.
Adds a new row to a sheet in Grid.
Updates the values in an existing row in Grid.
Finds a row by a column value in Grid.
More Limo Anywhere + Grid workflows
See all Limo Anywhere + Grid integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Mark cancellations” between Limo Anywhere and Grid?
Yes — describe it in the box above and Knit's Integrations Agent researches Limo Anywhere and Grid'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.
Can bookings be logged?
Yes. Each new booking in Limo Anywhere can be added as a row in Grid.
Do cancellations update the sheet?
When a booking is cancelled or rescheduled in Limo Anywhere, the row in Grid can be updated.