DgiEnviarReceptor

Description

Sends an already-issued Comprobante Fiscal Electronico (CFE) to its recipient. The node wraps it in a signed envelope (with a header identifying issuer and recipient), digitally signs it and POSTs it to the recipient’s SOAP endpoint over mutual TLS (the credential’s certificate is also used for the connection). It then processes the returned acknowledgment and updates the CFE status (sent, accepted or rejected).

The CFE to send can be identified by type, series and number (the node retrieves the signed XML stored when it was issued) or the signed XML can be passed directly in the input, for example chained from DgiEmitirCFE.

Configuration

Field	Type	Required	Description
credentials_id	credentials	Yes	dgi credential
receptor_url	text	Yes	Recipient’s SOAP endpoint (per-recipient, each client has its own)
tipo_cfe	text	No	Type of the CFE to send (to fetch it from the database)
serie	text	No	Series of the CFE to send
numero	text	No	Number of the CFE to send
rut_receptor	text	No	Recipient RUT (for the envelope header)
soap12	boolean	No	Use SOAP 1.2 instead of 1.1 (depending on what the recipient exposes)

Either tipo_cfe + serie + numero must be provided, or the signed XML must be passed in the node’s input; if the signed CFE cannot be found, the node returns an error.

Credentials

This module requires a dgi credential type with the following fields:

• Certificate (.p12): advanced signature certificate in base64 (also used for mutual TLS)
• Certificate password: password for the .p12 file
• RUT: issuer’s tax ID
• Environment: test (homologation) or prod (production)

Output

{
  "enviado": true,
  "aceptado": true,
  "estado": "acked",
  "codigo": "00",
  "glosa": "Comprobante aceptado",
  "tipoCfe": 111,
  "serie": "A",
  "numero": 159
}

Usage Example

{
  "credentials_id": "cred-dgi-prod",
  "receptor_url": "https://receptor.example.com/wsefactura",
  "tipo_cfe": "111",
  "serie": "A",
  "numero": "159",
  "rut_receptor": "212345670010"
}

Notes

• If the recipient returns a SOAP Fault, the node treats it as an error and does not mark the document as sent.
• The CFE status is recorded as acked when the recipient confirms receipt, or sent if it was sent but no acknowledgment has arrived yet.
• The connection to the recipient’s endpoint uses the same .p12 certificate from the credential for mutual TLS, not a separate certificate.
• Each recipient may have its own SOAP endpoint; it is best to resolve receptor_url dynamically per client within the workflow (e.g. from a CRM or database).

Related Nodes

• DgiEmitirCFE - Issue the CFE before sending it
• DgiReporteDiario - Report the CFE to the DGI
• DgiConsultarCFE - Check the status of a CFE