← Back to Skills Marketplace
20415
Downloads
12
Stars
0
Active Installs
13
Versions
Install in OpenClaw
/install xero
Description
Xero API integration with managed OAuth. Manage contacts, invoices, payments, accounts, and run financial reports. Use this skill when users want to interact with Xero accounting data. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Xero connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Xero action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Xero examples; they add no Xero capability - Xero is not an event source, a trigger cannot read Xero data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Install only if you intend to let Maton access your Xero accounting data. Prefer OAuth, choose the narrowest Xero scopes available, confirm every write or automation setup, and be especially careful with hosted functions, trigger destinations, or raw API-key use because they can create ongoing data access or forwarding.
Capability Assessment
Credentials
Network access, OAuth, OS credential-store use, and optional API-key fallback are proportionate for an accounting API integration and are disclosed with handling rules.
Install Mechanism
Installation uses pinned Maton CLI or SDK versions and describes OAuth login; no hidden install script, executable artifact, or remote payload execution was found.
Instruction Scope
The skill includes broad Maton function and trigger reference material, including other event sources, but it repeatedly scopes those sections to user-requested automation and warns that Xero itself is not an event source.
Persistence & Privilege
The skill can create persistent hosted functions, triggers, and destinations, but it documents approval, scoping, DENY_ALL network defaults, cleanup, and warnings for persistent forwarding and local --exec handling.
Purpose & Capability
The stated purpose is Xero API access for contacts, invoices, payments, accounts, bank transactions, and reports, and the documented capabilities match that purpose.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install xero - After installation, invoke the skill by name or use
/xero - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.5
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.4
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.3
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.2
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.1
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.5
- Updated all API endpoint URLs to use https://api.maton.ai instead of previous gateway or ctrl domains.
- Clarified connection management instructions to match new API base URL.
- Added explicit note in the connection section: always set the Maton-Connection header if you have multiple connections.
- Added a new Security & Permissions section noting that all write operations require explicit user approval.
- Removed LICENSE.txt file.
v1.0.4
- Added a new clawdbot metadata section to the skill manifest, specifying an emoji and required environment variable (MATON_API_KEY).
- No changes to functionality or documentation content.
v1.0.3
xero 1.0.3 Changelog
- Improved troubleshooting section: clarified distinction between API key issues and invalid app name errors.
- Added guidance to ensure URL paths start with "xero" for proper app routing.
- No code or functional changes; documentation update only.
v1.0.2
- Added guidance for using the api-gateway skill for other third-party apps.
- Replaced all shell cURL connection management examples with Python (urllib) examples for better portability and reliability with environment variables.
- Added troubleshooting advice and an expanded section to help resolve "Invalid API key" errors, including verification steps.
- Included important notes about using curl with brackets (requiring curl -g) and potential environment variable expansion issues when piping to other commands (like jq).
- No changes to functionality or code, documentation updates only.
v1.0.1
- Updated the base URL documentation to use /xero/{native-api-path} and clarified endpoint usage.
- Added instructions for specifying a connection with the Maton-Connection header, including behavior for multiple connections.
- Expanded example connection response details, including creation_time, last_updated_time, and metadata fields.
- Clarified API key acquisition (sign in or create an account) and endpoint documentation.
- No functional changes to the skill logic; documentation improvements only.
v1.0.0
Initial release: Integrate Xero accounting API with managed OAuth, supporting contacts, invoices, payments, accounts, bank transactions, and financial reports.
- Secure Xero API access via Maton-managed OAuth and API key.
- Manage Xero OAuth connections via web dashboard or API.
- Includes endpoints for contacts, invoices, payments, accounts, bank transactions, and core financial reports.
- Provides sample code for bash, JavaScript, and Python.
- Automatic handling of authentication headers and error codes.
Metadata
Frequently Asked Questions
What is xero?
Xero API integration with managed OAuth. Manage contacts, invoices, payments, accounts, and run financial reports. Use this skill when users want to interact with Xero accounting data. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Xero connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Xero action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Xero examples; they add no Xero capability - Xero is not an event source, a trigger cannot read Xero data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 20415 downloads so far.
How do I install xero?
Run "/install xero" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is xero free?
Yes, xero is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does xero support?
xero is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created xero?
It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.5.
More Skills