fix(types): Slack types clean

[khaliqgant]

Describe your changes

Issue ticket number and link

Checklist before requesting a review (skip if just adding/editing APIs & templates)

• I added tests, otherwise the reason is:
• External API requests have retries
• Pagination is used where appropriate
• The built in nango.paginate call is used instead of a while (true) loop
• Third party requests are NOT parallelized (this can cause issues with rate limits)
• If a sync requires metadata the nango.yaml has auto_start: false
• If the sync is a full sync then track_deletes: true is set
• I followed the best practices and guidelines from the Writing Integration Scripts doc

[my-senior-dev-pr-review]

🤖 My Senior Dev — Analysis Complete

👤 For @khaliqgant

📁 Expert in internal/ (9 edits) • ⚡ 5th PR this month

View your contributor analytics →

---

📊 27 files reviewed • 1 high risk • 78 need attention

🚨 High Risk:

• integrations/.nango/schema.json — Large binary file change that might affect numerous integrations requiring a thorough review on schema compatibility and API stability.

⚠️ Needs Attention:

• integrations/.nango/schema.ts — Critical for the correctness of type definitions interfacing with external APIs.
• integrations/slack/.nango/schema.ts — Specifies the structure of Slack API interactions which is critical for type safety.
• +22 more concerns...

---

🚀 Open Interactive Review →

The full interface unlocks features not available in GitHub:

• 💬 AI Chat — Ask questions on any file, get context-aware answers
• 🔍 Smart Hovers — See symbol definitions and usage without leaving the diff
• 📚 Code Archeology — Understand how files evolved over time (/archeology)
• 🎯 Learning Insights — See how this PR compares to similar changes

---

💬 Chat here: @my-senior-dev explain this change — or try @chaos-monkey @security-auditor @optimizer @skeptic @junior-dev

📖 View all 12 personas & slash commands

You can interact with me by mentioning @my-senior-dev in any comment:

In PR comments or on any line of code:

• Ask questions about the code or PR
• Request explanations of specific changes
• Get suggestions for improvements

Slash commands:

• /help — Show all available commands
• /archeology — See the history and evolution of changed files
• /profile — Performance analysis and suggestions
• /expertise — Find who knows this code best
• /personas — List all available AI personas

AI Personas (mention to get their perspective):

Persona	Focus
@chaos-monkey 🐵	Edge cases & failure scenarios
@skeptic 🤨	Challenge assumptions
@optimizer ⚡	Performance & efficiency
@security-auditor 🔒	Security vulnerabilities
@accessibility-advocate ♿	Inclusive design
@junior-dev 🌱	Simple explanations
@tech-debt-collector 💳	Code quality & shortcuts
@ux-champion 🎨	User experience
@devops-engineer 🚀	Deployment & scaling
@documentation-nazi 📚	Documentation gaps
@legacy-whisperer 🏛️	Working with existing code
@test-driven-purist ✅	Testing & TDD

For the best experience, view this PR on myseniordev.com — includes AI chat, file annotations, and interactive reviews.