Connect Orderspace to CII & UBL by InvoiceXML

Both apps 43Orderspace 29CII & UBL by InvoiceXML 14

• Trigger
  New Customer

  Triggers when a new customer is created in Orderspace.

• Trigger
  New Dispatch

  Triggers when items on an Orderspace order are dispatched.

• Trigger
  New Invoice

  Triggers when an invoice is created in Orderspace.

• Trigger
  New Order

  Triggers when a new order is placed in Orderspace.

• Trigger
  New Payment

  Triggers when a payment is made or recorded on an Orderspace invoice.

• Trigger
  New Product

  Triggers when a new product is created in Orderspace.

• Trigger
  Updated Customer

  Triggers when a customer is updated in Orderspace, returning the customer record with the updates applied.

• Trigger
  Updated Inventory Level

  Triggers when the stock on hand or available quantity of a product variant changes in Orderspace.

• Trigger
  Updated Order

  Triggered when an order is changed. Watches the 200 most recently created orders.

• Trigger
  Updated Product

  Triggers when a product is updated in Orderspace, returning the product with the updates applied.

• Action
  Add invoice

  Creates an invoice in Orderspace for one or more of a customer's orders.

• Action
  Add product

  Creates a new product with its variants, prices and categories in Orderspace.

• Action
  Create Customer

  Creates a new customer (a company that places orders) in Orderspace, with its buyer login, contact emails and address.

• Action
  Create Dispatch

  Creates a dispatch for an order, marking the given items as shipped and reducing stock on hand. The order becomes fulfilled once all its items are dispatched.

• Action
  Create Order

  Creates an order for an existing customer, with product, custom and shipping lines.

• Action
  Delete customer

  Deletes a customer from your Orderspace site.

• Action
  Delete order

  Deletes an order in Orderspace.

• Action
  Delete product

  Deletes a product (and its variants) from your Orderspace catalog.

• Action
  Get customer

  Returns a single Orderspace customer by its ID, including buyers, addresses, email addresses and assigned price list, payment terms and customer group.

• Action
  Get dispatch

  Returns a single dispatch (the fulfilled items of an order) by its ID, including shipping address and dispatch lines.

• Action
  Get invoice

  Returns a single invoice by its ID, including its lines, orders, billing address and payments.

• Action
  Get order

  Returns a single Orderspace order by its ID, including customer details, addresses, order lines and totals.

• Action
  Get product

  Returns a single product by its ID, including its variants, prices, categories and images.

• Action
  List customers

  Returns a list of customers, most recently created first, optionally filtered by company name, buyer email, status, reference, payment terms, group or price list.

• Action
  List inventory levels

  Returns stock levels (on hand and available quantities) for product variants, optionally filtered by product, SKU, or created/updated date.

• Action
  List orders

  Returns orders from your Orderspace site, most recently created first, optionally filtered by date, number, status, reference, customer or standing order.

• Action
  Update customer

  Updates an existing Orderspace customer. Fields left blank keep their current values.

• Action
  Update Inventory Level

  Sets the on-hand or available stock quantity for a product variant, identified by its SKU.

• Action
  Update product

  Updates an existing product in Orderspace, including its details, variants, categories and images. Fields left blank stay unchanged.

• Action
  Convert CII to UBL

  Translates a UN/CEFACT CII invoice XML into a standards-compliant UBL 2.1 XML document, enabling interoperability between systems that use different e-invoice formats.

• Action
  Convert UBL to CII

  Transforms a UBL 2.1 invoice XML into a UN/CEFACT CII XML document, bridging compatibility between PEPPOL-based systems and CII-native accounting platforms.

• Action
  Create CII Invoice

  Produces a UN/CEFACT Cross-Industry Invoice (CII) XML document from structured billing data, ready for submission through any EN16931-compliant e-invoicing channel.

• Action
  Create UBL Invoice

  Generates a standards-compliant UBL 2.1 XML invoice from structured billing data including seller, buyer, line items, and payment details.

• Action
  Extract Invoice Attachments

  Download an e-invoice's embedded attachments as a ZIP.

• Action
  Extract Invoice JSON

  Parses a PDF invoice into machine-readable JSON, reading embedded CII or UBL XML when available and applying AI-based extraction as a fallback for unstructured PDFs.

• Action
  Extract Invoice XML

  Pull the CII or UBL XML out of an e-invoice PDF.

• Action
  Parse Invoice JSON

  AI-parse any PDF invoice — messy, scanned, or handwritten — into structured JSON.

• Action
  Render CII to PDF

  Produce a human-readable PDF from a CII e-invoice.

• Action
  Render UBL to PDF

  Produce a human-readable PDF from a UBL e-invoice.

• Action
  Transform PDF to CII

  Reads an existing PDF invoice and produces a UN/CEFACT CII XML document using AI-powered data extraction. Ideal for digitising paper-based or scanned invoices into a structured CII format. Note: AI can make mistakes; review output before sending.

• Action
  Transform PDF to UBL

  Reads an existing PDF invoice and produces a UBL 2.1 XML document using AI-powered data extraction. Useful for onboarding legacy invoices into structured e-invoicing workflows. Note: AI can make mistakes; review output before sending.

• Action
  Validate CII Invoice

  Verifies a UN/CEFACT CII invoice XML against EN16931 semantic rules and XSD schema, returning a detailed compliance report including any rule failures or data inconsistencies.

• Action
  Validate UBL Invoice

  Checks a UBL 2.1 invoice XML against EN16931 business rules and schema constraints, returning a structured validation report with any rule violations or structural errors.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.