Ask Peasy

Find a single record by its exact UUID or extracted name/SKU, without guessing. Returns resolved, ambiguous (ask the person), or not_found (suggestions are not confirmed matches). Items resolve to a family while preserving the matched variant. Customer groups support ONLY all_active or payment_terms with exact nonnegative integer days; both exclude channels. Do not infer wholesale, overdue, best, catalog, or arbitrary groups. Group responses are live bounded pages: use nextCursor with the same selector until hasMore is false. A page is not an approved write snapshot. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

resolveRecords

Get full details for a specific bill including line items. Look up by bill number or ID. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getBillDetails

Get one data import run by ID with status, record counts, and app review/history links. Use when a user asks what happened to a specific staged import. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getSourceImportRun

Summarize inventory movements for an item and/or date range: total consumed, total received, net change, and recent transactions. Item names/SKUs resolve through searchItems and ambiguous families are returned for retry instead of selected arbitrarily. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getInventoryHistory

Get full details for a specific invoice including line items, amounts, payment status, and the linked sales order. Look up by invoice number (e.g. "INV-0042") or invoice ID. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getInvoiceDetails

Get detailed info for a specific item family by name, SKU, or ID. Text resolution uses searchItems and only auto-selects when one family matches; otherwise it returns candidates for a retry. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getItemDetails

Get full details for a specific purchase order or sales order including line items, quantities, and receive status. orderType is preferred, not absolute: the lookup also checks the sibling type and reports the actual type when corrected. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getOrderDetails

Get all invoices for a sales order with a payment rollup summary. Use when the user asks how much has been paid, invoiced, or is still owed on a specific order (e.g. "how much has Acme paid on SO-0042?"). Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getOrderInvoiceSummary

Get one entity-scoped payment from the local mirror. Returns canonical Payments History status, amount, direction, method, raw origin, customer-facing originLabel, processedByPeasyPayments (true, false, or null when origin is unavailable), document and counterparty context, stored failure reason, deterministic next action, snapshot time, and Peasy link. Classify with processedByPeasyPayments and explain with originLabel; never guess when it is null, and remember method identifies the rail, not the processor. Never returns provider IDs, raw metadata, payer contact details, or banking data. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getPaymentDetails

Get full details for a specific RFQ including items requested, vendors invited, and their quote responses. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getRfqDetails

Get receiving history — items received against purchase orders. Filter by item, vendor, or date range. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getReceivingHistory

Get recent operational activity for this business across app usage, imports, receiving, payments, and integration syncs. Use this when you need recent context before answering questions about what changed lately. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getRecentEntityActivity

Get full details for a specific task/thread including follow-up tasks with due dates and assignees. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getTaskDetails

Get full details for a specific template including recipe steps (bill of materials) with input items, quantities, and durations. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getTemplateDetails

Get full details for a specific transfer order including line items with quantities and items being transferred. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getTransferOrderDetails

Get bills (invoices from vendors). Filter by status, vendor name, or date range. Use status "overdue" to find bills past their due date. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getBills

List the recent CSV working copies (id, name, row/column counts) so you can resume cleaning one up. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

listCsvWorkingCopies

List all categories for the entity. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getCategoryList

List recent data import runs with status, data import name, target, record count, and app review/history links. Useful after staging a CSV or when a user asks what imports need review. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getSourceImportRuns

Get customer invoices. Filter by invoice status (draft/issued), payment status (unpaid/partially_paid/paid/overpaid), aging (overdue/coming_due), customer name, or date range. Use agingStatus "overdue" to find all past-due invoices with a remaining balance. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getInvoices

List open sales orders by invoicing need (billing coverage). Use when the user asks which existing sales orders still need invoices, what to invoice next, which fully-shipped orders are not yet billed, or which orders already have a draft invoice waiting to send. Each row returns billingStatus (issued coverage: uninvoiced/partial/invoiced), fulfillmentStatus, ordered/invoiced/draft quantities, draft + issued invoice counts, and a recommendedAction (null when no invoice exists and no billing work remains). For one specific known order use getOrderInvoiceSummary instead. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getSalesOrdersForInvoicing

