Skip to content
Recued
Menu
← Back to recipes

Wave invoice collections brief

by recued-core v1

Read-only Wave collections exception briefing. It reads a chosen invoice status bucket and asks the AI summarizer for exception-handling priorities: missing customer email, additional-recipient needs, unusual customer context, and largest or oldest receivables. Assume Wave native invoice reminders cover routine reminders. This recipe does not send invoice emails, mark invoices sent, record payments, update customers, or call arbitrary GraphQL.

Complete workflow

Workflow pack for Wave invoice-reminder exceptions. It adds a collections brief, an owner-approved Wave invoice email for cases native reminders cannot cover, and a scheduled watcher that closes the shared lifecycle when Wave reports the invoice paid or resolved. It depends on the Wave capability pack and does not create or edit invoices, record payments, change customers, or replace Wave native reminders.

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

Read-only Wave collections exception briefing. It reads a chosen invoice status bucket and asks the AI summarizer for exception-handling priorities: missing customer email, additional-recipient needs, unusual customer context, and largest or oldest receivables. Assume Wave native invoice reminders cover routine reminders. This recipe does not send invoice emails, mark invoices sent, record payments, update customers, or call arbitrary GraphQL.

waveinvoicescollectionscashflow
by recued-core pinned v1

Exception handler for Wave invoice reminders. Use this only when Wave's native invoice reminder automation is insufficient: the invoice customer has no primary email and the owner supplies an exception recipient, the reminder needs an additional recipient, or the owner provides a specific exception note. The recipe re-reads the business and invoice live from Wave, confirms the invoice still has an amount due, sends exactly one attended Wave invoice email, links the invoice to the customer, and seeds data.shared exception-watch state so wave-invoice-reminder-exception-watcher can close the loop when Wave shows the invoice paid or resolved. It never creates invoices, edits invoices, records payments, changes customers, deletes records, or calls arbitrary GraphQL.

waveinvoicecollectionsreminder-exception
by recued-core pinned v1

Scheduled adopter for Wave invoice reminder exception rows in data.shared. It reads the exception-watch ledger, re-reads one watched invoice from Wave, and marks the shared row responded_closed when the source of truth says the invoice is paid or has no amount due. It preserves the origin recipe id and does not send email, notify customers, record payments, edit invoices, change customers, or call arbitrary GraphQL.

waveinvoicecollectionsreminder-exception
by recued-core pinned v1
View pack details, dependencies, and permissions →
How it works 10 steps

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

Process (10 steps)
business ?
invoices_raw ?
invoices default
Apply default
invoice_count count
Count items in invoices
invoice_rows slice
Take a subset of
missing_email_rows filter
Filter by condition
missing_email_count count
Count items in missing email rows
brief ?
summary to_summary
Format results as a summary card
invoice_table to_table
Format results as a data table
Settings 6 configurable

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

wave setting =
focus setting = Prioritize invoice rows for exception handling only. Assume Wave native invoice reminders handle routine reminders. Call out missing customer email, likely additional-recipient needs, unusual context, and largest or oldest receivables. Do not suggest sending a duplicate reminder when native reminders can handle it. Do not imply any invoice was sent or paid unless the Wave records say so.
status setting = OVERDUE
page size setting = 25
max length setting = 900
business id setting =

Trust & control

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

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Wave connectionAi summarize
Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.business

About

Tags

wave waveinvoicescollectionscashflowai-summarypack:wave

Details

10 steps 6 configurable settings recipe_id: wave-invoice-collections-brief