Recued
Menu
← Back to recipes

Watch outbound follow-up replies

by recued-core v3 27 views

Use “Watch outbound follow-up replies” in Recued. Reactive reply-side of the outbound follow-up loop.

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.

Watch outbound follow-up replies
This recipe Background automation

Use “Watch outbound follow-up replies” in Recued. Reactive reply-side of the outbound follow-up loop.

emailmailfollowupreply
by recued-core pinned v3

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 41 steps

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

Data fetch
▼ message core.mail.get
Get mail
▼
Process (40 steps)
■ defaults defaults
Apply defaults
■ has_thread_id compare
Check if thread id has data
◆ shared_followups core.storage.shared.list
List storage shared
skip: step.has_thread_id not_equal true
■ matched_followups filter
Filter by condition
■ has_pressure compare
Check if matched followups has data
■ watched_contact default
Apply default
■ has_watched_contact compare
Check if watched contact has data
■ prior_mail_record_id default
Apply default
■ has_prior_mail_record compare
Check if prior mail record id has data
■ need_derive_contact all
Check if all conditions are true
◆ source_mail core.mail.get
Get mail
skip: step.need_derive_contact not_equal true
■ derived_contact default
Apply default
■ resolved_contact default
Apply default
■ has_resolved_contact compare
Check if resolved contact has data
■ from_email_norm lowercase
Convert from email to lowercase
■ resolved_contact_norm lowercase
Convert resolved contact to lowercase
■ sender_mismatch any
Check if any of the conditions are true
◆ body_read core.mail.body-read
Body read mail
skip: step.has_pressure not_equal true
■ body default
Apply default
■ body_present compare
Check if body has data
■ skip_classify any
Check if any of the conditions are true
■ defaults_2 defaults
Apply defaults
■ protect pii-protect
Apply pii-protect
✦ classify core.ai.classify
AI classifies data into one of the given categories
skip: step.skip_classify equal true
■ restore pii-restore
Apply pii-restore
■ defaults_3 defaults
Apply defaults
■ below_confidence compare
Check if confidence is less than setting min confidence
■ is_automated_or_irrelevant compare
Check if category equals automated_or_irrelevant
■ is_closed compare
Check if category equals closed_or_no_action
■ skip_state_update any
Check if any of the conditions are true
■ status ternary
Apply ternary
■ next_pressure_score ternary
Apply ternary
■ owner_action switch
Map category to one of: positive_reply, meeting_requested, needs_owner_reply, closed_or_no_action, objection_or_blocker
◆ write_followup_state core.storage.shared.patch
Patch storage shared
skip: step.skip_state_update equal true
■ skip_response_link any
Check if any of the conditions are true
◆ link_response_to_watched_mail core.memory.link.create
Create memory link
skip: step.skip_response_link equal true
■ should_notify all
Check if all conditions are true
■ notify_title switch
Map category to one of: positive_reply, meeting_requested, needs_owner_reply, objection_or_blocker
◆ notify core.notification.send
Send notification
skip: step.should_notify not_equal true
■ card to_summary
Format results as a summary card
▼
Output
summary card
Settings 2 configurable

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

channels setting = [object Object]
min confidence setting = 0.55

Uses (7 operations)

Mail Get mail core.mail.get
Shared store List storage shared core.storage.shared.list
Mail Body read mail core.mail.body-read
AI models AI classifies data into one of the given categories core.ai.classify
Shared store Patch storage shared core.storage.shared.patch
Memory Create memory link core.memory.link.create
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

Send notifications
Declared by the recipe — Recued grants these at install, where you review them before approving.

What it's allowed to do

Read Mail core.mail.get read-only
Read Shared store core.storage.shared.list read-only
Read Mail core.mail.body-read read-only
Read AI models core.ai.classify read-only
Write Shared store core.storage.shared.patch external change
Write Memory core.memory.link.create external change
Read Notifications core.notification.send external change

Data it touches

SurfacesMailShared storeAI modelsMemoryNotifications
Warehousedata.shareddata.mail

About

Tags

emailmailfollowupreplyreactiveclosed-loopwork-queueone-person-companystate:outbound-follow-up-response-watcherpack:outbound-follow-up-responseai_surface

Details

41 steps 2 configurable settings recipe_id: outbound-follow-up-response-watcher