Skip to content
English
  • There are no suggestions because the search field is empty.

Alert on short meetings

Send a Slack DM when a booking ends after less than 15 minutes — a useful signal that a room is being hogged for quick chats, or that a team is over-booking and bailing. For office managers tuning utilization or coaching teams on booking habits.

What this workflow does

  • A Booking Ended trigger fires whenever a meeting wraps up.
  • A Duration Range condition compares the booking's startAt and endAt against a 15-minute threshold.
  • Only short bookings continue to the next step; everything else ends silently.
  • A Send Direct Message action posts a Slack note to the organizer (or your facilities Slack channel).

     The finished workflow on the canvas: a Booking Ended trigger connected to a Duration Range condition. The condition's true port goes into a Send Direct Message action; the false port is unconnected.

Prerequisites

Build it

1. Create the workflow

From the Workflows list click New workflow, name it Alert on short meetings, and open the editor.

2. Add the booking trigger

  1. Click Add nodeTriggersBooking Ended.
  2. No settings to fill in — the trigger fires for every Booking Ended event your org receives.

3. Add the Duration Range condition

  1. Click Add nodeConditionsDuration Range.
  2. In the inspector:
    • From — click the data-reference icon and pick trigger → event → startAt.
    • To — same picker, pick trigger → event → endAt.
    • ModeShorter than.
    • Threshold15m.

Wire an edge from the trigger to the Duration Range's input.

Note: startAt and endAt are datetime objects. The condition reads both shapes (epoch and RFC3339) automatically — you don't have to think about the format.

4. Add the Slack action

  1. Click Add nodeActionsSend Direct Message.
  2. Settings:
    • Recipient Email — pick trigger → event → organizer → email from the data picker for a per-booking DM, or hard-code a facilities email if you'd rather centralize.
    • Content typemarkdown.
    • Message — paste:
       :clock4: Short booking ended in *{{ .trigger.event.space.name }}* — *{{ .trigger.event.subject }}*. Anything we can do to help?  
  3. Wire the true port of the Duration Range condition to the Slack action's input. Leave the false port unconnected.

5. Test it

  1. Click Run workflow.
  2. Edit the trigger payload to mock a short meeting:
    {   "event": {     "id": "evt-test",     "subject": "Quick chat",     "space": {"id": "sp-1", "name": "Phone Booth"},     "organizer": {"email": "you@example.com"},     "startAt": {"kind": "epoch", "timestamp": 1735689600},     "endAt": {"kind": "epoch", "timestamp": 1735690200}   } } 

    That's a 10-minute booking — short enough to trigger the alert.

  3. Click Run and confirm the DM lands.

6. Save and enable

Click Save, leave Enabled on, write a commit message ("Short-meeting alerts via Slack"), and the workflow takes over from the next Booking Ended onwards.

Variations

  • Different threshold. Set Mode to Between with a min/max if you only care about the 5-15 minute band, or Longer than with 2h for unusually long bookings.
  • Limit to one space. Chain a Is Same Space condition before Duration Range and configure the space ID. The DM only fires for that room.
  • Roll-up alerts. Wire the true branch into a Cooldown node first to avoid pinging on every short booking — see Stateful conditions.
  • Email instead of Slack. Swap the action for Send Email from the SMTP integration.

When it doesn't fire

If you expect a short-meeting alert and nothing arrives:

  1. Open Executions. The Booking Ended trigger should show a green run. If it doesn't, the workflow isn't Enabled or the booking system didn't emit the event.
  2. If the trigger fired, expand the Duration Range step. The trace shows the resolved from / to and the comparison result. Double-check the threshold isn't accidentally 15s or 15h.
  3. Slack delivery problems are surfaced on the action step. See Slack — When Slack stops working.

Related