POP icon

POP

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

Actions9

Invoice → Get Peppol Document

AI-generated

Summary

Retrieves a Peppol document by sending a POST request to the POP API, using the default peppol/document-get endpoint. Choose how to provide the request body: forward incoming JSON, build it from form fields, enter a complete JSON body, or send a raw payload.

Inputs

  • Environment — POP API environment; defaults to Production.
  • Endpoint Path — Relative endpoint path; defaults to peppol/document-get.
  • Input Mode — Select Use Incoming JSON, Form Fields, JSON, or Raw. Incoming JSON forwards the current input item's JSON as the body. Form Fields constructs a body from the fields below.
  • Integration UUID (required) — In Form Fields mode, the UUID of the integration whose document to retrieve.
  • License Key — In Form Fields mode, an optional POP license key. When provided, it is sent in the X-API-Key header and as license_key in the request body; otherwise the configured POP API credential may be used.
  • Target Environment — In Form Fields mode, optionally select Live or Sandbox; the default leaves the API environment unspecified.
  • Zone (Country Code) — In Form Fields mode, an optional country zone. The value is trimmed and converted to uppercase before being added to integration.zone; the UI notes it is required for sending to Peppol for a BE VAT number.
  • JSON Body — In JSON mode, provide the complete request body following the POP API v2 peppol/document-get schema.
  • Raw Body — In Raw mode, provide a raw request payload. The operation defaults the Content-Type to application/xml unless overridden.
  • Extra Headers (JSON) — Optional additional request headers supplied as a JSON object.

Output shape

A single POP API response object per input item, returned as n8n item JSON.

The request uses POST. With multiple input items, the operation makes a request for each item and pairs each result with its input. In Form Fields mode, the body contains license_key, optional environment, and integration with the UUID and optional uppercased zone. JSON and raw modes use the supplied body directly. API errors are raised as node errors unless Continue On Fail is enabled.

Links

Discussion