EMAIL · ERP · RULES · ARTIFICIAL INTELLIGENCE

Connect your workflows to DECA.

Turn email, order or delivery data into a DeCA. Combine rules, AI analysis and API calls to match your workflow.

Set up Power AutomateEmail creationAPI documentation
INTEGRATION TESTS

Power Automate

Requests from email workflows and Outlook identifiers. Full storage of long IDs and duplicate protection have been checked.

View setup →
AI + API / MCP

Artificial intelligence

Extract data from messages or attachments, validate it and send JSON to the API. Compatible assistants can also connect through MCP.

Connect an assistant →
HTTP COMPATIBILITY

Other automation tools

Make, n8n and tools that support HTTP requests can use the REST API. Each workflow needs configuration and verification.

Connection options →

From document to DeCA, step by step

Extract the shipper, carrier, date, route and goods. Route missing or conflicting information for review. Store the DeCA identifier returned by the API before archiving the message.

Email or orderRules / AIData validationCreate in DECA

Power Automate setup

  1. Add an HTTP action with method POST and URI https://deca.netsistemas.com/api.php.
  2. Set Content-Type: application/json and X-Api-Key: YOUR_COMPANY_KEY. For a personal key, replace the latter with X-User-Api-Key: YOUR_PERSONAL_KEY.
  3. When using these headers, select None for the action's built-in authentication. Store the key as a workflow secret.
  4. Send a JSON object in the body, without Markdown fences or surrounding text. If an AI step returns text, check it contains only the object before parsing it as JSON.
  5. Check the response and store idDeca. Move the email to CREADOS only after confirming creation; related messages that cannot be completed can go to REVISAR.
Example request body

Replace the placeholders with real values and map a stable email or order identifier. API field names remain in Spanish.

{
  "accion": "crear",
  "origenRegistro": "POWER_AUTOMATE",
  "idExterno": "ID_ESTABLE_DEL_CORREO_O_PEDIDO",
  "fechaTransporte": "2026-09-18",
  "matriculaTractora": "1478-AAA",
  "origen": "BURGOS",
  "destino": "MADRID",
  "cargadorNombre": "EMPRESA CARGADORA DE EJEMPLO",
  "cargadorNif": "NIF_REAL_CARGADOR",
  "cargadorDomicilio": "DOMICILIO_REAL_CARGADOR",
  "transportistaNombre": "TRANSPORTISTA EFECTIVO DE EJEMPLO",
  "transportistaNif": "NIF_REAL_TRANSPORTISTA",
  "lineas": [
    {
      "descripcion": "PINTURA",
      "cantidad": 2,
      "unidad": "palets",
      "pesoKg": 1200
    }
  ]
}

Send the REST API key in its header without a Bearer prefix. The /mcp endpoint uses OAuth and the MCP protocol, with a different setup.

This example contains 2 pallets and 1,200 kg total. Send dates as YYYY-MM-DD. If the carrier is omitted, the API uses the account company's name and tax ID; only rely on this when appropriate. To assign a driver, supply an existing idConductor.

Direct email creation

Watch the explanatory video in YouTube

Company and Agency / Fleet plans can create a DeCA by sending a template to deca@netsistemas.com. The subject is not used: data must be in the message body, either plain text or HTML.

CLAVE DE EMPRESA: YOUR_UNIQUE_KEY
FECHA VIAJE: 19/09/2026
TRANSPORTISTA NOMBRE: PORTES PERICO
TRANSPORTISTA NIF: B11223344
ORIGEN: BURGOS CALLE ZAMORA 19
DESTINO: MADRID CALLE ROMA, 91
MERCANCIA: PINTURA

Dates may also use YYYY-MM-DD or DD-MM-YYYY. Repeat MERCANCIA to create several lines. Optional fields are MATRICULA, MATRICULA REMOLQUE, CHOFER, TELEFONO CHOFER, EMAIL CHOFER, OBSERVACIONES and ID EXTERNO.

If no consignor is supplied, DECA uses the account company's legal name, tax ID and address, provided they are complete. A missing mandatory field or invalid key moves the message to REVISAR and replies to the sender. Created DeCAs move to CREADOS.

The confirmation is sent from deca_noreply@netsistemas.com to the original sender, with a blind copy to the address configured by the company. It includes a direct link and the DeCA QR code. When EMAIL CHOFER is supplied, the driver receives the same confirmation. Automatic messages are identified and never processed again, even if a request is sent from deca@netsistemas.com.

Long identifiers and retries

DeCA documents and multi-stop deliveries accept idExterno of up to 512 characters, without truncation. Send it together with origenRegistro (up to 50). The pair is unique within each company.

Before retrying an uncertain creation response or a 409 error, call GET /api.php?accion=buscar&origen=POWER_AUTOMATE&idExterno=.... URL-encode parameters. Check encontrado, idDeca and the version/PDF for dated trips. Do not change the external ID to force another record.

The 512 limit applies to DeCA documents; master records retain their 80-character limit. Supplementary Unicode characters count as two UTF-16 units in SQL Server.

More ways to automate

Make: use its HTTP module. n8n: use HTTP Request. Set POST, JSON and the appropriate API key header. Compatibility is based on HTTP, and does not mean that all workflows have been tested.

DECA Autoentrada for Windows: email and attachment processing with separate rules and AI settings. Created messages move to CREADOS, those requiring review to REVISAR, and unrelated messages stay in the inbox.

Download Autoentrada (Spanish)MCP

Automation tool documentation: Microsoft HTTP · Make HTTP · n8n HTTP Request.

What has been checked

Power Automate: workflow requests have been received and configuration reviewed. The Outlook identifier, 512-character storage and duplicate rejection have been tested in the DECA database.

AI processing: structured-response validation, incomplete data and message classification have been tested locally. Live provider connections, models and mailbox formats need verification with the customer's credentials.

These checks are not Microsoft certification or a guarantee for every model or automation tool. We can help verify your complete workflow before activation.

Discuss my integration