Integrations
Connect your channels and your data.
An agent is useless if it cannot see your stock and does not speak where your customers write. Here is what it connects to, and the documentation for each.
WhatsApp, Instagram, Messenger, email and website chat connect. Their conversations land in one inbox, and the agent answers each one from the shop’s catalog, prices and rules.
Meta channels
Meta Tech Provider, verified business.
Magnitude is registered with Meta as a Tech Provider, with a verified business. WhatsApp, Instagram and Messenger run on Meta’s official APIs, not through an unofficial gateway.
- Instagram and Messenger connect in one click, with your own account.
- WhatsApp connects with the number’s ID and its access token, checked before the channel opens.
- Meta’s rules are kept: free replies for 24 hours after the customer’s last message, a Meta-approved template after that.
- The number, the page and the Instagram account stay yours.
5 channels
Where your customers write.
Answer on the channel your customers already use, with a business number and the history kept.
See the channelDirect messages and story replies, handled as conversations rather than notifications.
See the channelMessenger
Your Facebook page wired to the same agent, with the same context as every other channel.
See the channelWeb agent
A widget on your site, one line of script, answering from your catalog and your opening hours.
See the channelThe shared inbox lands next to your other channels, and every email is filed on the customer’s record, so nothing is lost between chat and email.
See the channelLive data
Data sources
What the agent reads to answer correctly.
Catalog · AirtableFAQ
Before you pick a channel
Do we have to connect everything at once?
No, and it usually works better the other way: one channel first, whichever carries the most messages, and the rest once that one is running. One agent can answer on several channels, so what you tune on the first serves the others; website chat has its own web agent.
If a customer writes on two channels, is that two conversations?
Two conversations, one customer record. The record gathers their exchanges from every channel, Monday’s email next to Thursday’s message, so whoever picks it up sees what was already said.
What happens if a data source goes down?
The agent does not guess. What it cannot read, it does not assert: it says so and hands over, which is the behavior that keeps the other answers trustworthy.
What if the connector we need does not exist?
The REST API covers most cases: you expose an endpoint, the agent sends the customer query and reads the response. For anything else, tell us which one is missing.
Missing a connector?
Tell us which one. The REST API already covers most cases, and the rest is a conversation.
While you were reading this, a customer was waiting for an answer.
Create your agent, connect a channel, let it run. Fourteen-day free trial.
No credit card · Live in hours, no code