Special workflows for Moovs.
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.
Quote request to Moovs reservation
Pass a complete ground-transportation request into a reviewable Moovs reservation flow.
Starts when
Moovs or Volimox reports a new reservation request with the required trip fields.
Result
The reservation team receives a complete request rather than a partial message.
Volimox workflow
- 01Volimox normalizes passenger, pickup, timing, vehicle, and contact details.
- 02Volimox creates or updates the reservation with the original request attached.
- 03The operator reviews availability and confirms the quote or reservation path.
Human checkpoint
Vehicle, timing, and passenger details are reviewed before the reservation is treated as ready.
Trip status to passenger update
Keep the passenger informed when a Moovs trip changes state.
Starts when
A linked Moovs reservation or trip status changes.
Result
Passenger communication follows the actual trip state and not an outdated assumption.
Volimox workflow
- 01Volimox matches the event to the passenger and reservation reference.
- 02Volimox prepares the approved status update and records the new state.
- 03The operator confirms the message or escalates an exception to dispatch.
Human checkpoint
Unmatched or conflicting trip events are held for dispatch 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
- Trip status changed
Actions
- Create reservation
- Update trip
- Find passenger
- 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 Moovs reservation request
import { createZapierSdk } from "@zapier/zapier-sdk"
const zapier = createZapierSdk({
apiKey: process.env.ZAPIER_API_KEY,
})
export async function runMoovsAction() {
const { data: connection } = await zapier.findFirstConnection({
app: "webhooks-by-zapier",
owner: "me",
})
if (!connection) {
throw new Error("No approved Moovs connection was found")
}
const result = await zapier.runAction({
app: "webhooks-by-zapier",
action: "custom_request",
connection: connection.id,
input:
{
"method": "POST",
"url": "{{env.MOOVS_API_BASE}}/reservations",
"headers": "Authorization=Bearer {{secret.MOOVS_API_TOKEN}}",
"body": "{{lead.moovsReservationJson}}"
},
})
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.
Provider authorization
A reviewable connection, step by step.
- 01Confirm Moovs API access
- 02Select account and locations
- 03Map vehicle and trip statuses
This app is cataloged and its workflow contract is defined. We will enable the connection after provider access and sandbox verification.
Related apps