Add Microsoft Teams calendar trigger and Event sensitivity filter documentation

[claude]

Summary

• Adds a new Teams calendar trigger subsection to the Microsoft Teams integration page, explaining that agents can be triggered by calendar events in the user's Microsoft/Teams calendar
• Documents the Event sensitivity advanced setting — a multi-select (Normal / Private) that controls which calendar events activate the agent
• Both options selected by default (backward-compatible); users can deselect Private to exclude personal meetings from workflows, or deselect Normal to trigger only on private events

Linear issue

https://linear.app/relevance/issue/TSP-1336/

Test plan

• Verify new subsection renders correctly in Mintlify preview
• Confirm heading levels match existing Triggers section structure
• Check <Note> and <CardGroup> components display as expected
• Validate no broken internal links introduced

🤖 Generated with Claude Code

[linear]

TSP-1336

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
relevanceai	🟢 Ready	View Preview	Jul 10, 2026, 5:01 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[github-actions]

🎯 Vibe check

Reviewed: 1 file (1 with issues, 0 clean)

Scores

	Dimension	Score	What's holding it back
🔴	Consistency	5/10	"agent", "workforce", and "trigger" as Relevance AI product terms are uncapitalized throughout — ~25+ instances across headings, step titles, body text, and accordion titles.
🟡	Technical clarity	8/10	Missing /get-started/support link in the beta Note; "approval mode" and "autopilot" mentioned without pointing to where in the UI these settings live.
🟢	Non-technical clarity	9/10	Clear intro, well-signposted two-step setup, strong FAQ coverage. Admin consent section uses "Azure AD / Entra ID tenant" cold but the audience there is admins, so it's acceptable.
🟡	Structure	7/10	Prerequisites and setup overview both use <CardGroup> for content that isn't navigable or a parallel choice — simpler list formats serve those sections better.

Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5.

✨ Overall vibe: The page is comprehensive and technically sound — thorough troubleshooting, a complete permissions reference, and clear step-by-step setup make it genuinely useful. The main drag is pervasive uncapitalized Relevance AI product terms ("agent", "workforce", "trigger") throughout; this is the single biggest gap against CLAUDE.md requirements and affects nearly every section of the page.

🔧 Issues (5)

• integrations/popular-integrations/microsoft-teams.mdx:145,147,160,178,183,193,220,221,224,235,239,267,290,298,334,342,347,351,364,466,469 — "agent/agents" lowercase throughout when referring to Relevance AI product Agents. Widespread. Representative examples: line 145 "your agents respond" → "your Agents respond"; line 160 step title "Open your agent's settings" → "Open your Agent's settings"; line 347 "Navigate to your agent" → "Navigate to your Agent". Every instance where "agent" is a Relevance AI product noun needs capitalization.

• integrations/popular-integrations/microsoft-teams.mdx:147,286,466 — "workforce/workforces" lowercase when referring to Relevance AI Workforces. Line 147: "The same trigger setup also works for workforces" → "Workforces". Line 286 (card title body): "Teams messages can trigger an entire workforce" → "Workforce". Line 466 (accordion title): "in agent or workforce settings" → "Agent or Workforce settings".

• integrations/popular-integrations/microsoft-teams.mdx:149,151,174,185,205,226,237,464 — "trigger(s)" as a Relevance AI product noun is lowercase in headings and step titles. Line 151: ### Setting up a trigger → "Setting up a Trigger". Line 185: ### Advanced trigger settings → "Advanced Trigger settings". Line 205 (step title): "Open your trigger" → "Open your Trigger". Line 226 (step title): "Open your trigger settings" → "Open your Trigger settings". Line 237: ### Teams calendar trigger → "Teams calendar Trigger". Line 464 (accordion title): "Teams trigger option not visible in agent settings" → "Teams Trigger option not visible in Agent settings". (When "trigger" is a verb — e.g. line 147 "to trigger agents" — lowercase is correct per CLAUDE.md.)

• integrations/popular-integrations/microsoft-teams.mdx:330 — <Note> says "Please report any issues to our support team" with no link. Should link to /get-started/support per CLAUDE.md: "Always link to the support contact page rather than referencing specific email addresses" (applies to unlinked support mentions too).

• integrations/popular-integrations/microsoft-teams.mdx:153 — <a href="#step-1-connect-the-integration"> raw HTML anchor inside a <Note> component. All other internal links in this file and sibling pages use markdown [text](#anchor) syntax. Should be [Step 1: Connect the integration](#step-1-connect-the-integration) and [Step 2: Install the Relevance AI app](#step-2-install-the-relevance-ai-app-in-microsoft-teams).

🧩 Component suggestions (2)

• integrations/popular-integrations/microsoft-teams.mdx:15–28 — Prerequisites as <CardGroup cols={2}>. CLAUDE.md says CardGroups are not appropriate for "short adjective or property lists" or items that aren't navigable. These four prerequisites don't link anywhere and aren't parallel choices — they're a checklist. Replace with a plain - bullet list, or a <Steps> if you want to imply the reader should verify each one. The icons add no value here when none of the cards are interactive.

• integrations/popular-integrations/microsoft-teams.mdx:34–41 — "Setup overview" as <CardGroup cols={2}> with card titles beginning "1." and "2.". The numbered prefixes signal these are sequential required steps, not parallel choices — but cards visually imply equal, independent options. Either drop this section entirely (the detailed Step 1 / Step 2 sections immediately follow and make it redundant), or replace with a simple two-item numbered list: "1. Connect your Microsoft account — jump to step. 2. Install the Relevance AI app in Teams — jump to step."

🔋 Credit usage

Item	Count
Files reviewed	1
Context pages read	2
Total lines processed	~1,275

Files read: integrations/popular-integrations/microsoft-teams.mdx (532 lines), integrations/popular-integrations/outlook.mdx (423 lines), integrations/popular-integrations/slack.mdx (320 lines)