Show the owner what must be decided before Recued can run as a visible operating system: business profile, owner identity, external service lanes, inbox, calendar, weekly review cadence, and follow-up default. This recipe is read-only and intentionally does not pretend to inspect connection state.
SMB Finance Starter - QuickBooks
One-install front door for a small business that keeps its own books on QuickBooks Online. Install this first: it lights up locally at cold start with first-run onboarding, a Recued-native setup profile, and a unified work queue that pulls inbound email, calendar, and follow-ups into one prioritized list, plus mail-attachment invoice intake that parses a received invoice/receipt with the docling document toolkit and stages the extracted fields preview-first. It deepens when you bind QuickBooks and a Google Drive receipts folder: the daily back-office becomes a live AR / overdue / cash-in cockpit, overdue-invoice-chase drafts one reminder per past-due customer and sends the owner-approved batch through the mail-send gate, and the Drive folder-watch lane stages each new document through the same docling parse. Born blocked, honestly: before the QuickBooks and Google Drive binds the local queue and mail-attachment intake still run, while the accounting and Drive lanes show "connect QuickBooks / Google Drive." Capability packs own the execution points and gates - every QuickBooks write (invoice/payment/refund/void) and every Google Drive folder write stays approval-gated in accounting-quickbooks and gdrive, and customer email only ever sends owner-approved. This pack owns the working operating model; the capability packs own the money and the actuation. Shipped pinned to QuickBooks; collapses to the vendor-agnostic smb-finance-starter once Xero lands.
What this pack installs
Included recipes
11 pinned recipes
This pack installs the complete recipe workflow together. 5 supporting recipes run as background automation.
Optionally seed the owner's Recued-native operating system with a setup profile note, setup project, setup tasks, and weekly owner-review commitment. Defaults to preview; switch write_mode to create when the owner wants records written.
Read-only operating queue for a one-person company. It gathers Recued-native work signals from tasks, commitments, projects, notes, mail, calendar, and contact rollups into one view so the owner can see where attention is leaking before opening separate desks.
Classify each inbound email into urgent_action / awaiting_response / fyi / promotional / spam and send an in-app notification for urgent_action + awaiting_response (subject, sender, suggested next action). Promotional / spam classify silently — no notification noise on bulk mail. Fires automatically on inbound mail; the classifier model sees only PII-aliased text, never the raw sender.
Extract commitments from an inbound email into Recued's commitment tracker — who promised what to whom, with optional deadline and monetary amount. Thread-aware: a reply like 'yes, please send that by Friday' binds to the prior message, not the reply. Fires automatically on each inbound message; records only extractions above the confidence floor (default 0.7), resolves the counterparty to a known contact when possible, and the extractor model sees only PII-aliased text, never the raw sender.
Extract action items from an inbound email into Recued's task tracker — title, due date, and priority (low / medium / high). Thread-aware; fires automatically on each inbound message; records only extractions above the confidence floor (default 0.7). A task is assigned to a contact only when the mail explicitly delegates it to a named third party — otherwise it lands unassigned. The extractor model sees only PII-aliased text, never the raw sender.
Show all 11 recipes
Record a per-contact meeting-reschedule pattern whenever an event's start time actually changes (title-only edits don't fire) — the behavioral signal time-alert-before-event reads for its briefs.
Reactive silent producer. Listens to calendar.created + calendar.updated events; for each fired event builds the cheap pre-summarized rollup the alert recipe consumes. Writes calendar_event_rollup keyed on event_id with a deterministic brief (event summary + attendee count + start_at) plus the canonical attendee list. Dependent policy means deletion of the underlying event cascades the rollup automatically. The full attendee-pattern fold (which would walk timeline-read for each participant) deepens in D-124 housekeeping; this v1 producer keeps the rollup fresh for every newly-created or modified event.
Reactive silent producer. Listens to mail.created events; extracts the sender's email and stamps a contact_timeline_rollup enrichment with the latest interaction signal. Aggregate-policy upsert keyed on contact email. D-122 ships the cheap deterministic fields only — interaction_count seeded at 1, last_interaction set, recent_subjects single-element. The fuller fold (rolling window, attendee co-occurrence, thread-aware subject deduplication) ships in D-124 housekeeping once timeline-read becomes the producer's primary input. Calendar-side contact contributions also defer to the housekeeping pass.
Parse a received invoice or receipt (PDF / image / DOCX / scan) with the local docling tool into readable text - so any text model can read it - then extract vendor, number, amount, currency, and dates. Preview-first: shows the extracted fields and writes nothing; set write_mode to stage to persist a staged invoice/expense row into data.shared. Writes no accounting system - staging is the holding area for later review and posting. Content-isolated via Gateway-gated file refs.
Watch a Google Drive folder for new invoice / receipt documents and stage their extracted finance data. Polls the folder via the gdrive file.list operation, picks the newest document that is not a Google-native file, downloads its bytes straight into the warehouse CAS as a Gateway-gated data.file (file.download surfaces result.file_ref, so the bytes never flow through op-step values), parses it to Markdown with the local docling tool (which materializes the file_ref to a temp file it reads), and pulls vendor, number, amount, currency, and dates from the parsed Markdown via the same file-ref isolation. Preview-first: by default it shows the extracted fields and writes nothing; set write_mode to stage to persist a durable staged invoice/expense row into data.shared for later review and posting. A per-run context guard skips re-processing the same newest file across polls. This is the Drive-folder source lane for the SMB-finance intake; the manual single-document lane is invoice-intake-organizer.
Builds on
- email-outbox-pack v1+
- solo-first-run-setup v1+
- solo-work-queue v1+
- acct v1+
- accounting-quickbooks v1+
- gdrive v1+
- docling v1+
- smb-invoice-finance v1+
Trust & control
What installing this whole pack would let it do. Recued grants these permissions at install — review them there before approving.