Slack Bot - update channeld prop in New Message In Channel trigger

[michelle0927]

Updates the channelId prop to use the conversations propDefinition. Slack context

Summary by CodeRabbit

• Refactor

  • Renamed the Slack channel selection field to “Conversation” in the New Message in Channel source.

• Chores

  • Bumped Slack Bot package version to 0.5.7.
  • Updated New Message in Channel source version to 0.0.6.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
pipedream-docs	Ignored			Sep 26, 2025 5:51pm
pipedream-docs-redirect-do-not-edit	Ignored			Sep 26, 2025 5:51pm

[coderabbitai]

Walkthrough

Version numbers were incremented for the Slack bot package and a Slack source. In the source, the public prop key used to select a channel was renamed from "channelId" to "conversation". No other behavior or dependencies were changed.

Changes

Cohort / File(s)	Summary
Slack Bot Package Version components/slack_bot/package.json	Incremented package version from 0.5.6 to 0.5.7.
Slack Source: New Message in Channel components/slack_bot/sources/new-message-in-channel/new-message-in-channel.mjs	Bumped source version from 0.0.5 to 0.0.6; in props.channelId.propDefinition, changed key from `"channelId"` to `"conversation"`.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I twitch my whiskers, versions hop,
From six to seven—carrot top!
A convo blooms where channel stood,
Small renames nibble, neat and good.
I stamp my paws, release day cheer—
Hop hop, onward, crystal clear! 🥕🐇

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description omits the required “## WHY” section specified in the repository’s template and instead provides only a brief summary and link without the standardized heading or context. Without the template structure, the motivation behind the change is not clearly documented.	Please update the pull request description to include a “## WHY” heading and a detailed explanation of the motivation for the channel prop update, and ensure it follows the exact structure outlined in the repository’s description template.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title concisely describes the main change by indicating that the Slack Bot trigger for “New Message In Channel” has its channel prop updated, making it clear to a reader what the pull request does.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch slack-bot-trigger-update

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 89b584b and 278c267.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (2)

• components/slack_bot/package.json (1 hunks)
• components/slack_bot/sources/new-message-in-channel/new-message-in-channel.mjs (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Publish TypeScript components
• GitHub Check: Verify TypeScript components
• GitHub Check: pnpm publish
• GitHub Check: Lint Code Base

🔇 Additional comments (2)

components/slack_bot/package.json (1)

3-3: Version bump aligns with source update

Thanks for incrementing the package version alongside the source change—this keeps the published artifacts in sync after the propDefinition update.

components/slack_bot/sources/new-message-in-channel/new-message-in-channel.mjs (1)

9-27: Channel prop now correctly reuses the conversations propDefinition

Good call switching the channelId prop to the shared conversation propDefinition and bumping the source version. This keeps the trigger aligned with the latest Slack schema while preserving the existing prop key for downstream consumers.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}