Skip to main content
Glama

update_whatsapp_workflow

Modify existing WhatsApp workflows: update conditions, keywords, actions, or toggle status. Partial updates preserve unchanged fields; requires workflow ID.

Instructions

Editar workflow de WhatsApp — Modifica un workflow existente (cambiar condiciones, añadir/quitar palabras clave, editar acciones, renombrar, activar/desactivar). Soporta update parcial: solo se sobreescriben los campos que se envian, los demas se mantienen sin cambios. IMPORTANTE: el parametro 'id' es OBLIGATORIO y debe ser el ID numerico del workflow (obtenido de list_whatsapp_workflows). Si el usuario dice 'ajustalo', 'yes apply', 'hazlo' u otra respuesta de seguimiento, DEBES recordar el workflow_id del contexto previo de la conversacion y enviarlo. NUNCA enviar esta accion sin 'id'. Para cambiar solo el mensaje de una accion: SIEMPRE leer primero con list_whatsapp_workflows, copiar el array de actions completo preservando TODOS los valores originales (especialmente delay seconds), y enviar el array modificado. Si solo cambias name, conditions o status, NO envies 'actions' — se preservan automaticamente. [mutation]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID numerico del workflow a editar. OBLIGATORIO siempre. Obtenerlo de list_whatsapp_workflows. Sin este parametro la peticion se trata como creacion y fallara si falta el nombre.
nameNoNombre del workflow (max 100 caracteres). Si no se envia, se mantiene el nombre actual
trigger_typeNoTipo de trigger: 'message.received' o 'message.sent'. Si no se envia, se mantiene el valor actualmessage.received
conditionsNoObjeto con 'logic' (AND/OR) y 'rules' (array de condiciones). Si no se envia, se mantienen las condiciones actuales
actionsNoArray de acciones a ejecutar. Si no se envia, se mantienen las acciones actuales. IMPORTANTE: si envias este campo, debes enviar el array COMPLETO de acciones (no solo la que cambias). Para editar solo el mensaje de una accion reply/reply_with_ai: 1) llama list_whatsapp_workflows para obtener las acciones actuales, 2) modifica solo el campo que necesitas, 3) envia el array completo con todos los valores existentes preservados. Tipos soportados: reply_with_ai (con pre_send_check opcional), reply (con no_repeat opcional), delay (seconds: 1-300, OBLIGATORIO), ai_filter (filtro IA que decide si responder, previene bucles, ideal como primera accion). Para ai_filter se puede añadir prompt:'instrucciones' para personalizar criterios. VALIDACION: cada accion delay DEBE tener 'seconds' entre 1 y 300. Si copias un delay existente, manten su valor original de seconds.
session_idNoID de la sesion de WhatsApp a la que asignar este workflow. null = todos los numeros. Usa get_whatsapp_status para ver las sesiones.
statusNoEstado del workflow: 'enabled' para activar, 'disabled' para desactivar
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It discloses partial update behavior, the need to copy full actions array when editing a message, and validation rules for delay seconds. Ends with '[mutation]' to explicitly indicate mutation. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections and front-loaded purpose. However, it is verbose with repeated warnings and somewhat lengthy, which could be more concise without losing key information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description is highly complete: covers id requirement, partial update, actions handling, validation, and special instructions for ai_filter. Given the tool's complexity (7 params, nested objects), it provides sufficient context for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant meaning: explains the id's critical role and how to obtain it, details each action type (reply_with_ai, delay, ai_filter), provides validation rules, and emphasizes partial update semantics. Much more than schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Modifica un workflow existente' with specific actions like changing conditions, keywords, actions, renaming, activating/deactivating. It distinguishes from siblings like create_whatsapp_workflow by requiring an id.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance for follow-up responses, warns never to send without id, and gives detailed instructions for updating actions vs other fields. However, it doesn't explicitly mention when not to use this tool compared to alternatives like delete_whatsapp_workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wazionapps/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server