Skip to main content

Embed AI in existing tools

The most-used AI is the AI people do not have to go find. This page explains why meeting users inside the tools they already work in beats sending them to a separate app, how DIAL reaches into Microsoft Teams, Excel, automation pipelines, and custom web apps, and what each integration assumes. It is for decision-makers judging the reach and for builders who would wire it up.

Why this matters​

A standalone AI assistant competes for attention with every other tab. Adoption stalls not because the assistant is poor but because using it means leaving the work — switching context, copying data across, pasting results back. The friction is small per interaction and decisive in aggregate.

Embedding AI where work already happens removes that friction. A support agent triaging in Teams, an analyst modeling in Excel, or an operations team running an automation pipeline can call a governed model in place, without a context switch. The same governance still applies, because the request travels back to DIAL Core regardless of where it started.

What you can do with DIAL​

DIAL is API-first, so any surface that can make an HTTP request can reach it through the Unified API. The documented integrations cover the common surfaces:

  • Chat platforms. Bring DIAL into Microsoft Teams and Microsoft Copilot, so conversations with AI happen where team conversations already happen.
  • Productivity tools. The Microsoft Excel add-in puts DIAL inside the spreadsheet.
  • Automation pipelines. Use DIAL as a node in n8n workflows, so AI steps sit alongside the rest of an automation.
  • Your own web apps. DIAL Overlay drops a chat experience into an existing web application, and you can embed Chat in a web app directly.

In every case the embedded surface is a thin client. The model access, access control, and cost limits stay in Core, so an integration does not become an ungoverned side door.

How you'd build it​

  • Pick the surface. Integrations is the index of supported targets.
  • Follow the integration guide for your surface from the list above; each is a how-to with the specific setup.
  • For custom UIs, use the Overlay. DIAL Overlay is the supported way to embed chat into your own application.

Why DIAL over the alternatives​

Each tool has its own AI add-on, but those are per-tool and per-vendor: a Teams bot built on one provider, an Excel plugin on another, each with its own keys and its own blind spot for cost and audit. Building each integration directly against a model provider repeats that fragmentation. DIAL puts one governed gateway behind all of them, so the Teams bot, the Excel add-in, and the automation node share the same access rules, limits, and audit trail. The cost is running that gateway and using the documented integration for each surface rather than a turnkey vendor add-on.

Further reading​