Outcome
Render the current branded invoice email with effective From and Reply-To and optional custom message. No event, share, delivery or invoice mutation is created.
Before you start
- Verify the intended environment, authenticated identity and specifically approved organization context.
- The published application permission is invoices:read. Discover the exact granted canonical Books workspace and bind it separately from action input.
Discover the target
topolo whoami --json
topolo actions get app_topolo_books.invoices.email_preview --detail --json
topolo resources topolo-books --json
topolo workspaces list topolo-books --json
- Set BOOKS_WORKSPACE_ID to the exact granted workspace returned by discovery.
- documentId: Exact document.id from invoices.list/get or bills.list/get, as appropriate to this action; the displayed invoice number is distinct.
Request
POST /api/invoices/{documentId}/email-preview
Inspect and test this action. Save the reviewed input as payload.json; supply credential/resource context separately.
Input fields
| Field | Required | Meaning | Schema and constraints |
|---|---|---|---|
documentId | Required | Exact document.id from invoices.list/get or bills.list/get, as appropriate to this action; the displayed invoice number is distinct. | {"type":"string","minLength":1} |
recipientEmail | Required | Actual specifically approved recipient address; an example address does not authorize sending. | {"type":"string","maxLength":320,"format":"email","pattern":"^(?!\.)(?!.\.\.)([A-Za-z0-9_'+\-\.])[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\-]*\.)+[A-Za-z]{2,}$"} |
recipientName | Optional | recipient Name | {"type":"string","maxLength":200} |
message | Optional | message | {"type":"string","maxLength":2000} |
Inspect nested fields and the complete input schema.
Effects
- Renders the branded email without sending or creating a public invoice share.
Interpret the response
Read $.documentId for the returned invoice identifier. Empty collections and nullable fields do not discover a target.
Inspect preview.from, preview.replyTo, preview.subject, preview.html and attachment filenames.
Inspect the success schema. CLI/MCP add their own transport envelope; CLI --detail requests the full result.
Worked examples
Actual Books route handlers and the exported Worker were exercised against five local SQLite D1 concern databases with all committed migrations, the real posting Durable Object and local R2. Route captures use synthetic verified Auth; Worker captures use synthetic Auth transports. Nexus, Brand, Notify, Pay, Mercury and Xero responses are explicitly simulated at the provider transport boundary. Captures prove local request/response behavior and canonical SDK projection, not live bank access, payment movement, email delivery, provider eligibility, tax compliance, encrypted custody, scheduled execution, deployment or production completion. Fixture identities, credentials, addresses and records authorize no live operation.
Run a reviewed request
Save the input from the selected worked example as payload.json. Validate and inspect the plan before calling the action; refused examples demonstrate errors and are not instructions to execute.
CLI:
topolo actions validate app_topolo_books.invoices.email_preview --data @payload.json --json
topolo actions plan app_topolo_books.invoices.email_preview --resource-type workspace --resource-id "$BOOKS_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_books.invoices.email_preview --resource-type workspace --resource-id "$BOOKS_WORKSPACE_ID" --data @payload.json --detail --json
MCP tool and arguments for the first successful example:
{
"tool": "topolo_read_action",
"arguments": {
"actionId": "app_topolo_books.invoices.email_preview",
"input": {
"documentId": "doc_9ada81eb3f4c4f648fff8d8640edd8cd",
"recipientEmail": "recipient@example.com"
},
"resourceType": "workspace",
"resourceId": "<exact granted workspace id>",
"detail": true
}
}
Successful response · HTTP 200
Input · payload.json:
{
"documentId": "doc_9ada81eb3f4c4f648fff8d8640edd8cd",
"recipientEmail": "recipient@example.com"
}
Captured response · HTTP 200
{
"documentId": "doc_9ada81eb3f4c4f648fff8d8640edd8cd",
"preview": {
"from": "Fixture Accounts <accounts@example.com>",
"replyTo": null,
"subject": "Fixture invoice preview",
"html": "<p>Fixture invoice</p>",
"text": "Fixture invoice",
"attachments": [
{
"filename": "inv-000001.pdf",
"contentType": "application/pdf"
}
]
}
}
HTTP 200. Inspect preview.from, preview.replyTo, preview.subject, preview.html and attachment filenames.
Refused response · auth_error
Input · payload.json:
{
"documentId": "invoice_example",
"recipientEmail": "customer@example.com",
"message": "Thank you."
}
Captured response · HTTP 401
{
"error": "API key validation failed"
}
HTTP 401. SDK error code auth_error. Authenticate in the intended organization again. Verify whoami and the exact Books application/workspace binding before retrying; do not switch identity to work around a refusal.
Verify the result
- Inspect preview.from, preview.replyTo, preview.subject, preview.html and attachment filenames.
Errors and recovery
auth_error(HTTP 401): Authenticate in the intended organization again. Verify whoami and the exact Books application/workspace binding before retrying; do not switch identity to work around a refusal.
These are observed local refusals. Shared authentication, schema validation and resource authorization can also refuse before the route. Preserve the actual error, details and request id.
Recovery boundary
Repeat a read in the same authorized context; no state is changed.
Related actions
- List invoices: List invoices newest first. Filter by status, contact or issue date, search the number, reference and notes, and sort by issue date, due date, number, total or status. The response carries the outstanding total for the filtered set.
Evidence
Actual Books route handlers and the exported Worker were exercised against five local SQLite D1 concern databases with all committed migrations, the real posting Durable Object and local R2. Route captures use synthetic verified Auth; Worker captures use synthetic Auth transports. Nexus, Brand, Notify, Pay, Mercury and Xero responses are explicitly simulated at the provider transport boundary. Captures prove local request/response behavior and canonical SDK projection, not live bank access, payment movement, email delivery, provider eligibility, tax compliance, encrypted custody, scheduled execution, deployment or production completion. Fixture identities, credentials, addresses and records authorize no live operation.