Your own order dashboard
Read messages from your number and turn enquiries into orders for review in your dashboard.
Your app organizes; you decide what to confirm.
YOUR APP. YOUR NUMBER.
Link your number through Facebook, copy your personal key and use it in your application. A simple way to add WhatsApp messages to the software you built for your business.
One URL and one personal key to connect your MCP client. Enlazá handles the WhatsApp Business connection; your app reads messages, organizes orders and drafts or sends replies with the permissions you choose. Keep your number and WhatsApp Business on your phone.
Sign in to Enlazá and link WhatsApp Business. Creating an account and connecting your number are separate steps.
Name your integration and choose reading, sending and notifications as needed. Copy the key when it is shown once.
Store the key on your app’s server and connect an MCP client to https://enlaza.chat/mcp. Your coding agent can follow the documentation.
Read messages from your number and turn enquiries into orders for review in your dashboard.
Your app organizes; you decide what to confirm.
Bring enquiries into the system you already use. With event support, your app can learn about new messages and retrieve their content.
Events require a subscription; on-demand reading works too.
Prepare a reply using data from your system, then send text, an image or a PDF to the selected contact.
With sending permission, authorization and WhatsApp rules.
Use the same connection with an assistant supporting remote MCP and a Bearer key. Open its integration settings to connect.
The technical guide helps configure a compatible client.
An internal dashboard, a customer-service tool, an order organizer or an app built with AI: choose where your messages are useful. Enlazá provides authorized WhatsApp access; your software controls how it displays and processes that information.
Instructions for your coding agent →You need a connected WhatsApp Business number and an application supporting MCP over HTTP. Reading does not enable sending: you choose permissions. History and media depend on what is available for your number. To react automatically to new messages, your app must support events and create a subscription.
Link WhatsApp Business in Enlazá, create a personal key and store it on your app’s server. If your app already supports MCP, configure the URL and key. Otherwise, give the guide to your coding agent to add an MCP client. Keep the key in your secure secrets manager, never in a chat.
Your app connects using MCP over HTTP and tools for reading and sending. The guide includes JSON-RPC requests. Discover the available tools with tools/list rather than inventing WhatsApp endpoints.
Yes, with a connected number and the required permissions. Read on demand, or configure events and a subscription for notifications. Free-form replies require the 24-hour conversation window; outside it, use approved templates and consent.
A personal key works with clients supporting remote MCP and Bearer authentication, as well as your own applications. Each client’s configuration and capabilities determine which features it can use.
Yes. Revoke the key in Enlazá. Use a separate key for each integration to manage access independently. The secret is shown only once.
Yes. Enlazá offers a free trial for eligible numbers. Your account shows its status and terms; reconnecting a number does not restart a used trial. Check the connection and message reading before deciding how to continue.
Connect your app to Enlazá over MCP with a personal key stored on its server. Your software can read available messages, extract order details and save them to your CRM through an integration you have prepared. Enlazá supplies the WhatsApp connection; your app defines order rules, CRM access and human confirmation. Start with a read request.
Yes, if your app server can use an MCP client over HTTPS with Bearer authentication. Ask your coding assistant to implement the client using the Enlazá guide and store the key as a server secret. Do not put it in browser code or a chat. The protocol is MCP, not a generic WhatsApp REST API. See the protocol and permissions.
Configure MCP Events and an incoming-message subscription for the authorized connection. Your app needs an HTTPS receiver that verifies requests and completes the initial verification. Keep and renew the subscription according to its expiry. Reading messages and receiving notifications are separate capabilities: check that your client supports events and that notifications are authorized. See the events guide.