fastbill

Generate FastBill XML API requests and parse responses for invoice operations.

126|11|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/HybridAIOne/hybridclaw --skill fastbill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fastbill
Source: https://github.com/HybridAIOne/hybridclaw/tree/main/skills/fastbill
Command: npx skills add https://github.com/HybridAIOne/hybridclaw --skill fastbill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the need to manually assemble and validate FastBill invoice operations, letting you reliably query and update invoices, customers, payments, reminders, and e-invoice exports using structured inputs.

Core Features & Use Cases

  • XML API bridging with validation: Converts JSON-shaped request data into FastBill’s required XML payloads and parses XML responses back into usable structured output.
  • Gateway-safe request patterns: Uses the built-in http_request flow for live calls so Basic auth is injected by the HybridClaw gateway via the FASTBILL_BASIC_AUTH secret route.
  • Read vs write guardrails: Enforces operator-grant for mutating services (e.g., invoice.create, invoice.setpaid, invoice.sendbyemail) and supports dry-run for safer conversions from messy inputs.

Quick Start

Ask the AI to create an invoice draft from tracked time for customer 123 by calling invoice.create with operator-grant enabled.

Frequently Asked Questions about fastbill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate FastBill invoice creation using the XML API?

FastBill invoice automation works by serializing JSON inputs into valid XML API requests for the invoice.create service. You must provide operator-grant permission for mutating calls, and can use dry-run mode to safely validate the XML payload before executing the actual write operation.

Can I mark FastBill payments as received and send reminders through API calls?

Yes, marking FastBill payments as received and sending reminders are supported through the invoice.setpaid and invoice.sendbyemail XML API services. These controlled write operations require operator-grant authorization to execute, ensuring mutating actions are explicitly permitted.

How does the FastBill API handle authentication for XML requests?

FastBill API authentication is handled securely by injecting Basic auth credentials through the FASTBILL_BASIC_AUTH secret route within the gateway. This gateway-safe pattern means your XML API requests are authenticated automatically without exposing credentials directly in the request payload.

What is the best way to export e-invoice documents like XRechnung or ZUGFeRD from FastBill?

Exporting e-invoice documents such as XRechnung and ZUGFeRD is handled by generating specific XML API requests for e-invoice related services. The Skill parses the returned FastBill XML responses, converting them into structured, usable output for your accounting automation workflows.

Does FastBill API integration support read-only customer and invoice lookups?

FastBill API integration fully supports read-only lookup tasks for querying invoices, customers, and payments. These queries use gateway-safe XML request patterns to retrieve data and parse the XML responses back into structured output without requiring operator-grant permissions.

What are the limitations when converting JSON to FastBill XML for accounting automation?

The primary limitation for accounting automation is that mutating XML API calls are restricted unless operator-grant is provided or a dry-run is used. Additionally, all requests must conform to a service allowlist, meaning only explicitly permitted FastBill services can be executed.