Formmy

Add a CRM tag to a conversation. Use to mark categorical attributes the operator should see at a glance: 'VIP', 'lead', 'urgente', 'cotización', etc. label is free-form; color is hex. Optional comment is internal note (not shown to the client). In a WhatsApp conversation you do NOT need conversationId — it is detected automatically.

Add a RAG document/knowledge base entry to a Formmy agent

Send a message to a Formmy agent and get the full response (non-streaming)

Connect an external service (e.g. EasyBits DB) to a Formmy agent. The agent gets tools to interact with the service at chat time.

Create a new Formmy agent/chatbot

Record an order (cotización/pedido) for a conversation in Formmy. THIS IS THE CRM OF RECORD: every quote you send must be registered here, it is not optional. PRIORITY FIELDS you should almost always fill: `notas` (a summary of the order) and `cotizacionUrl` (the quote PDF on EasyBits). It shows in the contact panel's Órdenes accordion, moves the kanban card when `estatus` matches a CRM estado (call list_conversation_estados first), and bumps the conversation to the top. Use when an order/quote is confirmed or its status changes; only the most recent order drives the card and the board value. In a WhatsApp conversation you do NOT need conversationId — it is detected automatically from the current chat.

Delete a RAG document from an agent

Get details of a specific Formmy agent

Get a conversation with its messages

Get a specific RAG document with its full content

List all Formmy agents for the authenticated user

List the valid CRM pipeline stages (kanban columns) configured for this agent. ALWAYS call this before set_order_status so you move orders within the defined set instead of inventing new labels. Returns an array of { label, color }. Pick the closest matching stage and reuse its exact label. In a WhatsApp conversation you do NOT need agentId — the stages are derived from the current chat.

List conversations for a Formmy agent

List all RAG documents for a Formmy agent

List the ORDERS (pedidos/cotizaciones) of THIS conversation, newest first. Call it when the customer has more than one open quote and you need to act on a specific one instead of the latest: it returns each order's `id`, which you pass as `ordenId` to set_order_status or update_order. Also the way to check an order's current stage or lifecycle, since the board itself is not readable. Scoped to the current customer — it never lists other people's orders. In a WhatsApp conversation you do NOT need conversationId.

Remove a CRM tag from a conversation by its label. Case-insensitive match. In a WhatsApp conversation you do NOT need conversationId — it is detected automatically.

Semantic search across an agent's RAG documents

Save the person's fiscal / shipping data on their conversation so the operator sees it in the contact panel: `email`, `rfc` (Mexican tax ID), `razonSocial` (legal business name for invoicing), and a `direccion` (shipping address). Use when the customer gives you any of these — e.g. to bill (facturar) you need rfc + razonSocial, to ship you need direccion. Partial merge: send only the fields you just learned; omitted fields are left untouched. Each `direccion` you send is ADDED to their saved addresses (pass a stable `id` to update an existing one instead of adding a duplicate). In a WhatsApp conversation you do NOT need conversationId — it is detected automatically.

Move an ORDER (pedido) of a conversation to a pipeline stage (kanban column). The board groups orders by their stage (`estatus`). Use it whenever the deal changes column, in EITHER direction: quote sent → 'Cotización enviada', paid by transfer → 'Pago con transferencia', delivered → 'Cerrado', and also when the customer backs out → 'Cancelado'. Call list_conversation_estados first and reuse the exact label. To register a NEW order use create_order (which also sets its stage); when an order is cancelled or delivered, also close its lifecycle with update_order `status`. In a WhatsApp conversation you do NOT need conversationId — it is detected automatically from the current chat.

Share a Formmy agent with another user by email. Creates a permission so they can see and manage the agent.

Update an existing Formmy agent

Update an existing RAG document's title or content

Update an order of this conversation IN PLACE (the most recent one unless you pass `ordenId`) — use it when something about an ALREADY REGISTERED order changes: the customer adds/removes a product, the total changes, the delivery address changes, or you finally got their phone. It is also how you close an order's lifecycle with `status` (CERRADA when delivered/paid, ARCHIVADA when cancelled) so it stops counting as open on the board. Send ONLY the fields that changed (partial patch; omitted fields are left untouched). If you send `productos` without `total`, the total is recomputed from the line subtotals. Do NOT use create_order for a change — that would duplicate the card on the board. To move the order between pipeline stages use set_order_status instead.