Special workflows for Google Calendar.
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.
Qualified request to calendar hold
Create a reviewable time hold once a customer has supplied the required booking details.
Starts when
A Volimox conversation is qualified with service, location, duration, and preferred time.
Result
The team can see a real scheduling hold without pretending the booking is final.
Volimox workflow
- 01Volimox checks the configured calendar for availability.
- 02Volimox creates a tentative event with the lead summary and internal notes.
- 03The operator confirms the hold or sends the customer an approved alternative.
Human checkpoint
Calendar creation is gated by the required booking fields and operator policy.
Calendar event to customer reminder
Keep customers and operators aligned as a confirmed appointment approaches.
Starts when
A Google Calendar event is created, updated, or reaches its reminder window.
Result
The calendar becomes a reliable timing signal for the customer handoff.
Volimox workflow
- 01Volimox verifies that the event is linked to the correct lead or booking.
- 02Volimox prepares the confirmation, reminder, or reschedule message.
- 03The approved update is recorded with the event and conversation references.
Human checkpoint
Canceled or ambiguous events are held for review instead of notifying the wrong customer.
Supported triggers and actions.
A trigger starts the workflow. An action is the controlled operation Volimox performs after the rules pass.
Triggers
- Event created
- Event updated
- Event starts soon
Actions
- Find availability
- Create event
- Update event
- Cancel event
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 tentative booking hold
import { createZapierSdk } from "@zapier/zapier-sdk"
const zapier = createZapierSdk({
apiKey: process.env.ZAPIER_API_KEY,
})
export async function runGoogleCalendarAction() {
const { data: connection } = await zapier.findFirstConnection({
app: "google-calendar",
owner: "me",
})
if (!connection) {
throw new Error("No approved Google Calendar connection was found")
}
const result = await zapier.runAction({
app: "google-calendar",
action: "create_detailed_event",
connection: connection.id,
input:
{
"calendar": "{{env.GOOGLE_CALENDAR_ID}}",
"summary": "Tentative: {{lead.service}}",
"start": "{{lead.requestedStartIso}}",
"end": "{{lead.requestedEndIso}}",
"description": "Volimox lead {{lead.id}}",
"attendees": "{{lead.email}}"
},
})
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.
Google OAuth
A reviewable connection, step by step.
- 01Choose one or more calendars
- 02Set timezone and working hours
- 03Review event read/write scope
This app is cataloged and its workflow contract is defined. We will enable the connection after provider access and sandbox verification.
Related apps