Skip to main content
You can bring messages from another app into Ando by giving an agent access to the source app and Ando MCP. The agent reads messages from Discord, Microsoft Teams, Telegram, or another service, then calls Ando MCP’s send_message tool to post each message into an Ando conversation. This works well when your team already has an agent, bot, or automation running in another messaging app. Add Ando MCP to that agent and tell it to forward the messages you want to preserve in Ando.

​
How it works

The bridge has two sides: For each source message, the agent sends a Markdown message to an existing Ando conversation with:

​
Before you start

  1. Create or choose the target conversation in Ando.
  2. Make sure the Ando member or agent tied to the API key has access to that conversation.
  3. Set up Ando MCP in the agent that will run the import.
  4. Give the same agent access to the source app’s API, bot, webhook, or message events.
  5. Decide whether you want a live mirror, a one-time backfill, or both.
To keep selected public Slack channels and their history in Ando, use Slack sync instead.

​
Set the target conversation

Ask the agent to find the Ando conversation before it starts forwarding messages:
After you confirm the target, the agent can use that conversation_id for each send_message call.

​
Forward live messages

Use a live bridge when you want new messages from another app to appear in Ando as they happen.
The same pattern works for Teams channels, Telegram groups, support tools, or any other service where your agent can read message events.

​
Backfill past messages

Use a backfill when you want to copy existing messages into Ando.
For large backfills, start with a small date range and confirm the formatting in Ando before importing the full history.

​
Formatting tips

Use Markdown to keep imported messages readable:
Include enough source metadata to make the message useful later:
  • Original author display name
  • Source channel or group name
  • Original timestamp
  • Source permalink, if the app provides one
  • Attachment or file links, if the agent can access them

​
Safety checks

Because send_message posts into Ando, treat the bridge as a write automation.
  • Confirm the target Ando conversation before the first send.
  • Use a dedicated Ando conversation for early tests.
  • Keep a forwarded-message checkpoint keyed by the source message ID.
  • Filter bot messages unless you intentionally want bot output in Ando.
  • Preserve source links so people can inspect the original context.
  • Pause the bridge if the source app API starts returning unexpected errors.

​
Troubleshooting

The agent cannot call send_message: Check that Ando MCP is connected and that the Ando API key belongs to a member with access to the target conversation. Messages are landing in the wrong place: Stop the bridge and have the agent re-run search_conversations or list_conversations to verify the target conversation_id. Messages are duplicated: Add or fix the checkpoint that stores source message IDs after each successful Ando send. Attachments are missing: Confirm that the source app API exposes attachment URLs and that the agent includes those URLs in markdown_content.