cucuAdministrar

Description

Manages your company in CUCU: list and create branches, list and create points of sale (registered with the SIAT), mark them configured, import the points of sale that already exist in the SIAT, and see the digital certificate status and expiry. Uploading the certificate and its private key is done from the CUCU panel, not from a workflow.

Part of the Bolivia Fiscal Hub as an alternative to connecting directly to SIAT: CUCU is an authorised provider handling signing, CUIS/CUFD codes and submission to the SIN. Node: “Sucursales, puntos de venta y certificado”.

Configuration

Field	Type	Required	Description
credentials_id	credentials	Yes	cucu credential
operation	select	No	Operation — list_branches, create_branch, list_pos, create_pos, configure_pos, sync_pos, certificate_status
company_id	text	No	Company ID (UUID) — Empty = the credential one
branch_id	text	No	Branch ID (UUID)
pos_id	text	No	Point of sale (UUID) — Empty = the credential default point of sale
name	text	No	Name
address	text	No	Address
siat_code	number	No	SIAT branch code — Empty = the next available
city	text	No	City
municipality	text	No	Municipality
phone	text	No	Phone
email	text	No	Email
description	text	No	Point of sale description
siat_type_pos	number	No	SIAT point of sale type — Empty = 5 (CUCU default)
online	select	No	Operates online — “, true, false
output_key	text	No	Output key — The result is added to data[key] keeping the rest of the data

Credentials

This module requires a credential of type cucu with the fields:

• API key: starts with sk_test_ (sandbox) or sk_live_ (production); the environment is inferred from the prefix
• Environment: automatic, testing or production (if it contradicts the key, nothing is sent)
• Default point of sale (UUID): used when the node does not specify one
• Company ID (UUID): for branches and certificate status
• Webhook secret (whsec_…): to verify event signatures

Output

{
  "operation": "certificate_status",
  "data": {
    "hasCertificate": true,
    "certificateValid": true
  }
}

The output is stored under the configured key (output_key, default cucu) and the rest of data is kept. On error: error.message, error.type and, where applicable, status, code and siat_code.

Usage Example

{
  "credentials_id": "cred-cucu",
  "operation": "list_branches"
}

Notes

• Branches, points of sale and the company certificate status (needs company_id in the credential).
• Uploading the certificate and private key is intentionally NOT in the node, so they never pass through workflow traces. Do it from the CUCU panel.

Related Nodes

• cucuCufd - CUFD del punto de venta
• cucuContingencia - Contingencia (SIAT caído)