Recued
Menu
← Back to recipes

Create an approved follow-up commitment

by recued-core v2 28 views

Use “Create an approved follow-up commitment” in Recued. It carries out the named workflow using the connections and settings you choose.

Complete workflow

Outbound Follow-Up Loop 13 pinned recipes

Use Outbound Follow-Up Loop in Recued for solo, cold start, email, and mail. It includes 9 ready-to-run workflows and 2 related packs in one install.

You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.

Use “Outbound follow-up queue” in Recued. It provides a read-only outbound follow-up queue for a one-person company.

emailmailoutboxfollowup
by recued-core pinned v1

Use “Batch approve follow-up sends” in Recued. Action workflow over Email/Outbox. Scans likely silent outbound threads, drafts plain-text follow-ups, then sends the selected batch through the mail-send kernel ingredient. Changes remain behind Recued's approval controls.

emailmailfollowupoutbox
by recued-core pinned v1
Show all 13 recipes

Use “Schedule an approved meeting hold” in Recued. It carries out the named workflow using the connections and settings you choose.

emailmailcalendarmeeting
by recued-core pinned v2
View pack details, dependencies, and permissions →
How it works 40 steps

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

Data fetch
▼ proposals core.storage.shared.list
List storage shared
▼ watch_rows core.storage.shared.list
List storage shared
▼
Process (38 steps)
■ proposals_family filter
Filter by condition
■ pending_proposals filter
Filter by condition
■ has_target compare
Check if setting proposal thread key has data
■ targeted_proposals filter
Filter by condition
■ selected_pool ternary
Apply ternary
■ candidate_proposals slice
Take a subset of
■ pending_count count
Count items in pending proposals
■ has_candidate compare
Check if candidate proposals has data
■ defaults defaults
Apply defaults
■ 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
■ defaults_2 defaults
Apply defaults
■ counterparty_email trim
Trim whitespace from counterparty email raw
■ extraction_confidence default
Apply default
■ source_rows filter
Filter by condition
■ has_source_row compare
Check if source rows has data
■ source_already_committed compare
Check if source rows 0 value commitment id has data
■ has_thread compare
Check if thread id has data
■ has_response_record compare
Check if response record id has data
■ has_commitment_statement compare
Check if commitment statement has data
■ skip_create any
Check if any of the conditions are true
■ skip_counterparty_resolve any
Check if any of the conditions are true
◆ resolve_counterparty core.contact.resolve
Resolve contact
skip: step.skip_counterparty_resolve equal true
■ commitment_key_hash sha256
Apply sha256
◆ commitment_created core.work-entity.commitment.create
Create work entity commitment
skip: step.skip_create equal true
■ has_commitment compare
Check if commitment created commitment id has data
■ skip_finalize any
Check if any of the conditions are true
◆ mark_proposal_created core.storage.shared.write
Write storage shared
skip: step.skip_finalize equal true
◆ write_converted_state core.storage.shared.patch
Patch storage shared
skip: step.skip_finalize equal true
◆ link_commitment_to_reply_mail core.memory.link.create
Create memory link
skip: step.skip_finalize equal true
■ has_prior_mail_record compare
Check if prior mail record id has data
■ skip_source_link any
Check if any of the conditions are true
◆ link_commitment_to_source_mail core.memory.link.create
Create memory link
skip: step.skip_source_link equal true
■ card to_summary
Format results as a summary card
▼
Output
summary card
Settings 1 configurable

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

proposal thread key setting =

Uses (6 operations)

Shared store List storage shared core.storage.shared.list
Contacts Resolve contact core.contact.resolve
Tasks & notes Create work entity commitment core.work-entity.commitment.create
Shared store Write storage shared core.storage.shared.write
Shared store Patch storage shared core.storage.shared.patch
Memory Create memory link core.memory.link.create

Trust & control

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

What it's allowed to do

Read Shared store core.storage.shared.list read-only
Read Contacts core.contact.resolve read-only
Write Tasks & notes core.work-entity.commitment.create external change
Write Shared store core.storage.shared.write external change
Write Shared store core.storage.shared.patch external change
Write Memory core.memory.link.create external change

Data it touches

SurfacesShared storeContactsTasks & notesMemory
Warehousedata.commitmentdata.maildata.shared

About

Tags

emailmailcommitmentfollowupconversionapprovalclosed-loopone-person-companystate:outbound-follow-up-response-watcher

Details

40 steps 1 configurable settings recipe_id: outbound-follow-up-create-approved-commitment