OTHER
Reservation vs. Calendar Conflict Sync
Compares each desk reservation against the holder's calendar and badge data, then cancels desks held by people who are out-of-office or on all-day remote.
How it runs
The automated pipeline, trigger to output.
- TriggerEarly-morning schedule before office open
- ActionQuery today's reservations with holdersBigQuery
- ActionRead holder calendars for OOO/PTO/remoteGoogle Calendar
- LogicFlag reservations conflicting with absence
- ActionCancel conflicting holds via booking APIHTTP webhook
- OutputDM holders confirming cancellationSlack
What it does
This workflow catches desks reserved by people who clearly won't use them: anyone whose Google Calendar shows an all-day out-of-office, PTO, or remote block for the day. Early each morning it cross-checks reservations against calendars and recent badge history, cancels the conflicting holds, and notifies the holders so capacity is freed before colleagues start hunting for seats.
When to use it
Use it when standing reservations or recurring desk bookings pile up while people are traveling, on leave, or working from home, quietly locking out in-office staff.
How it works
- 1An early-morning scheduled trigger fires before office open.
- 2Query BigQuery for today's reservations with holder identifiers.
- 3For each holder, read Google Calendar for all-day OOO, PTO, or remote events.
- 4A logic step flags reservations that conflict with an out-of-office or remote block.
- 5Call the booking API webhook to cancel each conflicting hold and free the desk.
- 6DM each holder on Slack confirming the cancellation and that they can re-book if plans changed.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect Google CalendarEvents, attendees, availability.
- 3Connect HTTP webhookTrigger any URL on agent actions.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Other workflows
Sync IVR Prompt Registry in Airtable to Fresh ElevenLabs Audio
Runs nightly against an Airtable IVR prompt registry, finds rows whose script text changed since last synthesis, regenerates only those ElevenLabs clips.
Agent-Driven Full IVR Re-Voicing for a Rebrand
An agent takes a rebrand brief from Notion, audits every IVR prompt for old naming, rewrites and re-synthesizes the affected ones with ElevenLabs, archives them to Dropbox.
Regenerate IVR Voice Prompts When Notion Naming Doc Changes
Watches a Notion product-naming page and, whenever a product or feature name changes, regenerates the affected ElevenLabs IVR audio prompts and saves the new MP3s to Dropbox.
Pre-register a visitor, email a QR badge, and alert the host on arrival
When a host submits a visitor pre-registration form, this creates a visitor record, emails the guest a scannable QR badge with arrival instructions.
Sweep stale visitor check-ins, auto-checkout, and flag overdue guests
On a recurring schedule this finds visitors still marked on-site past their expected departure, auto-checks-out anyone past end-of-day.
Slack-Approved IVR Re-Voicing After a Product Rename
On demand from Slack, drafts updated IVR prompt scripts for a renamed product, posts them for human approval.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.