Integration · Sell and serve
Keybe and Meteor AI agents
Connect Keybe to Meteor to inspect chats, webhooks, CRM, tasks and automations, and send messages or templates with explicit confirmation.
How does Keybe connect to Meteor?
Meteor connects to Keybe so your AI agent can validate credentials, inspect and configure Smart Chat webhooks, list or retrieve conversations, transfer or close rooms, work with contacts, add notes, create tasks and trigger automations. External writes are guarded by idempotency, and message/template sending requires explicit confirmation.
Where it applies: Colombia, Latinoamérica. Keybe is used as a conversations, CRM/CDP and automation platform. Documented public routes are called directly; account-specific private routes are configured per tool.
What it automates
What a Meteor Met does with Keybe
Human handoff with context
The agent summarizes the customer, phone, reason and conversation before creating a task, triggering a flow or sending an internal template.
Keep Smart Chat synchronized with Meteor
Keybe webhooks notify Meteor about new or updated messages so automations can run.
Review history before answering
The agent can inspect bounded room history before escalating, closing or creating a task.
Trigger journeys from commercial conditions
Meteor can trigger a Keybe flow for hot leads, human support requests, abandoned carts or post-sale follow-up.
35 tools
Everything your Met can ask Keybe for
Each one is a real action in the connector. You can switch off the ones you would rather it never used.
| Tool | What it does |
|---|---|
keybe_consultar_conexion | Checks configured credentials and base URLs without exposing secrets. |
keybe_diagnosticar_crm_configuracion | Audits token, webhooks, agents, inboxes, groups, fields, flows, tasks and response times. |
keybe_validar_token | Validates the Bearer token against Keybe Auth. |
keybe_consultar_webhook | Reads configured Smart Chat webhooks for the appUUID. |
keybe_configurar_webhook | Creates Smart Chat webhook settings. |
keybe_actualizar_webhook | Updates Smart Chat webhook settings. |
keybe_listar_conversaciones | Lists Smart Chat rooms with filters and pagination. |
keybe_consultar_conversacion | Retrieves a room by roomId. |
keybe_transferir_conversacion | Transfers a room to another agent or inbox with idempotency. |
keybe_cerrar_conversacion | Closes a room with an audited reason. |
keybe_listar_agentes | Lists Keybe agents through a configured endpoint. |
keybe_listar_canales | Lists connected channels through a configured endpoint. |
keybe_listar_inboxes | Lists Smart Chat inboxes through a configured endpoint. |
keybe_listar_spaces | Lists spaces through a configured endpoint. |
keybe_listar_filtros | Lists conversation filters through a configured endpoint. |
keybe_listar_grupos | Lists support groups through a configured endpoint. |
keybe_consultar_mensajes | Reads room messages with bounded history. |
keybe_enviar_mensaje | Sends a message only with endpoint, idempotency and confirmation. |
keybe_enviar_plantilla | Sends a WhatsApp template only with endpoint, idempotency and confirmation. |
keybe_buscar_contactos | Searches contacts by phone, email, name or document. |
keybe_consultar_contacto | Retrieves a contact by id, phone or email. |
keybe_listar_campos_contacto | Lists contact fields to map commercial context from SIESA. |
keybe_actualizar_contacto | Updates a contact with idempotency. |
keybe_registrar_contexto_recompra_contacto | Saves SIESA repurchase context on the contact. |
keybe_crear_contacto | Creates a contact with idempotency. |
keybe_agregar_nota_contacto | Adds an internal contact note. |
keybe_listar_actividades | Lists activities or timeline events. |
keybe_medir_tiempos_respuesta | Measures human response times by agent, inbox, contact or room. |
keybe_listar_flows | Lists available Keybe automations. |
keybe_disparar_flow | Triggers an automation with payload and idempotency. |
keybe_consultar_estado_flow | Checks the status of a flow execution. |
keybe_listar_tareas | Lists tasks by contact, agent, status or dates. |
keybe_crear_tarea | Creates a task with idempotency. |
keybe_actualizar_tarea | Updates a task with idempotency. |
keybe_enrutar_a_vendedora_virtual | Transfers a room and leaves operational context for a virtual seller. |
The limits
What the Keybe integration does NOT do
We would rather say it here than have you find out during rollout.
-
It does not invent private Keybe endpoints; private or undocumented routes must be configured.
-
It does not send messages or templates without idempotency and explicit confirmation.
-
It does not expose tokens, private headers or complete raw payloads.
Before you start
What you need to connect Keybe
- 1
Keybe Bearer token
Provided by Keybe or generated from the account with the required permissions.
- 2
Keybe appUUID
Retrieved from the Keybe app/account that will receive operations.
- 3
Default user, agent and inbox ids
Configured for room listing, transfers and closes.
- 4
Additional per-tool endpoints
Added as JSON when the account uses private or undocumented routes.
Frequently asked questions
Questions about Keybe and Meteor
Yes, when the account's sending endpoint is configured and the operation includes idempotency and explicit confirmation.
Yes. The transfer uses Smart Chat room endpoints and requires idempotency to avoid duplicate handoffs.
The tool fails closed and explains which endpoint must be configured. Meteor does not guess third-party routes.
Sell and serve
Other integrations in the same family
Want to see a Met running Keybe?
We will show you with your own account connected, not with a canned demo.