Success story — How we helped Synknet cut support tickets by 60%Read more
Communication infrastructure

A messaging API that's simple to integrate, on every channel

Talqui is the messaging infrastructure behind your customer service: official channels, inbox, AI and reports, all ready. You plug your system in through a plugin or the API and it starts talking to your customers.

01 · Ready foundation

Messaging infrastructure, ready to use

Official channels, real-time delivery, an inbox and reports are already live, proven every day in high-volume operations. You connect your system and inherit scale and reliability that would take years to build.

  • Messenger
  • Instagram
  • WhatsApp
  • Webchat
  • iMessage
  • SMS
TalquiTalqui's ready foundation

Messaging infrastructure

Real-time messages, queues and delivery, running around the clock with no servers for you to operate.

Ready on Talqui

Channels

WhatsApp, Instagram, Messenger, Telegram and Webchat with official connections, maintained by Talqui.

Ready on Talqui

Inbox

Queue, transfers, notes and history ready for your team from day one.

Ready on Talqui

Analytics

Reports by channel, agent and AI without building a single dashboard.

Ready on Talqui

Plugins

The only part that is yours: your business rules, wired into everything that is already there.

You write it
  • AgentsIn the inbox, with your widget
  • AI agentsUse your system's actions
  • Your systemGets events in real time
  • Ready to useMessages, queues and delivery running before the first line of code.
  • Channels right awayWhatsApp, Instagram, Webchat and the rest available right away, with no channel-by-channel integration.
  • Your team already workingThe inbox your agents use every day, with your plugin inside it.
  • Numbers from the startReports by channel, agent and AI without building a dashboard.
  • Only your rulesYou write the part that sets your business apart. Talqui maintains the rest.
02 · What you build

Three ways to integrate your system with Talqui

Use one, two or all three. The docs walk you through each step.

  1. 01Build your plugin

    A backend, a screen beside the conversation and a settings page. Use only what you need.

    Read more

  2. 02Receive the events

    Every message, tag and closed conversation reaches your system the moment it happens.

    Read more

  3. 03Give tools to the AI

    Your system's actions become tools the AI agent uses while it serves customers.

    Read more
03 · In practice

Your system's data next to every conversation

Agents don't need another tab to check an order, a contract or an invoice. Your system shows up next to the conversation, already on the right customer, and the action happens right there.

Identify contactsSee right away whether the contact is already in your system, right in the widget, without switching screens.
Run actionsChange things in other systems without switching tabs: update a record, open an order, log a payment.
Send documentsGenerate the invoice copy, contract or receipt in your system and paste the file straight into the reply.
Configure per customerEach company connects its own account of your system on the plugin's settings screen.
How the widget works
04 · Integrations

Ready integrations with CRMs, ERPs and channels

Each one is a plugin built on the same foundation. Admins install, connect and configure it inside Talqui.

See the full catalog
05 · Developers

How to publish a plugin, from clone to catalog

The public boilerplate ships a backend, a widget and settings ready to edit. Once done, the plugin goes through review and enters the install catalog.

  1. 01Clone the boilerplatePublic repository with a Node backend, MCP, widget and settings in Vue.git clone https://github.com/talqui-oss/talqui-plugin-example
  2. 02Run it locallyNode 22 or newer and pnpm. One command starts everything.pnpm install && pnpm dev
  3. 03Ask for credentialsThe team issues your plugin's ID and token.developer@talqui.com
  4. 04Send it for reviewTalqui tests every address, route and tool. It takes 3 to 5 business days.MCP Inspector
  5. 05PublishThe plugin enters the catalog and later versions ship without a new approval.urn:talqui:plugin:<name>

API changelog

  1. Typing indicator for plugins in the Services API.
  2. Campaigns through the API: Talqui as a platform for other software.
  3. Plugins can now connect to the RTM API.
See the changelog
06 · AI agents

Connect your AI agents. They look up conversations, reach resources and build reports right inside Talqui.

Use the assistant your team already has to work with your support data, with no spreadsheet exports and no switching screens.

  • Claude Code
  • Codex
  • Cursor
  • Claude
  • ChatGPT
  • Gemini

FAQ

Questions about plugins and the API

Do I need a developer to use plugins?

Not for the catalog plugins. The account admin installs, connects and configures each one inside Talqui. A developer only comes in when you want to connect a system that doesn't have a plugin yet.

Which systems already have a plugin?

Channels like the official WhatsApp API, Instagram, Messenger, Telegram and WebChat; CRMs like HubSpot, Pipefy and Twenty; ISP systems like IXC, SGP, MK Solutions, Hubsoft and Leaf; plus Calendly, Jira, GLPI and Mercado Livre. The full list is in the integrations catalog.

How does the API authenticate calls?

In three ways: as an agent, with a JWT token; as a plugin, valid for every account that installed it; and as a plugin connection, limited to a single account. Plugin and connection send the ID and token encoded in base64.

Can I use only the API, without the inbox?

Yes. With the API you open conversations, send messages, run campaigns, search contacts and read the history. The inbox stays available for when your team needs to step in.

How does my system learn what happens in conversations?

Through the RTM API, a real-time connection that delivers events like message received, conversation opened or closed, tag added and rating. One plugin follows many customers on the same connection.

What is MCP and where does it show up in Talqui?

MCP (Model Context Protocol) is the open standard that lets AI use tools. Your plugin's tools are available to the AI agent during conversations and in the procedure editor.

Where is the plugin hosted?

On your infrastructure. You publish the backend, the widget and the settings on HTTPS addresses, and they move at your pace, without waiting for a new Talqui release.

Can I publish my plugin in the Talqui catalog?

Yes. Build from the public boilerplate, publish the addresses and send the request to developer@talqui.com. The team reviews and tests every address before releasing the plugin in the catalog, within 3 to 5 business days.

Platform

Everything for support and sales in one place

Plugins connect to every Talqui feature. The same conversations, the same team and the same channels run through the whole platform.