Use “Post-meeting follow-up extractor” in Recued. Detect half of the post-meeting loop.

How it works 22 steps

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

Process (22 steps)

■ event_id default

Apply default

■ has_event compare

Check if event id has data

■ event_summary default

Apply default

■ event_status default

Apply default

■ event_end_at default

Apply default

■ source_id default

Apply default

■ notes_raw default

Apply default

■ notes truncate

Truncate notes raw to a max length

■ event_confirmed compare

Check if event status equals confirmed

■ event_has_ended is_past

Check if is in the past

■ notes_present compare

Check if notes has data

■ notes_mention_action contains_any

Apply contains_any

■ skip_extract any

Check if any of the conditions are true

■ protect pii-protect

Apply pii-protect

■ extracted ?

skip: step.skip_extract equal true

■ action_items_raw default

Apply default

■ restore pii-restore

Apply pii-restore

■ action_items default

Apply default

■ action_item_count count

Count items in action items

■ proposals_table to_table

Format results as a data table

■ gate_note ternary

Apply ternary

■ card to_summary

Format results as a summary card

Settings 4 configurable

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

action terms setting = action,todo,to-do,follow up,follow-up,next step,next steps,owner,due,deadline,will send,I'll,we'll,assign

after offsets setting = +15m

calendar slug setting = primary

max notes chars setting = 16000