docs(TSP-1236): explain dual Slack auth methods across Builder and SuperGTM

[claude]

Summary

• Adds a new "Understanding Slack connections in Relevance AI" section to integrations/popular-integrations/slack.mdx, placed between the initial setup steps and the triggers section. Uses a two-card layout and an <Info> callout to clearly distinguish the workspace-level bot token (Builder) from the per-user OAuth token (SuperGTM).
• Adds a new FAQ entry: "Why does Slack work in SuperGTM but not in Builder (or vice versa)?" explaining the two auth methods and troubleshooting steps.
• Updates the Slack accordion in get-started/chat/super-gtm/integrations.mdx to note that SuperGTM uses per-user OAuth, with a cross-link to the Builder Slack docs and a note that workspace admins can allow one type while blocking the other.

Motivation

Customers were confused when Slack worked in one area of the platform but not another, because the two connection types (workspace bot vs. per-user OAuth) can be allowed/blocked independently by workspace admins.

Test plan

• Verify cross-links resolve correctly: /integrations/popular-integrations/slack and /get-started/chat/super-gtm/integrations
• Check sentence case on all new headings and card/accordion titles
• Confirm <Info> callout renders correctly (single paragraph, no nested lists)
• Confirm <CardGroup cols={2}> layout renders correctly

Linear: https://linear.app/relevance/issue/TSP-1236/

[linear]

TSP-1236

[github-actions]

🎯 Vibe check

Reviewed: 2 files (1 with multiple issues, 1 relatively clean)

Scores

	Dimension	Score	What's holding it back
🟡	Consistency	6/10	slack.mdx: 4 heading sentence-case violations, "seamless" in the frontmatter description, "agent" lowercase where the product term requires capitalization, "Once setup" typo. integrations.mdx: "builders app" should be "Builder".
🟡	Technical clarity	6/10	slack.mdx: 6 Supademo embed divs use "padding-top" in JSX style objects — React requires paddingTop (camelCase). This likely breaks the aspect-ratio sizing, collapsing the video embeds. Also: a hardcoded URL on line 13, and the support callout links nowhere.
🟢	Non-technical clarity	9/10	The new "Understanding Slack connections in Relevance AI" section is the strongest part of this PR — it explains the dual-auth model plainly and answers the single most confusing Slack question. Minor deduction for the marketing-ish description.
🟡	Structure	7/10	slack.mdx: the <Tip> on lines 66–71 violates CLAUDE.md's one-paragraph callout rule (contains a numbered list and bold labels). The top-of-page numbered list (lines 11–19) is a sequential procedure that should use <Steps>. The last FAQ entry largely repeats the new dual-auth section above.

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

✨ Overall vibe: The core addition — explaining that Builder and SuperGTM use different Slack auth methods — is genuinely useful and well-written on both pages. integrations.mdx is solid with one minor nit. slack.mdx needs a pass to fix the JSX rendering bug, four heading cases, and a callout component violation before this is ship-ready.

🔧 Issues (11)

• integrations/popular-integrations/slack.mdx:3 — description uses "seamless communication" — adjacent to the banned "seamlessly". Replace with plain description, e.g. "Connect Slack to your Relevance AI Agents, Workforces, and SuperGTM to read and post messages, trigger workflows, and send notifications."

• integrations/popular-integrations/slack.mdx:7 — <Note> opens with "Note: " — redundant since the component already signals it's a note. Remove the "Note: " prefix.

• integrations/popular-integrations/slack.mdx:9 — "contact our Support" has no link. Per content standards, this must link to /get-started/support.

• integrations/popular-integrations/slack.mdx:13 — bare URL https://app.relevanceai.com typed inline as text. Use linked text instead: [Log in to Relevance AI](https://app.relevanceai.com) or just "Log in to Relevance AI."

• integrations/popular-integrations/slack.mdx:21,75,145,168,183,205 — six Supademo embed <div> wrappers use "padding-top":"56.75%" in their style objects. JSX inline styles require camelCase property names — "padding-top" is not applied by React; it must be paddingTop: '56.25%'. This likely collapses all six video embeds to zero height. (integrations.mdx line 10 already does this correctly for reference.)

• integrations/popular-integrations/slack.mdx:91 — "Once setup, you can trigger…" → "Once set up, you can trigger…" ("setup" is a noun; "set up" is the verb/adjective form).

• integrations/popular-integrations/slack.mdx:94 — heading ### Advanced Trigger Settings → ### Advanced Trigger settings (sentence case; "Settings" is not a proper noun).

• integrations/popular-integrations/slack.mdx:125 — heading ### Customize Message Formatting → ### Customize message formatting (sentence case).

• integrations/popular-integrations/slack.mdx:138,140,141 — "your agent" / "the agent" in the Escalate section refers to the Relevance AI product feature — should be capitalized: "your Agent", "the Agent."

• integrations/popular-integrations/slack.mdx:150 — heading ## Agent Notifications → ## Agent notifications (sentence case; "Notifications" is not a proper noun).

• integrations/popular-integrations/slack.mdx:271 — heading ## Privacy Policy → ## Privacy policy (sentence case).

• get-started/chat/super-gtm/integrations.mdx:44 — "in the builders app" → "in the Builder" (product area name is capitalized as "Builder" — see slack.mdx line 36 for consistent usage).

🧩 Component suggestions (2)

• integrations/popular-integrations/slack.mdx:11–19 — the seven-step onboarding sequence is a plain markdown numbered list. This is a sequential procedure — wrap it in <Steps> so it gets the visual progress indicators. Each item maps cleanly to a <Step title="...">.

• integrations/popular-integrations/slack.mdx:66–71 — the <Tip> contains **Channel vs DM setup:** as a bold label followed by a two-item numbered list. CLAUDE.md: "Callouts must be a single short paragraph — no bullet lists, no multi-line content, no bold labels inside." Convert this to a proper #### Channel vs DM setup sub-heading followed by the two-item list (or a <Steps> block), then remove the <Tip> wrapper.

🏗️ Page structure (1)

• integrations/popular-integrations/slack.mdx:260–264 — the FAQ entry "Why does Slack work in SuperGTM but not in Builder (or vice versa)?" is a near-verbatim repeat of the new "Understanding Slack connections in Relevance AI" section (lines 31–48). The FAQ answer is almost word-for-word the same content. Consider collapsing the FAQ to one sentence pointing up to that section: "See Understanding Slack connections in Relevance AI."

✅ Clean files (1)

get-started/chat/super-gtm/integrations.mdx — one minor nit (line 44 "builders app"), otherwise headings, components, links, product term casing, and structure are all correct.

🔋 Credit usage

Item	Count
Files reviewed	2
Context pages read	1 (build/workforces/build-an-ai-workforce/add-triggers.mdx)
Total lines processed	~1080

Files read: get-started/chat/super-gtm/integrations.mdx (530 lines), integrations/popular-integrations/slack.mdx (285 lines), build/workforces/build-an-ai-workforce/add-triggers.mdx (265 lines)