Integration
Connect Cartes.io to ZUGFeRD & XRechnung by InvoiceXML
When something happens in Cartes.io, your agent does the next thing in ZUGFeRD & XRechnung by InvoiceXML. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Cartes.io and ZUGFeRD & XRechnung by InvoiceXML to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Cartes.io can start in ZUGFeRD & XRechnung by InvoiceXML
When New map in Cartes.io
then Create XRechnung Invoice in ZUGFeRD & XRechnung by InvoiceXML
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Cartes.io and ZUGFeRD & XRechnung by InvoiceXML
Triggers and actions 2 triggers · 18 actions
- New map
Fires when a new map is created.
- New marker
Fires when a new marker is added to a map.
- Add map
Create a new map.
- Find categories
Search for categories matching a query.
- Find maps
Search for maps matching a query.
- Get map
Retrieve a single map by ID.
- Get map static image
Generate a static image snapshot of a map.
- Get marker
Retrieve a single marker by ID.
- List categories
List all available map/marker categories.
- List maps
List all maps.
- List marker locations
List the recorded location history for a marker.
- List markers
List all markers on a map.
- Convert XRechnung to PDF
Renders an XRechnung invoice XML file (UBL or CII syntax) into a readable PDF preview. The PDF is for human reading only and has no legal standing.
- Create XRechnung Invoice
Generates a validated XRechnung 3.0 e-invoice (UBL by default, or CII) from structured invoice data and returns the XML document. Totals and the VAT breakdown are calculated from the lines unless supplied.
- Create ZUGFeRD Invoice
Creates a new ZUGFeRD compliant PDF/A-3b invoice from scratch using the provided invoice data.
- Extract Invoice JSON
Reads a structured e-invoice (a Factur-X / ZUGFeRD / Peppol PDF with embedded CII or UBL XML, or a standalone CII or UBL XML file) and returns its data as structured JSON. Pure XML parsing, no AI.
- Extract Invoice XML
Pulls the embedded XML invoice out of a hybrid PDF (ZUGFeRD, Factur-X or other PDF/A-3 invoice) and returns it unchanged.
- Transform to ZUGFeRD
Turns a plain PDF invoice into a ZUGFeRD 2.x hybrid invoice (PDF/A-3 with embedded XML) using AI extraction.
- Validate XRechnung Invoice
Validates a CII XML invoice for XRechnung / EN16931 compliance.
- Validate ZUGFeRD Invoice
Validates a ZUGFeRD 2.x hybrid PDF invoice against the official schema and EN 16931 business rules for the profile it declares, and returns whether it is compliant along with any errors and warnings.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Cartes.io
Cartes.io to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Cartes.io to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Cartes.io to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Cartes.io to Google SheetsGoogle Sheets
Cartes.io to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Cartes.io to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into ZUGFeRD & XRechnung by InvoiceXML
Questions
Cartes.io and ZUGFeRD & XRechnung by InvoiceXML, answered
What can start an automation from Cartes.io?
Any of Cartes.io's 2 triggers in the catalog, including New map and New marker. Describe the moment in plain language and your agent picks the right one.
What can your agent do in ZUGFeRD & XRechnung by InvoiceXML when something happens in Cartes.io?
Any of ZUGFeRD & XRechnung by InvoiceXML's 8 actions, including Create XRechnung Invoice, Create ZUGFeRD Invoice, Convert XRechnung to PDF and Extract Invoice JSON. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from ZUGFeRD & XRechnung by InvoiceXML to Cartes.io?
ZUGFeRD & XRechnung by InvoiceXML has no triggers in the catalog today, so automations start in Cartes.io. If you need the other direction, ask: your agent reads ZUGFeRD & XRechnung by InvoiceXML's API documentation and adds it.
Do I have to build a connector for Cartes.io or ZUGFeRD & XRechnung by InvoiceXML?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.