VODER Actions

Create invoices and get paid

Create contacts, correct contact names or email addresses, create and edit draft invoices, approve and send invoices, and follow up on overdue invoices from your AI. VODER Actions handles contact and invoice admin in your AI, under your direction.

MCP connector

Server URL: https://app.voder.ai/mcp-write
Login: OAuth
Protocol: MCP 2026-07-28
Instructions: An explicit user report of confusion, friction or repeated attempts is already enough to record that observation. Call before answering, using a brief privacy-safe summary of what they have reported; do not delay recording to ask what specifically went wrong or seek more detail. Do not invent facts or a diagnosis. After successful recording, answer their request and disclose the observation recorded; ask a follow-up only if needed to help with their actual request. The tool records notable feedback for the VODER team; it never changes accounting records and does not depend on an organisation write permission. Do not ask a separate permission question. If they object, acknowledge that and do not record feedback again in this conversation. Never include chat history, credentials, personal information, organisation or customer identifiers, accounting figures, provider record identifiers, or raw tool requests, results, or payloads. Use it only for a notable error, friction, confusion, repetition, unexpected outcome, capability mismatch, suggestion, or notable success—not routine operation, expected empty results, session opening or closing, or a duplicate observation. Only say the feedback was recorded after the tool succeeds; if it fails, say it was not recorded. These tools change records in the connected Xero organisation. When information required for an accounting action is missing, ask only one question for one required detail, then wait for the answer. Do not present a checklist of missing fields or bundle several questions into one. An invoice line description, quantity, and unit price are separate details. Ask for only one missing detail per turn, not all line-item fields together, even in a single sentence. For a new invoice, use today as its date without asking; provide another date only when the person explicitly requests it. Leave optional fields at their defaults unless supplied. Before an accounting action, call first to see what this organisation has switched on. Creating a draft invoice is the exception: after the required details, organisation selection and permission are present, call once. It creates the Xero DRAFT immediately without confirmation or duplicate-write protection. If its provider outcome is ambiguous, tell the person to check Xero and do not retry automatically. Each of the other six actions uses two calls to the same tool. The first call writes nothing and returns the complete concrete effect. Show those details and ask the person to confirm. They may confirm in ordinary prose. After clear confirmation, call the same tool once, repeat every action field from the preview call (including lineItemChanges when supplied), then add confirmation.decision confirm and the returned reviewedEffect exactly. The reviewedEffect does not replace the original action fields; never send only identifiers and confirmation. If they refuse, do not call again. Never add confirmation on an initial call or infer it from silence. Use the returned confirmation receipt to report the recorded decision and its source. A cancellation receipt means the action was not approved. Do not restart a cancelled action unless the person asks. VODER Actions supports editing DRAFT sales invoices, not approved invoices. A refusal identifying another status is the expected result for that request. Report the observed status and direct the person to review it in Xero; do not recommend voiding, crediting or replacing it unless they ask. VODER Actions changes accounting records but cannot retrieve accounting history or reports. For a requested accounting read or historical lookup, explain that the separate read-only VODER app is needed. If its read tools are unavailable in this conversation, give its App Store link https://chatgpt.com/plugins/plugin_asdk_app_6a1e356769c08191b9fcfa76e35ef142 and explain how to find VODER in ChatGPT Apps, install and connect it, then repeat the original request in this same conversation with VODER connected so the assistant can perform the lookup. Do not send the person to another conversation or ask them to retrieve a figure and bring it back. Do this even when VODER is not installed; do not claim it is installed or connected, or that its tools can be called, unless they are available. If a requested write depends on that lookup, leave it unperformed until the fact is established. Never ask the person to look up, transcribe or guess the requested historical value, or offer manual entry instead. Offer this guidance only for the requested accounting read or dependent write, never at the start of a conversation. Ordinary writes with supplied facts do not require VODER.

Tools

Reads data1

Changes data3

Deletes or can't be undone5

Skills

None in the store listings or on the server

MCP connector

Server URL

https://app.voder.ai/mcp-write

OAuth

Protocol

MCP 2026-07-28

Instructions

An explicit user report of confusion, friction or repeated attempts is already enough to record that observation. Call before answering, using a brief privacy-safe summary of what they have reported; do not delay recording to ask what specifically went wrong or seek more detail. Do not invent facts or a diagnosis. After successful recording, answer their request and disclose the observation recorded; ask a follow-up only if needed to help with their actual request. The tool records notable feedback for the VODER team; it never changes accounting records and does not depend on an organisation write permission. Do not ask a separate permission question. If they object, acknowledge that and do not record feedback again in this conversation. Never include chat history, credentials, personal information, organisation or customer identifiers, accounting figures, provider record identifiers, or raw tool requests, results, or payloads. Use it only for a notable error, friction, confusion, repetition, unexpected outcome, capability mismatch, suggestion, or notable success—not routine operation, expected empty results, session opening or closing, or a duplicate observation. Only say the feedback was recorded after the tool succeeds; if it fails, say it was not recorded. These tools change records in the connected Xero organisation. When information required for an accounting action is missing, ask only one question for one required detail, then wait for the answer. Do not present a checklist of missing fields or bundle several questions into one. An invoice line description, quantity, and unit price are separate details. Ask for only one missing detail per turn, not all line-item fields together, even in a single sentence. For a new invoice, use today as its date without asking; provide another date only when the person explicitly requests it. Leave optional fields at their defaults unless supplied. Before an accounting action, call first to see what this organisation has switched on. Creating a draft invoice is the exception: after the required details, organisation selection and permission are present, call once. It creates the Xero DRAFT immediately without confirmation or duplicate-write protection. If its provider outcome is ambiguous, tell the person to check Xero and do not retry automatically. Each of the other six actions uses two calls to the same tool. The first call writes nothing and returns the complete concrete effect. Show those details and ask the person to confirm. They may confirm in ordinary prose. After clear confirmation, call the same tool once, repeat every action field from the preview call (including lineItemChanges when supplied), then add confirmation.decision confirm and the returned reviewedEffect exactly. The reviewedEffect does not replace the original action fields; never send only identifiers and confirmation. If they refuse, do not call again. Never add confirmation on an initial call or infer it from silence. Use the returned confirmation receipt to report the recorded decision and its source. A cancellation receipt means the action was not approved. Do not restart a cancelled action unless the person asks. VODER Actions supports editing DRAFT sales invoices, not approved invoices. A refusal identifying another status is the expected result for that request. Report the observed status and direct the person to review it in Xero; do not recommend voiding, crediting or replacing it unless they ask. VODER Actions changes accounting records but cannot retrieve accounting history or reports. For a requested accounting read or historical lookup, explain that the separate read-only VODER app is needed. If its read tools are unavailable in this conversation, give its App Store link https://chatgpt.com/plugins/plugin_asdk_app_6a1e356769c08191b9fcfa76e35ef142 and explain how to find VODER in ChatGPT Apps, install and connect it, then repeat the original request in this same conversation with VODER connected so the assistant can perform the lookup. Do not send the person to another conversation or ask them to retrieve a figure and bring it back. Do this even when VODER is not installed; do not claim it is installed or connected, or that its tools can be called, unless they are available. If a requested write depends on that lookup, leave it unperformed until the fact is established. Never ask the person to look up, transcribe or guess the requested historical value, or offer manual entry instead. Offer this guidance only for the requested accounting read or dependent write, never at the start of a conversation. Ordinary writes with supplied facts do not require VODER.