Mercury transaction review brief
Use “Mercury transaction review brief” in Recued. It provides a read-only Mercury transaction review with category and user context.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (8 steps)
transactions_raw
recued-core.mercury.transaction.search
Search transaction on mercury
categories_raw
recued-core.mercury.category.search
Search category on mercury
users_raw
recued-core.mercury.user.search
Search user on mercury
transactions
default
Apply default
transaction_count
count
Count items in transactions
summarize
core.ai.summarize
AI generates a concise summary
transaction_table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
▼
Output
summary
card
table
transaction_table
json
categories_raw.result
json
users_raw.result
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
end
setting
=
[object Object]
focus
setting
=
Identify visible transactions needing action: pending or failed status, missing notes or categories, receipt-policy exceptions, and suspicious counterparty or amount patterns. Use only returned Mercury data.
start
setting
=
[object Object]
search
setting
=
[object Object]
status
setting
=
pending
account id
setting
=
[object Object]
max length
setting
=
1200
Uses (4 operations)
Pack operation
Search transaction on mercury
recued-core.mercury.transaction.search
Pack operation
Search category on mercury
recued-core.mercury.category.search
Pack operation
Search user on mercury
recued-core.mercury.user.search
AI models
AI generates a concise summary
core.ai.summarize
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
AI models
core.ai.summarize
read-only
3 more aren't listed here. You'll see them at install.