POPInstall

Summary

Fetches invoice document notifications and status by sending a POST request to POP’s document-notifications endpoint. Choose how to provide the request body; with Form Fields, supply the integration UUID and optionally a license key and target environment.

Inputs

• Environment — Selects the POP API environment; defaults to Production.
• Endpoint Path — Relative API path; defaults to sdi/document-notifications.
• Input Mode — Choose incoming JSON, Form Fields, a complete JSON body, or a raw body. Incoming JSON is posted as-is; Form Fields builds a body containing integration.uuid and optional environment and license_key.
• Integration UUID (required) — UUID of the integration whose status to retrieve. Used in Form Fields mode.
• License Key — Optional POP license key for Form Fields mode. When provided, it is sent as X-API-Key and license_key; otherwise the configured POP API credential may be used.
• Target Environment — Optional Live or Sandbox target for Form Fields mode; omitted when Default is selected.
• JSON Body — Complete request body for JSON mode; must follow the POP API v2 document-notifications schema.
• Raw Body — Request payload sent as raw text in Raw mode. The node defaults Content-Type to application/xml unless overridden by Extra Headers.
• Extra Headers (JSON) — Optional additional request headers as a JSON object.

Output shape

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

The operation posts one request per incoming item. The response is returned through the shared POP request helper; API or request errors are surfaced as node errors, or as error output items when Continue On Fail is enabled.

Links

• n8n community nodes installation guide