POP icon

POP

Interact with POP Cloud API (v2) for e-invoicing (SdI and Peppol)

Actions9

Invoice → Create ZUGFeRD Invoice

AI-generated

Summary

Create a ZUGFeRD or Factur-X invoice package by sending a POST request to the POP Cloud API. Supply the request as incoming JSON, form fields that the node maps into the POP invoice schema, a JSON body, or a raw body; the default endpoint path is create-zugferd.

Inputs

  • Environment and endpoint — The API environment defaults to Production. The endpoint path defaults to create-zugferd and can be changed.
  • Input Mode — Choose incoming JSON (the current input item's JSON is sent as-is), Form Fields, JSON (a complete POP request body), or Raw (the body is sent without JSON encoding). Defaults to incoming JSON.
  • Form fields — In Form Fields mode, provide the required invoice/order ID, filename, customer type, invoice number, invoice date, and total including taxes. Optional collections describe the transmitter, sender, recipient, invoice metadata, line items, payment terms, bank details, and additional invoice settings. Line item description is required; if a line item discount is enabled, its discount percentage is required. Bank details are required when the payment method is Bank Transfer.
  • License Key — In Form Fields mode, an optional POP license key. When supplied, it is sent in the X-API-Key header; otherwise the node can use the configured POP API credential.
  • Target Environment — In Form Fields mode, optionally select Live or Sandbox; leaving it empty uses the API default.
  • JSON Body — In JSON mode, provide the complete request body following the POP API ZUGFeRD schema.
  • Raw Body — In Raw mode, provide the request body as text. The node defaults Content-Type to application/json unless overridden.
  • Extra Headers (JSON) — Optional additional HTTP headers, accepted in any input mode.

Output shape

A single item containing the POP API response for each input item.

The node makes one POST request per input item. In passthrough mode it sends that item's JSON unchanged; in form mode it builds the POP request body, including calculated line-item totals and discounts. Errors are raised as API errors unless the workflow is configured to continue on fail.

Links

Discussion