Skip to content
Novu logoNovu
Vercel AI SDK + Microsoft Teams

Connect your Vercel AI SDK agent to Microsoft Teams

The Vercel AI SDK is the open-source TypeScript toolkit for building agents and AI apps on any model provider. Novu Connect gives it a voice in Microsoft Teams, with a real two-way conversation and reliable delivery. Build the agent once, reach users where they already work.

Explore Novu Connect
Connect your Vercel AI SDK agent to Microsoft Teams with Novu Connect

What is Vercel AI SDK

The Vercel AI SDK gives developers one TypeScript API for agents: generateText and streamText, tool calling, structured output, and a provider layer for OpenAI, Anthropic, Google, Groq, and more. You write the agent loop in your own app and swap models without rewriting it. The AI SDK runs the agent. It does not carry the conversation to your users. That last mile, reaching a person in Slack and routing their reply back to your agent, is what Novu Connect adds.

  • One TypeScript API across OpenAI, Anthropic, Google, Groq, and more
  • Tool calling and structured output for real agent actions
  • generateText for full replies, streamText for streaming ones
  • Runs anywhere JavaScript runs, from Next.js to plain Node

Vercel AI SDK in Microsoft Teams

Novu Connect is the communication layer, the ACI, Agent Communication Infrastructure, bridge between your AI SDK agent and Microsoft Teams. Your agent keeps running in your app. Novu delivers its messages to Microsoft Teams, maps each user, and forwards their replies back to your handler. We never run your agent's reasoning. That is the whole point.

One agent, Microsoft Teams, resolved in the thread

Novu Connect brings an existing AI agent into Microsoft Teams with channel and thread awareness, human handoff workflows, and reliable delivery. Teams connects from the Novu dashboard with authentication. A client needs access for new analysts. The agent checks the seat pool, grants roles with MFA after approval, and confirms.

How to connect Vercel AI SDK to Microsoft Teams

  1. Keep your AI SDK agent

    Your agent loop, tools, and prompts stay in your codebase exactly as they are. Novu Connect wraps the input and output, so your AI SDK logic does not change when you add Microsoft Teams.

  2. Connect the channel

    Run npx novu connect --channel teams --runtime ai-sdk. The CLI scaffolds a bridge route in your app and connects Microsoft Teams. You can also paste the prompt below into your coding agent and let it wire the bridge for you.

  3. Wire the bridge handler

    The CLI prints a requirements file with the bridge route and handler. Return your generateText or streamText result from the handler, and use toModelMessages to pass the Microsoft Teams conversation history to your model.

  4. Go live

    Sign in to keep the agent live, then run your dev server. Your AI SDK agent now holds a two-way conversation in Microsoft Teams, and the same agent can reach every other channel from one thread.

Every Vercel AI SDK connect command

$npx novu connect --channel teams --runtime ai-sdk

Prompt for your coding agent

Connect this project's Vercel AI SDK agent to Microsoft Teams with Novu using instructions from https://novu.co/agents.md

Full setup for Vercel AI SDK lives in the Vercel AI SDK connect guide.

Vercel AI SDK and Microsoft Teams, common questions

No. Novu Connect uses a custom-code bridge. Your AI SDK agent keeps running in your app. Novu forwards messages from Microsoft Teams to your handler and routes replies back, so your agent code stays the same.

Connect your Vercel AI SDK agent to another channel

Same agent, built once. Pick where it talks next, and it holds one conversation across every channel.