docs(TSP-1420): add Slack interactive forms documentation

[claude]

Summary

• Creates /build/tools/tool-steps/slack/interactive-forms.mdx — a new page covering agent Slack card button types (message, form, wizard) and form field configuration, with a focus on the new dropdown field support from PR #17558
• Documents the options array structure (label vs value distinction) and all constraints: max 100 options, 75-char label cap, no duplicate values, single-select only
• Updates the Slack integration overview page (/integrations/popular-integrations/slack.mdx) to link to the new page
• Updates the Send Message tool step page to cross-reference interactive forms
• Adds the new page to the Slack Tool Steps navigation group in docs.json and the shared snippet

Related

• Linear: https://linear.app/relevance/issue/TSP-1420/
• Implements documentation for PR #17558 (Slack dropdown field support)
• Related to TSP-1419 / PR #17510 (Slack wizard button docs, also in progress)

[mintlify]

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

Project	Status	Preview	Updated (UTC)
relevanceai	🟢 Ready	View Preview	Aug 27, 2026, 7:30 AM

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

[linear]

TSP-1420

TSP-1419

[github-actions]

🎯 Vibe check

Reviewed: 5 files (3 with issues, 2 clean)

Scores

	Dimension	Score	What's holding it back
🟡	Consistency	6/10	Six heading capitalization failures in slack.mdx; banned-word-adjacent term in frontmatter description; two [here] link texts; setup used as a verb in two places.
🟡	Technical clarity	7/10	send-message.mdx iframe title reads "Add the Python Tool step to your Tool" — copy-paste artifact. Tool step name uses a colon in step instructions but a dash in the page title. Image alt text in slack.mdx is "Slack Triggers New Pn" (truncated/meaningless).
🟡	Non-technical clarity	8/10	The connection-types card in slack.mdx drops "workspace-level bot token" and "per-user OAuth" without any plain-language gloss. Fine for technical readers, but non-technical admins will be lost.
🟡	Structure	8/10	<Tip> in slack.mdx contains a numbered list with bold labels — violates the CLAUDE.md one-short-paragraph callout rule. send-message.mdx ends after step 5 with no closing context.

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

✨ Overall vibe: The new interactive-forms.mdx page is the strongest file in this PR — clear structure, good use of JSON examples, and the <CardGroup> / <Accordion> / <Warning> components are all appropriate. The slack.mdx update brings the most problems: a cluster of heading capitalization failures in the new Advanced Trigger Settings section, and a <Tip> callout stuffed with a numbered list. Fix those and the PR is in good shape.

🔧 Issues (14)

• integrations/popular-integrations/slack.mdx:3 — frontmatter description: "enabling seamless communication" — "seamlessly" is explicitly banned; "seamless" carries the same spirit. Rewrite: "enabling communication between your AI Workforce and your team's Slack workspace."

• integrations/popular-integrations/slack.mdx:63 — image alt text is Slack Triggers New Pn — "Pn" appears to be a truncated file name artifact. Replace with a descriptive alt text like "Slack channel trigger configuration screen".

• integrations/popular-integrations/slack.mdx:101 — Once setup, you can trigger your Agent → Once set up, … (setup is a noun; set up is the verb phrase).

• integrations/popular-integrations/slack.mdx:105 — heading ### Advanced Trigger Settings → sentence case: ### Advanced trigger settings

• integrations/popular-integrations/slack.mdx:107 — heading #### Live Status Updates → #### Live status updates

• integrations/popular-integrations/slack.mdx:111 — heading #### Exclude Keywords → #### Exclude keywords

• integrations/popular-integrations/slack.mdx:122 — heading #### No Agent Reply → #### No Agent reply (Agent is a product name; Reply is not)

• integrations/popular-integrations/slack.mdx:136 — heading ### Customize Message Formatting → ### Customize message formatting

• integrations/popular-integrations/slack.mdx:161 — heading ## Agent Notifications → ## Agent notifications

• integrations/popular-integrations/slack.mdx:259 — accordion title When I setup a Slack trigger, I can't find channels in my workspace. → When I set up a Slack trigger, …

• build/tools/tool-steps/slack/send-message.mdx:9 — link text [here](/integrations/popular-integrations/slack) — CLAUDE.md forbids "here" as link text. Rewrite: [Slack integration](/integrations/popular-integrations/slack).

• build/tools/tool-steps/slack/send-message.mdx:18 — iframe title attribute reads "Add the Python Tool step to your Tool" — copy-paste error from another page. Should reference Slack Send Message.

• build/tools/tool-steps/slack/send-message.mdx:24 — step 1 refers to 'Slack: Send Message' (colon) but the page title uses 'Slack - Send Message' (dash). If both appear in the product UI, clarify which to search for; if only one is correct, fix the step text.

• build/tools/tool-steps/slack/interactive-forms.mdx:9 — link text [here](/integrations/popular-integrations/slack) — same "here" link text issue. Rewrite: [Slack integration overview](/integrations/popular-integrations/slack).

🧩 Component suggestions (1)

• integrations/popular-integrations/slack.mdx:77–82 — <Tip> contains a numbered list with bold labels, which violates CLAUDE.md's rule that callouts must be a single short paragraph. Either drop the <Tip> wrapper and let the two-item numbered list stand on its own beneath the prose paragraphs, or convert to a <Steps> component if you want the visual progress indicators.

🏗️ Page structure (2)

• build/tools/tool-steps/slack/send-message.mdx — the page ends after step 5 with no closing sentence or next step. This is a how-to page; add a brief closing note pointing to related pages. Natural candidates: [Slack interactive forms](/build/tools/tool-steps/slack/interactive-forms) and [Slack integration overview](/integrations/popular-integrations/slack).

• build/tools/tool-steps/slack/interactive-forms.mdx — the page explains how to configure fields but never says which Tool step generates the interactive card in the first place. A reader arriving here cold won't know they need the Send Message step first. Add a prerequisite sentence near the top, e.g. "These field definitions are used inside the 'Slack - Send Message' Tool step when building a card with form or wizard buttons."

✅ Clean files (2)

_snippets/components/integrations/slack-tool-steps.mdx, docs.json

🔋 Credit usage

Item	Count
Files reviewed	5
Context pages read	2
Total lines processed	~596

Files read: _snippets/components/integrations/slack-tool-steps.mdx (11 lines), build/tools/tool-steps/slack/interactive-forms.mdx (95 lines), build/tools/tool-steps/slack/send-message.mdx (29 lines), integrations/popular-integrations/slack.mdx (320 lines), build/tools/tool-steps/slack/retrieve-messages.mdx (26 lines, sibling context), build/workforces/build-an-ai-workforce/add-triggers.mdx (265 lines, linked context)