List locally mirrored payment summaries using the same status model as Payments History. Each result includes method (the payment rail), raw origin, customer-facing originLabel, and processedByPeasyPayments (true, false, or null when origin is unavailable). For processor questions, classify with processedByPeasyPayments and explain with originLabel; never guess when it is null or infer the processor from card, ACH, check, or another method. Filter by direction, status, date, method, document number, counterparty, or reference. Use this to resolve a payment ID before getPaymentDetails. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getPayments

Get requests for quotation (RFQs). Filter by status or search by number/subject. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getRfqs

Look up recent application errors for this business. For QuickBooks questions call getQuickBooksSyncStatus first; these logs do not establish current sync status or explain an unrelated warning. Use when the user mentions encountering errors, when helping debug an issue, or when the user clicked "Get help" on an error notification. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getRecentEntityErrors

Get recent purchase orders or sales orders with status, dates, and totals. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getRecentOrders

Get tasks/threads (tasks, quotes, samples, notes). Filter by type, stage, or search by title. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getTasks

Get work order templates (recipes/BOMs). Returns template name, output item, type, yield quantity, and COGS. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getTemplates

Get transfer orders (stock movements between locations). Filter by status or search by transfer order number. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getTransferOrders

Get work orders (manufacturing/production). Filter by status, item being produced, or date range. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getWorkOrders

Look up a customer by name. Returns contact info and recent order history. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getCustomerInfo

Look up a vendor/supplier by name. Returns contact info and recent PO history. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getVendorInfo

Read current stored QuickBooks connection health, configured directions, exact attention and classified failure/blocked/informational totals with bounded record examples and review links. Use FIRST for QuickBooks sync, warnings or connection questions. Read-only: never refreshes, reconnects or retries. Token expiry/failures do not prove revoked authorization. Generic recent errors are supplementary, not authoritative sync status. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getQuickBooksSyncStatus

Explain an item's cost across units: the per-inventory-unit cost (the Google Sheets export "Expense Value ($)" column) vs each variant's per-unit cost (shown on the item detail panel), with the conversion ratio between them. Use when a user asks why a cost differs between their Google Sheet and the item detail, or to confirm a variant's inventory unit, conversion ratio, or cost. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getItemCostBreakdown

Summarize sales by item over a date window: units sold, revenue, COGS, gross profit/margin, and order count per item, sorted best-seller first. Use for "what was my best seller last month" or, with itemName, "how many X did I sell". "Sold" counts placed orders (status "open") and excludes draft quotes, cancellations, and deleted orders. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

getSalesSummary

Search for items/products by name or SKU. Returns matching items with IDs and details. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

searchItems

Search Peasy walkthrough videos for visual explanations of how features work. Use when the user explicitly asks for a video/demo/walkthrough or when a visual explanation is likely to be the single best primary resource. Returns matching video titles, descriptions, and URLs. When a video is the one primary CTA/resource you choose, include it in your reply using the [video:Title](url) marker so the chat UI renders a clickable play card. Do not include a video just because searchSupportDocs was used. Query tips: - Use feature names and action verbs (e.g., "create purchase order", "how items work") Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

searchVideos

Suggest a pre-authored onboarding journey chain (or partial snippet) that can be reused dynamically in a reply. Use when a user asks for workflow guidance and would benefit from the structured inventory/buy/receive/make/sell/demo journey steps. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

suggestJourneyChain

View a page of a CSV working copy (columns + a page of rows + totals) to inspect its current state. 0-based `page`; each page is 20 rows. Responses include a `peasy_url` field on entity records — surface it as a clickable "Open in Peasy" link so the user can drill into the full record in Peasy.

viewCsvWorkingCopy