OTHER
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.
How it runs
The automated pipeline, trigger to output.
- TriggerRecurring evening schedule
- ActionQuery overdue checked-in visitorsAirtable
- LogicBranch: past end-time vs after building close
- ActionAuto-checkout and update recordsAirtable
- ActionAlert security on guests still on-siteMicrosoft Teams
- OutputPost cleanup summary to facilitiesMicrosoft Teams
What it does
Keeps the visitor log honest. It closes out lingering check-ins automatically and surfaces the ones that need human attention, so your on-site count reflects reality and no guest is silently left unaccounted for overnight.
When to use it
Use it when guests sometimes leave without scanning out and your active-visitor list drifts. Essential for evacuation accuracy and for sites that must prove the building is empty at close.
How it works
- 1A scheduled trigger runs every evening (and optionally hourly during business hours).
- 2The flow queries Airtable for records with status `Checked in` whose expected departure has passed.
- 3A branch splits guests: those merely past their scheduled end time versus those still on-site after building close.
- 4Guests past close are auto-set to `Checked out (system)` with a note, and their hosts are notified in Teams to confirm the guest actually left.
- 5Any guest still flagged on-site after the close threshold triggers a security alert in the Teams operations channel with name, host, and last-seen time.
- 6A cleanup summary of all actions taken is posted for the facilities team.
Set it up
What you configure once, before turning it on.
- 1Connect AirtableBases, tables, views, automations.
- 2Connect Microsoft TeamsChannels, chats, files.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.
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.
Build a daily expected-visitor roster and send it to the front desk
Every morning this pulls the day's pre-registered visitors from Airtable, builds a sorted arrival roster with hosts and times.
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.