Actions36
- 📦 Producto Actions
- 📊 Stock Actions
- 📋 Movimiento Actions
- 🛒 Venta Actions
- 📥 Recepción Actions
- 📥 Borrador Recepción (n8n) Actions
- 📝 Borrador (texto) Actions
- 🤖 Propuesta IA Actions
- 🏭 Bodega Actions
- 👤 Cliente Actions
- 📚 Catálogo Actions
- 📰 Reportes (legacy) Actions
📥 Borrador Recepción (n8n) → Confirmar
AI-generatedSummary
Confirms a pending n8n reception draft in the Ditextil inventory system by POSTing to /api/reception-drafts/{id}/confirm, optionally overriding the destination warehouse and recording who confirmed it.
Inputs
- ID Borrador (receptionDraftId) (required) — Numeric ID of the reception draft to confirm. Used in the request path.
- ID Bodega (draftWarehouseId) — Warehouse selected from a dropdown loaded from /api/warehouses. If empty or 0, it is omitted from the request, so the API decides the warehouse (presumably the draft's own).
- Confirmado Por (confirmedBy) — Name recorded as the confirmer. Defaults to 'n8n'. Omitted if blank.
Output shape
The JSON response from the Ditextil API for the confirm call, emitted as one or more n8n items (an array response becomes multiple items) linked to the input item.
The source does not define the response fields. Any API error throws and stops the node unless 'Continue On Fail' is on. In that case an item with an 'error' message is returned instead. The call runs once per input item, so each incoming item confirms a draft. Confirming likely commits the draft as a reception, but the source only shows the API call.
Examples
Example 1: Confirm a draft after a human reviews it, receiving into a specific warehouse.
Resource: Borrador Recepción (n8n); Operation: Confirmar; ID Borrador: {{$json.draft_id}}; ID Bodega: Main warehouse; Confirmado Por: 'approver@company'.
Example 2: Create a draft from a message and confirm it automatically in the same workflow.
Run 'Crear desde Texto', then Confirmar with ID Borrador set to the id from the previous node's output; leave ID Bodega empty; Confirmado Por: 'n8n'.