Connect Hume AI to CII & UBL by InvoiceXML

Both apps 31Hume AI 17CII & UBL by InvoiceXML 14

• Trigger
  Chat ended (instant)

  Fires when an EVI chat session ends (chat_ended webhook event).

• Trigger
  Chat started (instant)

  Fires when a new EVI chat session begins (chat_started webhook event).

• Trigger
  New Voice

  Triggers when a new voice is created.

• Trigger
  Tool call (instant)

  Fires when EVI calls a registered tool during a conversation (tool_call webhook event).

• Action
  Add config

  Create a new EVI configuration (voice assistant setup).

• Action
  Add prompt

  Create a new system prompt for use in an EVI configuration.

• Action
  Add tool

  Create a new tool definition that EVI can call during a conversation.

• Action
  Add voice

  Save a new custom voice to the account from a TTS generation ID, for reuse in later speech requests.

• Action
  Convert voice

  Convert the speech in an uploaded audio file into a different saved voice.

• Action
  Delete config

  Delete an EVI configuration from the account.

• Action
  Delete voice

  Delete a saved custom voice from the account.

• Action
  Generate Text to Speech

  Convert text to speech using Hume AI's expressive text-to-speech technology.

• Action
  List configs

  List the EVI configurations saved to the account.

• Action
  List prompts

  List the prompts saved to the account.

• Action
  List tools

  List the tool definitions saved to the account.

• Action
  List voices

  List the custom voices saved to the account.

• Action
  Update config

  Update an EVI configuration's name or description.

• 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.