Connect Jitbit Helpdesk to ZUGFeRD & XRechnung by InvoiceXML

Both apps 28Jitbit Helpdesk 20ZUGFeRD & XRechnung by InvoiceXML 8

• Trigger
  New Ticket

  Triggers when a new ticket is created in Jitbit Helpdesk, optionally limited to a category, section, status, submitter, company, technician or tag.

• Action
  Add article

  Creates a new knowledge base article in a category.

• Action
  Add asset

  Creates a new asset in Jitbit Helpdesk with its model, manufacturer, type and supplier.

• Action
  Add company

  Creates a new company in Jitbit Helpdesk, or returns the existing company's id if the name is taken.

• Action
  Add tag to ticket

  Adds a tag to a ticket. The tag is created if it does not already exist.

• Action
  Add time spent

  Logs a time spent entry on a ticket under the connected user. Requires technician permissions.

• Action
  Create New Reply

  Posts a new reply (comment) to an existing helpdesk ticket.

• Action
  Create Ticket

  Creates a new helpdesk ticket in a category, with a subject, body and priority.

• Action
  Create User

  Creates a new helpdesk user. Requires administrator permissions.

• Action
  Find Ticket

  Searches tickets by text, optionally narrowed by submitter, category, status, assignee and creation date, and returns the matching tickets.

• Action
  Find User

  Finds a helpdesk user by their email address and returns their profile.

• Action
  Get Article

  Returns a knowledge base article with its full content, category, tags and attachments.

• Action
  Get ticket

  Returns a helpdesk ticket's details, including its status, category, submitter, assignee, tags, attachments and custom field values.

• Action
  List Companies

  Returns every company in your Jitbit helpdesk with its name, email domain and notes. Requires an administrator account.

• Action
  List Ticket Comments

  Returns all comments (replies) posted on a Jitbit Helpdesk ticket.

• Action
  List tickets

  Returns the helpdesk tickets the connected user can see, optionally filtered by mode, category, status, submitter, company, assignee, tag and dates.

• Action
  List Time Spent Entries

  Returns every time spent entry logged against a ticket, including who logged it, the seconds spent and when. Requires technician permissions.

• Action
  Update company

  Updates a company's name, notes and email domains in Jitbit Helpdesk.

• Action
  Update ticket

  Updates one or more properties of an existing helpdesk ticket, such as its status, priority, category, assignee, due date, tags, subject or body.

• Action
  Update user

  Updates an existing helpdesk user's profile, such as name, email, contact details, company, department, password and account status. Requires administrator permissions.

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

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

• Action
  Create ZUGFeRD Invoice

  Creates a new ZUGFeRD compliant PDF/A-3b invoice from scratch using the provided invoice data.

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

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

• Action
  Transform to ZUGFeRD

  Turns a plain PDF invoice into a ZUGFeRD 2.x hybrid invoice (PDF/A-3 with embedded XML) using AI extraction.

• Action
  Validate XRechnung Invoice

  Validates a CII XML invoice for XRechnung / EN16931 compliance.

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