Short answer: Drop the "Xero → Create Invoice" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Contact ID contactId | string | Required | Contact ID |
Line Item Description description | string | Required | Line Item Description |
Quantity quantity | number | Required | Quantity |
Unit Amount unitAmount | number | Required | Unit Amount |
Due Date dueDate | date | Required | Due Date. (date/time) |
{"contactId": "{{trigger.contactId}}","description": "{{trigger.description}}","quantity": "{{trigger.quantity}}","unitAmount": "{{trigger.unitAmount}}","dueDate": "{{trigger.dueDate}}"}
{"Invoices": [{"Total": 100,"Status": "DRAFT","InvoiceID": "inv123","InvoiceNumber": "INV-0001"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.