Conecta Clientus con tus asistentes de IA
MCP permite que un asistente compatible utilice herramientas y datos de Clientus mediante una conexión autorizada. Tú decides qué acceso compartir.
En esta página
Qué puedes hacer con MCP
MCP significa Model Context Protocol. Es una forma común de conectar asistentes con aplicaciones: tú haces una solicitud en el chat y el asistente utiliza las herramientas que Clientus le permite.
Puedes consultar contactos y conversaciones, revisar tareas o ventas y realizar las operaciones disponibles para tus permisos. La conexión no habilita automáticamente todas las funciones de la plataforma.
ChatGPT y Claude tienen instrucciones específicas en la guía. Otros clientes, como Claude Code, pueden utilizar el transporte HTTP y los mecanismos de autenticación compatibles. La disponibilidad también depende del plan y de las políticas de tu asistente.
Conecta tu cuenta, sin crear una clave empresarial
- Abre Mis asistentes de IA y elige el asistente que utilizas.
- Sigue sus instrucciones para agregar Clientus. Cuando el cliente admite OAuth, se abre el inicio de sesión y la autorización en Clientus.
- Selecciona las empresas y los permisos que quieres compartir. Después vuelve a tu asistente para terminar.
- Haz una consulta de lectura e indica la empresa. Revisa tu autorización y su actividad desde la misma página.
Crear una credencial o copiar una dirección no confirma una conexión. Clientus distingue una autorización concedida de una actividad registrada. Si tu cliente no admite OAuth, la guía ofrece una alternativa manual dentro de las opciones avanzadas.
Tus permisos se comprueban en cada operación
- Las conexiones personales pertenecen a tu cuenta. Las nuevas autorizaciones incluyen solo las empresas que seleccionaste; una empresa a la que entres después no se agrega automáticamente.
- Cada operación de negocio se ejecuta en una empresa identificada. Si hay varias y no se puede determinar cuál utilizar, Clientus exige una selección.
- El servidor valida la empresa, tu membresía y tu rol vigente. Los permisos de la conexión no amplían los de tu cuenta. Perder acceso a una empresa también retira ese acceso al asistente.
- Las credenciales antiguas conservan su alcance y aparecen identificadas en el gestor. Revisa sus permisos si quieres reemplazarlas por una selección más limitada.
Cuándo debes aprobar una acción
Los envíos de mensajes, asignaciones y transferencias, así como las operaciones sensibles que lo requieren, preparan una solicitud de aprobación en Clientus. El asistente no puede aprobarla por ti. Algunas tareas reversibles y autocontenidas se ejecutan directamente cuando tienes permisos; no todas las escrituras requieren una confirmación.
La lista de herramientas al final indica la política de aprobación de cada capacidad. También se mantienen los límites de uso y la auditoría de la operación.
Cómo retirar el acceso
En Mi cuenta → Mis asistentes de IA, abre Tus autorizaciones y revoca la autorización OAuth o la credencial manual correspondiente. El servidor vuelve a comprobar su vigencia al utilizarla. Desconecta también Clientus en los ajustes de tu asistente.
Las claves técnicas de una empresa se revocan por separado desde Integraciones → API y desarrolladores. Los agentes IA internos se administran en Configuración → IA; no son conexiones personales externas.
Detalles para desarrolladores
URLs, transporte y credenciales
El servidor utiliza MCP Streamable HTTP. La URL de conexión es:
https://mcp.clientus.ai/mcpLa variante /mcp/w/{workspace} fija una sola empresa. La credencial debe estar autorizada para esa empresa; cambiar el slug o enviar otro identificador no amplía el acceso.
Los clientes con OAuth descubren los metadatos de autorización a partir del desafío WWW-Authenticate. Clientus usa PKCE y consentimiento de empresas y permisos. Los tokens de acceso y las credenciales MCP manuales se envían mediante Authorization: Bearer …; nunca en la URL.
Las claves MCP técnicas se crean en Integraciones y se delegan a un asesor activo de esa empresa. Su alcance combina los permisos elegidos y el rol del asesor. Una clave API empresarial sin acceso MCP no abre este protocolo; una credencial MCP no sustituye a una clave REST.
POST transporta solicitudes JSON-RPC; GET y DELETE conservan las reglas del transporte. Utiliza los encabezados Accept y de versión/sesión exigidos por tu SDK. Un cliente de protocolo recibe respuestas de protocolo o errores estructurados, nunca la guía HTML. Solo la navegación humana se dirige a la guía.
Guarda las credenciales en un almacén de secretos y utiliza los permisos mínimos. Puedes consultar el contrato REST para integraciones de servidor a servidor; no todas las herramientas MCP tienen un equivalente REST publicado.
Herramientas disponibles
Este catálogo se obtiene de las capacidades MCP implementadas. La disponibilidad para tu conexión depende además de tus permisos, empresa y configuración. Las capacidades futuras no aparecen aquí.
Explorar capacidades y aprobaciones (147)
| Herramienta | Capacidad | Aprobación |
|---|---|---|
search_customers | List and filter tenant contacts with stable pagination and sorting. | Sin confirmación adicional |
get_customer | Get the 360-degree customer profile, identities, sales and timeline. | Sin confirmación adicional |
update_customer | Edit a contact's core identity fields (name, phone, email) — manual edits always win over automated writers. | Sin confirmación adicional |
set_customer_relationships | Classify a contact's relationships with the business. Changes which conversations count toward customer-service metrics, so every change is audited. | Sin confirmación adicional |
send_template_to_new_contact | Send an approved WhatsApp template to start or resume contact — someone Clientus does not know yet (met at an expo, a walk-in who asked to be contacted) or an existing customer being reached at their current number after a correction. Finds or creates the contact by phone, routes to an agent/line, sends, and assigns. Human-approved: reviews the exact phone, template and destination before anything is sent. | Requerida |
merge_customers | Merge two customer profiles transactionally with tenant guardrails. | Requerida |
resolve_customer_identity_match | Confirm or dismiss a proposed cross-channel identity match. | Requerida |
list_conversations | List the tenant inbox with ownership, channel and attention filters. | Sin confirmación adicional |
get_next_conversation | Pick the single conversation this person should attend next, in the shared priority order, skipping what someone else already has open and anything assigned to another agent. Returns the conversation and the coded reasons behind its priority. Reads only: it neither assigns nor changes anything. | Sin confirmación adicional |
search_conversations | Search all tenant conversations by customer or message content. | Sin confirmación adicional |
get_conversation | Get a conversation header, its customer/channel context and whether the business can reply right now (reply_capability). | Sin confirmación adicional |
assign_conversation | Assign another agent's conversation or return it to the pool. | Requerida |
transfer_conversation | Transfer an owned conversation or claim an unassigned conversation. | Requerida |
snooze_conversation | Postpone a conversation until a future date, or resume it now. | Sin confirmación adicional |
get_conversation_messages | Page through the messages in one authorized conversation. | Sin confirmación adicional |
search_conversation_messages | Search the complete history of one conversation. | Sin confirmación adicional |
send_message | Send one idempotent plain-text reply through an authorized conversation channel, subject to the channel's reply rules (reply-only channels, reply window and message limit). | Requerida |
list_social_comments | List public social comments grouped by publication and attention state. | Sin confirmación adicional |
get_comment_metrics | Read how many public social comments arrived in a calendar period (workspace timezone), by platform, and how many are still without a reply. Aggregates only: never returns individual comments. | Sin confirmación adicional |
list_agent_presence | List assignable agents with workload, leave and online presence. | Sin confirmación adicional |
search_sales | Find sales and receivables associated with a customer or reference. Legacy ERP ledger; includes native commerce sales through the compatibility projection. Prefer /v1/commerce/* for the canonical model. | Sin confirmación adicional |
search_payments | Find payment receipts and customer payment history. Legacy ERP ledger; includes native commerce payments through the compatibility projection. Prefer /v1/commerce/* for the canonical model. | Sin confirmación adicional |
list_collection_accounts | List receivables, grouped customer debt and proposed reminders. | Sin confirmación adicional |
search_quotes | List customer-facing quotations by number, customer or commercial status. Legacy quotation ledger; sales, payments and balances of the canonical commerce model live under /v1/commerce/*. | Sin confirmación adicional |
list_opportunities | Read the tenant sales pipeline and bounded open opportunity cards. | Sin confirmación adicional |
list_channels | List connected tenant channels and their operational status. | Sin confirmación adicional |
get_link_settings | Tracked-link policy of the workspace: whether links sent in messages are tracked per channel, their lifetime and the domain they go out with (shared, company subdomain or own domain). | Sin confirmación adicional |
update_link_settings | Change the workspace's tracked-link configuration: its subdomain (empresa.clientus.link, related to the company and never another's) and its policy (tracking on/off, per channel, lifetime, which domain links go out with). Supports a dry run that checks everything without writing. | Requerida |
list_customer_calls | List imported Aircall and WhatsApp calls for the tenant. | Sin confirmación adicional |
list_automations | List automation drafts, active versions and status. | Sin confirmación adicional |
pause_automation | Pause an active automation: no new runs start, the published version is kept and live runs finish on their own. Idempotent. | Sin confirmación adicional |
duplicate_automation | Copy an automation's saved graph and run settings into a new draft. Never publishes; identity-bound settings are reset and reported. | Sin confirmación adicional |
create_ad_lead_automation | Create the DRAFT of the curated ads-leads recipe, also used as a topic of attention, from parameters (which ads and, optionally, which words, new chats or Instagram stories also start it; welcome message or quick reply; questions; frequently asked questions and hand-over to a person on request; who receives the person; whether to tell Meta). The server builds the flow with the same builder as the dashboard editor; the caller never sends a graph. Never publishes and sends nothing: a person reviews and publishes it in the dashboard. | Sin confirmación adicional |
get_automation_capabilities | Per connected social account: which comment actions (like, public reply, private reply) and messaging rules an automation can rely on, plus the availability for a selection. | Sin confirmación adicional |
test_automation | Dry-run the saved draft or the active version against a synthetic comment/message: trigger match and why, resolved messages, variant and actions. Sends nothing. | Sin confirmación adicional |
list_automation_runs | List an automation's runs newest first (cursor pagination), without run variables. | Sin confirmación adicional |
get_automation_run | Read one run and its step log: status, handle, error, latency, variant and provider acceptance per step, plus its end-to-end trace (comment → event → message → tracked links → WhatsApp, estimated) — never raw inputs, outputs, variables, link tokens or comment text. | Sin confirmación adicional |
get_automation_diagnostics | Timeline of recent comments for a social automation: event, match, run, steps, provider acceptance and latency per stage. | Sin confirmación adicional |
get_automation_funnel | Conversion funnel of an automation (comments → matched → triggered → message sent → link sent → clicked → sent to WhatsApp → WhatsApp received, the last one estimated), filterable by date, account and post, with per-post stages, health and outcomes explicitly linked to its runs. | Sin confirmación adicional |
list_automation_funnel_items | Drill down one funnel stage: the comments or runs that reached it (or, with missing=true, the ones that stopped at the previous stage), with guard skip reason, message outcome, link, click and WhatsApp times. | Sin confirmación adicional |
get_automation_link_recipients | Who received the tracked links of an automation and who opened them: one row per contact with links sent, human clicks and last click. | Sin confirmación adicional |
list_automation_publications | List recent posts (or live Instagram stories) of one connected account, to scope a comment trigger by publication. | Sin confirmación adicional |
resolve_automation_publication | Resolve a pasted post URL to its account and native post id among the selected connected accounts. The URL is never fetched. | Sin confirmación adicional |
get_response_attribution | Read who answered each conversation turn — human, AI, or automation (Conversation Flow / automation engine / campaign) — and the resulting AI share of total attended volume. | Sin confirmación adicional |
get_conversation_metrics | Read aggregate conversation counts by calendar period (creation date) — total and broken down by channel or by agent, with optional comparison against the previous equivalent period. Read-only aggregates only: never returns individual conversations. | Sin confirmación adicional |
get_attention_counts | Read how much work the inbox queue is holding right now: the four attention buckets (overdue, awaiting, follow-up, backlog) plus the breakdown by commercial tier, under the same channel, agent, lifecycle, unassigned and priority filters as the inbox itself. | Sin confirmación adicional |
list_unattended_leads | Read who is owed a reply right now across every channel, one row per person: inbox threads, social comments and missed calls where the person did something after the last time a team member answered them, oldest wait first, with a summary by age, source and channel. Customer names and message previews are only returned to credentials that can already read them through their own scopes. | Sin confirmación adicional |
list_ai_agents | List the workspace's conversational AI agents with their structured configuration and activation rules, plus the channels a rule can name. | Sin confirmación adicional |
get_ai_agent | Read one conversational AI agent: status, structured configuration (never a raw prompt or a model) and activation rules. | Sin confirmación adicional |
create_ai_agent | Create a conversational AI agent. It is created turned off: it answers nobody until it is activated. | Sin confirmación adicional |
update_ai_agent | Edit a conversational AI agent: name, structured configuration (qualification, follow-up, material) and activation rules. Every change saves a new immutable version and makes it the default; it never rewrites a saved one and never turns the agent on or off. | Requerida |
activate_ai_agent | Turn a conversational AI agent on: it starts answering the people who match its activation rules. | Requerida |
deactivate_ai_agent | Turn a conversational AI agent off. It stops answering; its configuration and rules are kept. | Sin confirmación adicional |
archive_ai_agent | Archive a conversational AI agent. It stops answering and its rules are retired; it cannot be restored. | Requerida |
list_ai_agent_versions | List the immutable versions of a conversational AI agent, newest first: number, name at the time, who saved it, the version it started from and which one is the default. | Sin confirmación adicional |
get_ai_agent_version | Read one immutable version of a conversational AI agent with the configuration and the rules it was saved with. | Sin confirmación adicional |
create_ai_agent_version | Save a new immutable version of a conversational AI agent, starting from its default version or from another one, as the default (new conversations get it) or as a candidate (nothing changes for customers). It never edits a saved version and never turns the agent on or off. | Requerida |
promote_ai_agent_version | Make an existing version of a conversational AI agent its default: new conversations get it from then on, and the ones the agent is already handling keep theirs. It creates no version and edits none. | Requerida |
list_ai_agent_experiments | List the experiments of a conversational AI agent, newest first, with their status, their variants and how many people each variant has been assigned. | Sin confirmación adicional |
get_ai_agent_experiment | Read one experiment of a conversational AI agent: status, variants, people assigned to each one, frozen scope and promoted variant. | Sin confirmación adicional |
create_ai_agent_experiment | Create the draft of an experiment between 2 to 4 versions of a conversational AI agent. A draft assigns nobody until it is started. | Sin confirmación adicional |
update_ai_agent_experiment | Edit the draft of an experiment of a conversational AI agent: its name, its versions or their order. Only while it is a draft. | Sin confirmación adicional |
start_ai_agent_experiment | Start an experiment of a conversational AI agent: from then on the people the agent adopts for the first time are split evenly between its variants. It freezes the agent's default version as the scope. | Requerida |
pause_ai_agent_experiment | Pause a running experiment of a conversational AI agent: it stops assigning new people; the ones already assigned keep their variant. | Sin confirmación adicional |
resume_ai_agent_experiment | Resume a paused experiment of a conversational AI agent: it assigns new people to its variants again, with the same scope it started with. | Requerida |
complete_ai_agent_experiment | Complete an experiment of a conversational AI agent for good, with or without promoting one of its variants as the agent's default version. Nothing is promoted unless a person asks for it. | Requerida |
cancel_ai_agent_experiment | Cancel an unfinished experiment of a conversational AI agent for good, without promoting anything. Its assignments are kept. | Requerida |
promote_ai_agent_experiment_variant | Promote a variant of a completed experiment of a conversational AI agent: it becomes the agent's default version, with the agent's live rules. It is the experiment's own transition, never a separate write. | Requerida |
list_workspaces | List the workspaces (companies) the authenticated credential may operate, with the caller's role in each. | Sin confirmación adicional |
get_company_settings | Read the workspace's company settings: identity (name, slug, country, timezone), the business profile printed on quotes, sales notes and invoices, the document logo, the workspace icon and whether the «Ventas y pagos» module is enabled and decided. | Sin confirmación adicional |
update_business_profile | Edit the business profile printed on documents (trade and legal name, tax id and regime, fiscal address, contact details, payment instructions, quote terms, footer and quote validity). Partial: only the fields sent change and null clears one; expected_version guards against overwriting a concurrent edit. | Requerida |
set_document_logo | Set, replace or remove the logo printed on quotes, sales notes and invoices (separate from the square workspace icon). The image comes from a public https URL or base64 PNG/JPG bytes. | Requerida |
set_sales_module | Turn the «Ventas y pagos» module (quotes, sales, invoices and collections) on or off for the whole workspace and record the company's decision. Turning it off hides it from everyone and keeps every record. | Requerida |
get_setup_progress | How far the workspace's setup is: percent of steps ready, whether it can already serve customers, the steps in order (tell us about your business, channels, authorized replies, first reply from Clientus, team, response times and document data) with their state and their one action, and the step to do next. The same guide an administrator sees in Settings. | Sin confirmación adicional |
update_setup_profile | Answer the setup guide's first step («Cuéntanos de tu negocio»): whether the business works with a team or the owner serves customers alone, and which main channels its customers use. It only tailors the guide (which steps count and which channels it expects); it connects nothing and contacts no one. | Sin confirmación adicional |
list_tasks | List tasks by view (mine or team), due bucket, assignee, contact and type. | Sin confirmación adicional |
get_task | Read one task with its assignee, contact and due information. | Sin confirmación adicional |
create_task | Create a task for a person, optionally anchored to a customer, conversation, deal or sale. | Sin confirmación adicional |
update_task | Edit a task's fields: title, details, type, priority, due date, reminder and anchors. | Sin confirmación adicional |
complete_task | Mark a task as done, optionally with an outcome. | Sin confirmación adicional |
assign_task | Change who is responsible for a task, with an optimistic-concurrency precondition. | Requerida |
reassign_tasks | Move every open task of one person to another (or to the unassigned pool). | Requerida |
search_notes | List or search the team's internal notes about a customer, deal or task. | Sin confirmación adicional |
create_note | Add an internal note anchored to a customer, conversation, deal or task. Customers never see notes. | Sin confirmación adicional |
get_contact_followup | What is pending with a customer: open tasks, next due, recent notes and the active payment commitment. | Sin confirmación adicional |
list_payment_commitments | List payment promises by customer, status and promised date. | Sin confirmación adicional |
create_payment_commitment | Register a customer's promise to pay. Pauses automatic collection reminders until the promised date. | Requerida |
get_ad_performance | Performance of Meta ads in a calendar period (workspace timezone): conversations, people, qualified, handed off, opportunities and sales attributed to the LAST ad touch of each person within an attribution window, by campaign, ad set or ad, plus Meta spend, cost per result and return when Meta Ads is connected. Money stays in its own currency; nothing is ever converted. | Sin confirmación adicional |
list_ad_touchpoints | List the ad clicks that started conversations: when, platform, ad, ad set, campaign, the milestones reached (automation ran, qualified, handed off) and the person and conversation each belongs to. Filter by ad, campaign, person, conversation and period. | Sin confirmación adicional |
list_ad_catalog | Find the campaigns, ad sets and ads of Meta that the workspace knows, by name, with their Meta id (the one an ad trigger uses) and status. q matches part of the name; source seen lists the ads that already brought a conversation, which works without Meta Ads connected. Ids and names only: never the ad account, tokens or people. | Sin confirmación adicional |
get_ad_attention | See which automation (a «topic») attends the people who arrive from each Meta ad in a calendar period: every known ad grouped by the topic that answers it, the ads that brought conversations and no topic attends, the ads two topics both cover (with which one wins and why) and the ads whose campaign or ad set is not known yet. Conversations only: no spend. Ids, names and counts: never people. | Sin confirmación adicional |
list_marketing_leads | List website lead requests (demo booking or WhatsApp callback) with what the person declared, attribution, the latest demo or WhatsApp outcome and whether the team already contacted them. | Sin confirmación adicional |
get_marketing_lead_metrics | Read website lead-capture aggregates for a calendar period (workspace timezone): requests, demos booked and their outcome, WhatsApp callbacks and delivery, contacted, breakdowns by industry, need, campaign and placement, and the distinct-session funnel. Aggregates only. | Sin confirmación adicional |
search_quick_replies | List the quick replies the caller can use or manage, with filters by category, availability, team, owner, status and content type. | Sin confirmación adicional |
get_quick_reply | Read one quick reply with its content blocks, attachments, audience and usage counters. | Sin confirmación adicional |
create_quick_reply | Create a quick reply (content blocks, shortcut, category, availability by team/branch/person). Sellers can only create personal ones. | Sin confirmación adicional |
update_quick_reply | Edit a quick reply's content, shortcut, category, availability or status; also marks it as reviewed. | Sin confirmación adicional |
archive_quick_reply | Archive a quick reply (soft delete; frees its shortcut, keeps its usage history). | Sin confirmación adicional |
get_quick_reply_context | Read-only, cheap, global (no id). Call it BEFORE proposing a new quick reply or asking who should see it: returns the workspace's real categories, real department/branch/team groups (with id and name — never invent one), the single catalog of variable tokens Clientus resolves (with group, label, example and missing-data behaviour — create/update/import accept exactly these tokens), field limits, how many replies already exist, and whether the caller may share (false = only personal replies make sense). | Sin confirmación adicional |
import_quick_replies | Bulk-create quick replies in one call instead of many create_quick_reply calls — the JSON canonical schema, or already-normalized rows from a CSV/XLSX file. dry_run: true classifies and validates every row (new / possible duplicate by name-or-content / exact duplicate by shortcut / invalid) without writing anything — always call it once before committing a file the user has not reviewed. Without dry_run, valid rows are created one by one under the SAME rules as create_quick_reply (a seller can only import personal replies); one bad row never blocks the rest, and every row's outcome comes back individually. A shortcut that already exists is skipped, never overwritten. | Sin confirmación adicional |
export_quick_replies | Export the quick replies the caller can use or manage as the canonical JSON schema — backup, migration, replicating a configuration across workspaces, or reviewing the library offline. Same audience rule as search_quick_replies: exports exactly what that caller could already see. | Sin confirmación adicional |
list_conversation_flows | List the workspace's conversation flows (today: capture WhatsApp from social DMs) with their status, results and template coverage. | Sin confirmación adicional |
get_conversation_flow | Read one conversation flow with its full configuration, results and template coverage. | Sin confirmación adicional |
disable_conversation_flow | Turn a conversation flow off. Live runs finish on their own; no new ones start. | Sin confirmación adicional |
simulate_conversation_flow | Dry-run a conversation flow with sample customer messages: intent, known WhatsApp, phone parsing, routing and template readiness. Sends nothing. | Sin confirmación adicional |
get_whatsapp_template_status | Per-line status of the flow's WhatsApp template (approved / pending / missing) and how many lines can send it. | Sin confirmación adicional |
list_flow_instances | List flow runs (one per source conversation) with state, outcome, routing and handoff. | Sin confirmación adicional |
get_flow_instance | Read one flow run with its step-by-step history. | Sin confirmación adicional |
stop_flow_instance | Stop a live flow run; the customer conversation continues with the team. | Sin confirmación adicional |
take_over_flow_instance | Take control: stop the flow run and pause every automation on its source conversation so a person continues. | Sin confirmación adicional |
list_routing_policies | List the workspace's routing policies: who receives which new customer and from which WhatsApp line. | Sin confirmación adicional |
get_routing_policy | Read one routing policy with its ordered rules and fallback. | Sin confirmación adicional |
simulate_routing | Simulate a routing decision (channel, customer, topic, country, priority) and explain which rule matched and why. Applies nothing. | Sin confirmación adicional |
recommend_agent_for_conversation | Best Agent: recommend who should handle an EXISTING conversation and from which channel, with the same rule-by-rule explanation as simulate_routing. Applies nothing. | Sin confirmación adicional |
commerce_list_connections | List the workspace's commerce connections (native ledger, online stores, ERPs and file imports) with their health and per-resource policy; never credentials. | Sin confirmación adicional |
commerce_get_connection_capabilities | Read one commerce connection with what it can read or write per resource and which system owns each field; never credentials. | Sin confirmación adicional |
commerce_search_customers | Find commerce customers by name, email, phone, tax id or external reference, with their linked contacts, before registering a sale or a payment. | Sin confirmación adicional |
commerce_create_customer | Create a commerce customer (person or company) with its contacts and addresses, idempotently. | Sin confirmación adicional |
commerce_get_customer_commerce_summary | Summarize one customer's purchases, payments, open balance, credit and subscriptions by currency, as of today. | Sin confirmación adicional |
commerce_get_customer_ledger | Page through one customer's chronological ledger of sales, payments, refunds and credits with running balances. | Sin confirmación adicional |
commerce_list_items | List catalog items (products, services and plans) with their price, tax treatment and status. | Sin confirmación adicional |
commerce_get_item | Read one catalog item with its price and tax treatment. | Sin confirmación adicional |
commerce_upsert_item | Create a catalog item (product, service or plan) with its price, idempotently. | Sin confirmación adicional |
commerce_list_orders | List sales orders with status, payment status, totals and balance due, filtered by customer, seller, dates or origin. | Sin confirmación adicional |
commerce_get_order | Read one sales order with its lines, taxes, applied payments, balance due and the actions the caller may take. | Sin confirmación adicional |
commerce_create_order | Register a sale (sales order) with its lines and optional payments in one transaction; balance and payment status are derived. | Sin confirmación adicional |
commerce_cancel_order | Cancel a sales order with a reason; what was paid must be zero or is kept as customer credit. | Requerida |
commerce_invoice_order | Invoice a confirmed native sale in full: the invoice copies its lines and taxes and the balance due, with any down payment, moves to the invoice. Not a CFDI. | Sin confirmación adicional |
commerce_list_quotes | List quotes with their status, validity and totals. A quote is never revenue. | Sin confirmación adicional |
commerce_get_quote | Read one quote with its lines, taxes and the sale it became when accepted. | Sin confirmación adicional |
commerce_create_quote | Create a quote (draft or already sent) with its lines; totals are computed on the server and it never counts as a sale. | Sin confirmación adicional |
commerce_send_quote | Mark a draft quote as sent to the customer (the PDF and the message are sent by the caller). | Sin confirmación adicional |
commerce_accept_quote | Accept a quote: it becomes a confirmed sale with the same lines and prices in one transaction, optionally with a down payment. | Sin confirmación adicional |
commerce_reject_quote | Record that the customer declined a quote, with an optional reason. | Sin confirmación adicional |
commerce_cancel_quote | Withdraw a draft or sent quote (the company cancels it), with an optional reason. | Sin confirmación adicional |
commerce_list_payments | List payments received with their method, status and how they were applied to sales and invoices. | Sin confirmación adicional |
commerce_get_payment | Read one payment with its allocations to sales and invoices. | Sin confirmación adicional |
commerce_register_payment | Register a payment received, applied to open sales or kept as customer credit, idempotently. | Sin confirmación adicional |
commerce_allocate_payment | Apply an existing payment or customer credit to open sales with explicit amounts. | Sin confirmación adicional |
commerce_reverse_payment | Reverse a payment captured by mistake with a reason, releasing what it paid; the original stays in the audit trail. | Requerida |
commerce_register_refund | Register money returned to a customer for a sale or for an overpayment kept as credit. | Requerida |
commerce_get_subscription | Read one subscription with its billing periods and their status. | Sin confirmación adicional |
commerce_create_subscription | Create a subscription or membership with its amount, interval and billing anchor, idempotently. | Sin confirmación adicional |
commerce_cancel_subscription | Cancel a subscription now or at the end of the current period, optionally cancelling its unbilled open periods. | Requerida |
commerce_list_open_balances | List open receivables (sales and invoices with a balance due) with their due dates and days overdue, as of today. | Sin confirmación adicional |
commerce_get_sales_metrics | Sales, collections, refunds, receivables, customers and pipeline metrics for a period, with breakdowns and time series in the workspace base currency. | Sin confirmación adicional |
commerce_bill_subscription_cycle | Register the sale that bills one subscription period, with optional payments, in one transaction. | Sin confirmación adicional |