For Ecommerce
Plugins & Connectors
Take your agent to where your customers already are. Daguito integrates with the most popular ecommerce platforms and routes inbound messages from each channel to the flow you choose. Install a plugin, connect your API key, and start chatting.
Every integration ends up routing messages to a flow. The plugin or connector is just the entry point: the logic lives in your flows and knowledge bases, and the same configuration works across every channel.
Ecommerce integrations
Daguito offers native integrations for the three most common store platforms in Latin America and worldwide. Each one embeds the same chat widget and syncs your product catalog so the agent answers with real data from your store.
WordPress & WooCommerce
The daguito-chat plugin embeds the agent on your WordPress site and, if you use WooCommerce, syncs your products into the agent's knowledge base.
During installation, the plugin provisions a WordPress channel with one or two agent flows (a general assistant and, if you have WooCommerce, a sales assistant). Your WooCommerce products are imported in the background with async queues, without blocking the admin.
Installation
1. Sube el plugin a /wp-content/plugins/daguito-chat/
2. Actívalo desde el menú Plugins
3. Ve a Ajustes > Daguito Chat
4. Pega tu API key de daguito.com
5. Listo Requires WordPress 6.0 or later and PHP 7.4 or later. The connection uses WordPress application passwords for OAuth.
Three ways to embed the widget
- Floating widget — auto-injected in the footer of every page across the site.
[daguito-chat]shortcode — drop it into any page or post.- Gutenberg block — to insert it from the template editor.
The shortcode accepts an optional flow parameter to force a specific flow on that page instead of the channel's default flow:
[daguito-chat]
[daguito-chat flow="flow_xxxxx"] Shopify
The Daguito app for Shopify installs via OAuth 2.0. When you accept the permissions, Daguito automatically provisions an agent flow bound to the widget channel and injects the widget script into your store.
The widget ships as a Theme App Extension (TAE) that shows up in the theme editor. The merchant enables or disables it from Customize → App embeds, no code required.
Requested permissions
In production the app requests four scopes. The first two are required to inject the widget and read your catalog; the theme scopes let it manage the Theme App Extension:
scopes = "write_script_tags,read_products,read_themes,write_themes" The Shopify app is NOT embedded: it does not appear inside the Shopify admin. All configuration happens server-side after the merchant accepts the permissions during OAuth.
Tiendanube & Nuvemshop
The Tiendanube integration (Nuvemshop in Brazil) is server-side only: there is no plugin artifact to download. After OAuth, Daguito injects the widget into your store using Tiendanube's Scripts API.
The integration is GDPR and LGPD compliant: it handles store redaction, customer erasure, and data request webhooks.
Tiendanube sends all of its events (install, uninstall, suspend, and privacy events) to a single multiplexed endpoint, indicating the event type in the x-linkedstore-event header.
Widget injection requires manually uploading the tnb-shim.js file to the Partners Portal with the “Automatic install” option enabled. This step is not automated via CLI or GitHub Actions.
The web widget
The widget is a React-based chat component loaded cross-origin from widget.daguito.com. It is the same embed for every platform: WordPress, Shopify, and Tiendanube all share the exact same widget.
Reusing a single widget means every improvement reaches all stores at once, with no per-plugin update.
What the widget does
- API key resolution — discovers the store's key automatically on load.
- Cart sync — a bridge with Shopify keeps the cart current throughout the conversation (more platforms coming).
- Structured search — queries your catalog and returns products inside the chat.
- Responsive design — mobile-optimized out of the box.
Widget API
The widget authenticates with an api_key (not a JWT). Under the /api/widget prefix it exposes the public endpoints that drive the conversation:
POST /api/widget/init # arranca la sesión y devuelve la config de render
POST /api/widget/message # envía un mensaje del visitante
POST /api/widget/cart/sync # sincroniza el carrito (Shopify hoy)
GET /api/widget/history/:session_id # recupera el historial de la conversación
POST /api/widget/form-response # devuelve la respuesta de un formulario Native channel connectors
Beyond stores, Daguito receives messages over several channels and routes them to the configured flow. Every inbound channel uses the same ingest pipeline: persist the message, coalesce it, and run the flow.
Widget
The widget channel covers chat on your landing page and the ecommerce integration. It is the default channel provisioned when you install the Shopify or Tiendanube app.
WhatsApp Business API
The WhatsApp connector receives messages through Meta's Graph API webhook and verifies every event before processing it. Routing an inbound message to a flow is still in progress: today the webhook validates, logs, and normalizes the message, but channel-to-flow resolution is still being wired up.
It handles text, image, audio, video, documents, location, and interactive replies (lists and buttons). It needs three environment variables:
# Variables de entorno requeridas
WHATSAPP_VERIFY_TOKEN # cadena que defines en el panel de Meta
WHATSAPP_ACCESS_TOKEN # token del usuario de sistema, para enviar respuestas
WHATSAPP_APP_SECRET # App Secret de Meta, para verificar X-Hub-Signature-256 Every inbound webhook is verified with the X-Hub-Signature-256 signature (HMAC-SHA256 of the raw body using the App Secret). If the signature does not match, the message is rejected.
Webhook
The webhook channel is an HTTP POST trigger: any external system can send an event and start a flow. It's the path for custom integrations that don't fit an existing plugin.
Email and Instagram appear as planned integrations on our website, but they are NOT yet implemented in the platform. We don't document their use because there is no API or configuration for them yet.
Step-by-step setup
A summary of how to get each integration running. In every case you need an API key from your Daguito account.
WordPress
Download the plugin, activate it, and paste your API key in Settings → Daguito Chat. The plugin creates the sync flow and imports your WooCommerce products automatically.
Shopify
Install the app via OAuth. Daguito provisions the flow bound to the widget, then the merchant enables the widget in the theme editor (App embeds).
Tiendanube
Start the install via OAuth. Widget injection requires manually uploading the shim to the Partners Portal with automatic install enabled.
Today WhatsApp is configured server-side with environment variables (verify token, access token, and app secret) and by pointing the Meta webhook at the Daguito API. Routing the inbound message to your flow is still being wired up; reach out if you want it enabled.
Channel routing & flow binding
A channel connects to a flow through the channel_flow_bindings relational table. The channel is the entry point; the bound flow decides how to respond. This is how the widget and ecommerce channels work today.
A database constraint (uniq_channel_flow_bindings_active) guarantees only one active flow per channel. Switching flows deactivates the previous one and activates the new one in a single transaction.
You can reuse the same flow across multiple channels, or dedicate a different flow to each one. The channel is the entry point; the flow is the brain.
Manage channels via API
From the admin API you can list your channels with their active flow and change the binding or status of each one:
GET /api/channels # lista los canales y su flujo activo
PATCH /api/channels/:channelId # activa el canal o cambia su flujo enlazado