ttextxt Open Textxt

Connected Apps

Connect services and MCP tools

Connect Gmail, business messaging, or a remote MCP server so approved Assistants and Agent workflows can use external capabilities.

Current product guide · Updated 2026-09-04

Where to open it

Path

Open Settings > Connected Apps and choose a service or MCP Servers.

What it can do

  • Connect a Gmail account through Google OAuth without requiring it to match the Textxt account email.
  • Connect WhatsApp through the official Meta Cloud API and Zalo through the official Zalo OA API.
  • Use verified connections as triggers and reply destinations in published Agent workflows.
  • Connect a public HTTPS Streamable HTTP MCP server, inspect its tools, and allow only the tools AI Assistant needs.
  • Authorize protected MCP servers with OAuth 2.1 PKCE, dynamic client registration, or a pre-registered client ID.

Step by step

  1. Open Connected Apps, choose a provider or MCP Servers, and complete its setup.
  2. Verify the connection status and incoming-event configuration.
  3. Open an Agent workflow, select the connection as its trigger, and configure deterministic filters.
  4. Publish the workflow and inspect Runs. Keep customer-facing replies behind approval.

Ask an external AI

Paste this prompt into ChatGPT, Claude, or another assistant that can open public web pages:

Read https://textxt.com/help/connected-apps and guide me step by step. Use only capabilities documented on that page, ask for missing context, and do not invent buttons or settings.

Example questions

  • How do I connect Gmail to Textxt and send only Primary inbox messages into a chat?
  • What credentials and webhook settings are required for WhatsApp Business in Textxt?

Good to know

  • Textxt supports official WhatsApp Business and Zalo OA APIs, not personal WhatsApp Web or personal Zalo session automation.
  • Credentials remain server-side. Disconnecting removes active credentials while preserving workflow history and audit records.
  • Connecting a service does not automatically forward all messages; you must publish a workflow with the desired filters and destination.
  • MCP credentials stay server-side. Every Assistant MCP call appears as an approval step, and server responses are treated as untrusted data.
  • MCP supports public HTTPS Streamable HTTP endpoints with OAuth, a Bearer token, or no authentication. Private localhost and stdio servers still require a future Desktop Bridge.
Keep private data private.

Never paste Textxt passwords, OAuth tokens, API keys, private chat exports, or confidential attachments into an external AI just to ask how the product works.

Continue with Textxt