Special workflows for Limo Anywhere.
Each scenario shows the trigger, the Volimox handoff, and the human checkpoint. These are concrete workflow blueprints, not a claim that every connection is live today.
New reservation to dispatch brief
Bring a Limo Anywhere reservation into Volimox with the context needed for a clean handoff.
Starts when
Limo Anywhere reports a new reservation or quote request.
Result
A reservation becomes one visible workflow with passenger and dispatch context.
Volimox workflow
- 01Volimox reads the passenger, pickup, timing, vehicle, and trip details.
- 02Volimox creates a dispatch brief and links the reservation reference.
- 03The operator reviews the request and confirms the next customer or dispatch action.
Human checkpoint
Reservation status and required trip fields are checked before a customer promise.
Dispatch status to passenger update
Send a controlled passenger update when the ride status changes.
Starts when
Limo Anywhere reports a reservation update or dispatch status change.
Result
Passengers receive timely information without losing dispatch accountability.
Volimox workflow
- 01Volimox reconciles the event to the existing reservation and lead.
- 02Volimox prepares the approved SMS or email using the verified trip fields.
- 03The operator approves the update and the event is recorded in the timeline.
Human checkpoint
Stale events and unmatched passengers pause for review.
Supported triggers and actions.
A trigger starts the workflow. An action is the controlled operation Volimox performs after the rules pass.
Triggers
- Reservation created
- Reservation updated
- Dispatch status changed
Actions
- Create reservation
- Update reservation
- Find customer
- Add note
Detailed connection code.
This server-side TypeScript reference follows the same connection → action → mapped input pattern used by modern automation platforms. Provider credentials remain inside the approved connection; browser code never receives them.
TypeScript · server only
Create a reservation through the customer API
import { createZapierSdk } from "@zapier/zapier-sdk"
const zapier = createZapierSdk({
apiKey: process.env.ZAPIER_API_KEY,
})
export async function runLimoAnywhereAction() {
const { data: connection } = await zapier.findFirstConnection({
app: "webhooks-by-zapier",
owner: "me",
})
if (!connection) {
throw new Error("No approved Limo Anywhere connection was found")
}
const result = await zapier.runAction({
app: "webhooks-by-zapier",
action: "custom_request",
connection: connection.id,
input:
{
"method": "POST",
"url": "{{env.LIMO_ANYWHERE_API_BASE}}/reservations",
"headers": "Authorization=Bearer {{secret.LIMO_ANYWHERE_API_KEY}}",
"body": "{{lead.limoAnywhereReservationJson}}"
},
})
return result.data
}Connection setup.
The setup path is specific to the provider. We will never ask you to paste credentials into a public page.
Customer API credentials
A reviewable connection, step by step.
- 01Existing Limo Anywhere customer account
- 02API license and credentials
- 03Map vehicle and service types
This app is cataloged and its workflow contract is defined. We will enable the connection after provider access and sandbox verification.
Related apps