Propose commitments from follow-up replies
Use “Propose commitments from follow-up replies” in Recued. It carries out the named workflow using the connections and settings you choose.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Data fetch
shared_followups
core.storage.shared.list
List storage shared
existing_proposals
core.storage.shared.list
List storage shared
▼
Process (43 steps)
existing_proposals_family
filter
Filter by condition
response_needed_rows
filter
Filter by condition
commitment_candidate_rows
filter
Filter by condition
already_committed_rows
filter
Filter by condition
already_committed_keys
map
Extract from each item
uncommitted_rows
filter
Filter by condition
proposed_thread_ids
map
Extract from each item
rows_without_proposal
filter
Filter by condition
candidate_rows
slice
Take a subset of
pending_count
count
Count items in rows without proposal
has_candidate
compare
Check if candidate rows has data
defaults
defaults
Apply defaults
proposal_key
default
Apply default
defaults_2
defaults
Apply defaults
has_response_record
compare
Check if response record id has data
has_response_mail_slug
compare
Check if response mail slug has data
skip_body_read
any
Check if any of the conditions are true
body_read
core.mail.body-read
Body read mail
skip: step.skip_body_read equal true
response_body
default
Apply default
body_present
compare
Check if response body has data
now_iso
date_add
Add 0 minutes to
skip_extract
any
Check if any of the conditions are true
protect
pii-protect
Apply pii-protect
extract_commitment
core.ai.extract
AI extracts structured fields from data
skip: step.skip_extract equal true
restore_commitment
pii-restore
Apply pii-restore
commitment_statement_raw
default
Apply default
commitment_statement
trim
Trim whitespace from commitment statement raw
raw_direction
default
Apply default
direction_is_outbound
compare
Check if raw direction equals outbound
direction_is_internal
compare
Check if raw direction equals internal
internal_or_inbound
ternary
Apply ternary
commitment_direction
ternary
Apply ternary
counterparty_email_raw
default
Apply default
counterparty_email
trim
Trim whitespace from counterparty email raw
promised_for_at
date_parse
Parse restore commitment restored promised for at iso as a date
extraction_confidence
default
Apply default
missing_statement
compare
Check if commitment statement is empty
below_confidence
compare
Check if extraction confidence is less than setting confidence threshold
skip_propose
any
Check if any of the conditions are true
write_proposal
core.storage.shared.write
Write storage shared
skip: step.skip_propose equal true
skip_notify
any
Check if any of the conditions are true
notify
core.notification.send
Send notification
skip: step.skip_notify equal true
card
to_summary
Format results as a summary card
▼
Output
summary
card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
channels
setting
=
[object Object]
confidence threshold
setting
=
0.65
Uses (5 operations)
Shared store
List storage shared
core.storage.shared.list
Mail
Body read mail
core.mail.body-read
AI models
AI extracts structured fields from data
core.ai.extract
Shared store
Write storage shared
core.storage.shared.write
Notifications
Send notification
core.notification.send
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.
Permissions it requires
Declared by the recipe — Recued grants these at install, where you review them before approving.What it's allowed to do
Read
Shared store
core.storage.shared.list
read-only
Read
Mail
core.mail.body-read
read-only
Read
AI models
core.ai.extract
read-only
Write
Shared store
core.storage.shared.write
external change
Read
Notifications
core.notification.send
external change