OTHER

No-Show Desk Reclaimer

Cross-references badge-in events against today's desk reservations and automatically releases desks whose holders never badged into the building by a cutoff time.

CategoryOther
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily cutoff schedule (e.g. 10:30 AM)
  • ActionQuery reservations joined to badge-in eventsGoogle BigQueryBigQuery
  • LogicFilter to reservations with no badge-in before cutoff
  • ActionRelease no-show desks via booking APIHTTP webhook
  • ActionDM affected employees about released holdsSlack
  • OutputPost reclaimed-desk summary to facilities channelSlack

What it does

Every weekday at a set cutoff (e.g. 10:30 AM), this workflow pulls the day's confirmed desk reservations and matches each one against badge-in data from the access-control system. Reservations whose holder has no badge-in event by the cutoff are flagged as no-shows, their desks are released back to available, and the holder is notified so they can re-book if they did show up late.

When to use it

Run it in any office on hybrid attendance where booked-but-unused desks block colleagues from finding a seat. It recovers wasted capacity without a facilities admin manually auditing the floor plan each morning.

How it works

  1. 1A scheduled trigger fires at the daily cutoff time.
  2. 2Query BigQuery for today's confirmed reservations joined to badge-in events keyed on employee ID.
  3. 3A filter keeps only reservations with zero badge-in events before the cutoff.
  4. 4For each no-show, call the desk-booking system's release endpoint via webhook to free the seat.
  5. 5DM each affected employee on Slack explaining their hold was released and how to re-book.
  6. 6Post a summary of reclaimed desks to the facilities channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect HTTP webhookTrigger any URL on agent actions.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.