Skip to navigation
ChannelsMessaging

Automation and Languages

Overview

Connect Messaging SDK settings to your AI Agent’s existing configuration. Share the current SDK reference with developers who maintain these connections.

Limitations

Messaging methods and event payloads can differ from legacy integration examples. Check each method before copying old code.

MCP service sign-in and Ada identity tokens serve different purposes. An Ada identity token does not authenticate an end user to an MCP service.

Capabilities & configuration

Use the Messaging integration points below with the relevant dashboard feature.

ConfigurationMessaging integration
VariablesPass flat metadata through setMetaFields. Review field limits.
API toolsSupply configured input data through the documented metadata methods.
MCP toolsFollow the tool’s sign-in or sensitive-metadata configuration. Keep service credentials separate from Ada identity.
LanguagesSet the initial language or call setLanguage.
ProactivesOpen Messaging > Outreach to configure Proactive messages. If a moved notice appears, follow Go to Outreach. Use triggerProactive for custom triggers.

Implementation & usage

Validate Messaging configuration on your installed website or app.

  • Check variable values after initialization and after a metadata update.
  • Verify sensitive values against the tool configuration that consumes them.
  • Test every supported language, including returning users and explicit language changes.
  • Test Proactive triggers, substitutions, display conditions, and campaign reporting.

Use Personalization and identity for metadata limits and signed-in user flows.

Compare reporting changes after migration. A Proactive campaign event can depend on whether its message renders.

Have any questions? Contact your Ada team, or email us at .