Recued
Menu
← Back to recipes

How many of my Calendly bookings were actually meetings

by recued-core v1 7 views

Use “How many of my Calendly bookings were actually meetings” in Recued. Splits a scheduled-event list on the two things it can honestly tell you apart. Cancelled events stay IN THE list — status is an optional filter, so a bookings count that omits it counts meetings that did not happen.

How it works 20 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (20 steps)
page_size clamp
Clamp setting count between 1 and 100
days clamp
Clamp setting window days between 1 and 365
me ?
user_uri default
Apply default
have_user template
Generate text from a template
fail: step.user_uri is_empty
window_start date_add
Add -{{step.days}} days to
events_raw ?
events default
Apply default
have_events template
Generate text from a template
fail: step.events is_empty
event_count count
Count items in events
status_values pluck
Extract status from each item
status_seen unique
Remove duplicates from
cancelled filter
Filter by condition
cancelled_count count
Count items in cancelled
uncancelled filter
Filter by condition
uncancelled_count count
Count items in uncancelled
by_start sort
Sort by start_time
recent_cancelled slice
Take a subset of
card to_summary
Format results as a summary card
cancelled_table to_table
Format results as a data table
Settings 3 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

count setting = 100
calendly setting =
window days setting = 30

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Permissions it requires

Read your Calendly connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

calendly calendlyschedulingmeetingsread-only

Details

20 steps 3 configurable settings recipe_id: review-booked-vs-held-calendly