[ACTION] Trengo - Add Helpcenter API Methods and List Help Centers Action #19273

SIVALANAGASHANKARNIVAS · 2025-11-26T17:22:33Z

WHY

This PR addresses issue #19172 by adding Helpcenter API support for Trengo.

Summary

Added new Helpcenter API methods to trengo.app.mjs and created a new action:

API Methods Added:

getHelpCenter - Get a specific help center by ID
getCategories - List all categories in a help center
getCategory - Get a specific category by ID
getBlocks - List all blocks in a help center
getBlock - Get a specific block by ID
getArticle - Get a specific article by ID

Actions Added:

list-help-centers - Lists all help centers with optional max results filter

API Documentation

Resolves #19172

Summary by CodeRabbit

Release Notes

New Features
- Added the ability to list help centers within the Trengo integration, allowing users to retrieve and manage help center information efficiently.
Version Update
- Bumped component version to 0.6.0.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Added new API methods for Trengo Helpcenter: - getHelpCenter: Get a specific help center - getCategories: List all categories in a help center - getCategory: Get a specific category - getBlocks: List all blocks in a help center - getBlock: Get a specific block - getArticle: Get a specific article Resolves PipedreamHQ#19172

This file defines an action to list all help centers with optional max results.

vercel · 2025-11-26T17:22:41Z

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

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
pipedream-docs-redirect-do-not-edit	Ignored			Nov 26, 2025 10:07pm

pipedream-component-development · 2025-11-26T17:22:52Z

Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified.

pipedream-component-development · 2025-11-26T17:22:53Z

coderabbitai · 2025-11-26T17:22:55Z

Walkthrough

Introduces a new Trengo integration action module to list help centers, leveraging the Trengo API endpoint. The action accepts an optional maxResults parameter to limit the number of results returned. Additionally, the package version is incremented from 0.5.0 to 0.6.0 to reflect this new functionality.

Changes

Cohort / File(s)	Summary
New Trengo Action `components/trengo/actions/list-help-centers/list-help-centers.mjs`	New action module that exports configuration and runtime logic for listing help centers; includes props for app selection and optional maxResults filtering; streams help center data via `utils.getResourcesStream` and accumulates results into an array
Version Update `components/trengo/package.json`	Package version incremented from `0.5.0` to `0.6.0`

Sequence Diagram

sequenceDiagram
    actor User
    participant Action as list-help-centers
    participant Utils as utils
    participant API as Trengo API
    participant Stream as Result Stream

    User->>Action: Invoke with maxResults parameter
    Action->>Utils: Call getResourcesStream()
    Utils->>API: Call getHelpCenters()
    API-->>Stream: Stream help center data
    Stream-->>Utils: Emit results
    Utils->>Action: Accumulate up to maxResults
    Action->>Action: Export summary with count
    Action-->>User: Return collected help centers array

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Verify the action follows established Trengo integration patterns
Confirm getResourcesStream implementation and maxResults boundary logic work as intended
Validate props schema (app, maxResults) aligns with component conventions
Check the summary export format matches expected structure

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main changes: adding Helpcenter API methods and a list help centers action to the Trengo component.
Description check	✅ Passed	The PR description follows the template with a WHY section, provides a clear summary of API methods and actions added, and includes relevant API documentation links.
Linked Issues check	✅ Passed	The PR implements all 7 coding objectives from issue #19172: getHelpCenter, getCategories, getCategory, getBlocks, getBlock, getArticle API methods, and the list-help-centers action.
Out of Scope Changes check	✅ Passed	All changes are directly aligned with issue #19172 requirements. The version bump in package.json is a standard practice for publishing component updates.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4be26fa and 255da42.

📒 Files selected for processing (1)

components/trengo/package.json (1 hunks)

🔇 Additional comments (1)

components/trengo/package.json (1)

3-3: Version bump aligns with semantic versioning; however, review context is incomplete.

The minor version bump from 0.5.0 to 0.6.0 is appropriate for adding new features. However, the PR objectives and AI summary reference multiple code changes (new API methods in trengo.app.mjs, new action list-help-centers.mjs) that are not included in the provided review context.

Please ensure the full PR includes the following files for comprehensive review:

components/trengo/trengo.app.mjs (should contain new API methods: getHelpCenter, getCategories, getCategory, getBlocks, getBlock, getArticle, and getHelpCenters)

components/trengo/actions/list-help-centers/list-help-centers.mjs (new action to list help centers)

Without these files, I cannot verify:

Correct implementation of Helpcenter API methods per the Trengo API documentation

Proper action structure and adherence to Pipedream component guidelines (naming, JSDoc, pagination handling, etc.)

Integration between the new action and app methods

Proper error handling and request validation

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

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

coderabbitai

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

components/trengo/trengo.app.mjs (1)
365-421: Missing comma after attachLabel breaks the methods object

There’s no comma after the attachLabel method before the // Helpcenter API methods comment and the new methods. This makes the methods object invalid and explains the Biome parse errors cascading from this region.

Add a comma after the closing brace of attachLabel:
     attachLabel({
       ticketId, ...args
     }) {
       return this._makeRequest({
         method: "POST",
         path: `/tickets/${ticketId}/labels`,
         ...args,
       });
-    // Helpcenter API methods
+    },
+    // Helpcenter API methods
With that fixed, the new Helpcenter methods (getHelpCenter / getCategories / getCategory / getBlocks / getBlock / getArticle) follow the existing _makeRequest pattern and look consistent with the Trengo API surface you described.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 10ad254 and 6c14ddd.

📒 Files selected for processing (2)

components/trengo/actions/list-help-centers/list-help-centers.mjs (1 hunks)
components/trengo/trengo.app.mjs (1 hunks)

🧰 Additional context used

🪛 Biome (2.1.2)

components/trengo/trengo.app.mjs

[error] 376-376: Expected a semicolon or an implicit semicolon after a statement, but found none

An explicit or implicit semicolon is expected here...

...Which is required to end this statement

(parse)

[error] 381-382: Expected a statement but instead found ',
getCategories('.

Expected a statement here.

(parse)

[error] 383-383: Expected an expression but instead found '...'.

Expected an expression here.

(parse)

[error] 384-384: Expected a statement but instead found ')'.

Expected a statement here.

(parse)

[error] 389-390: Expected a statement but instead found ',
getCategory('.

Expected a statement here.

(parse)

[error] 391-391: Expected an expression but instead found '...'.

Expected an expression here.

(parse)

[error] 392-392: Expected a statement but instead found ')'.

Expected a statement here.

(parse)

[error] 397-398: Expected a statement but instead found ',
getBlocks('.

Expected a statement here.

(parse)

[error] 399-399: Expected an expression but instead found '...'.

Expected an expression here.

(parse)

[error] 400-400: Expected a statement but instead found ')'.

Expected a statement here.

(parse)

[error] 405-406: Expected a statement but instead found ',
getBlock('.

Expected a statement here.

(parse)

[error] 407-407: Expected an expression but instead found '...'.

Expected an expression here.

(parse)

[error] 408-408: Expected a statement but instead found ')'.

Expected a statement here.

(parse)

[error] 413-414: Expected a statement but instead found ',
getArticle('.

Expected a statement here.

(parse)

[error] 415-415: Expected an expression but instead found '...'.

Expected an expression here.

(parse)

[error] 416-416: Expected a statement but instead found ')'.

Expected a statement here.

(parse)

[error] 421-421: Expected a statement but instead found ','.

Expected a statement here.

(parse)

components/trengo/actions/list-help-centers/list-help-centers.mjs

This fixes the Biome parse error caused by a missing closing brace and comma after the attachLabel method. The methods object was invalid because the attachLabel method was not properly terminated before the Helpcenter API methods.

coderabbitai

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6c14ddd and 4be26fa.

📒 Files selected for processing (1)

components/trengo/trengo.app.mjs (1 hunks)

components/trengo/trengo.app.mjs

michelle0927

LGTM! Ready for QA!

vunguyenhung · 2025-11-27T02:02:30Z

Hello everyone, I have tested this PR and there're some test cases failed or needed improvement.

Please check test reports below for more information:

[ACTION] trengo - Helpcenter - Actions Batch 1: https://www.notion.so/ACTION-trengo-Helpcenter-Actions-Batch-1-1-2b7bf548bb5e81e1bd7fc4c9af914ce4

vunguyenhung · 2025-11-27T02:26:28Z

Hello everyone, I have tested this PR and there're some test cases failed or needed improvement.

Please check test reports below for more information:

[ACTION] trengo - Helpcenter - Actions Batch 1: https://www.notion.so/ACTION-trengo-Helpcenter-Actions-Batch-1-1-2b7bf548bb5e81e1bd7fc4c9af914ce4

jcortes

Hi @SIVALANAGASHANKARNIVAS lgtm! Ready for QA!

vunguyenhung · 2025-11-28T01:35:20Z

Hello everyone, I have tested this PR and there're some test cases failed or needed improvement.

Please check test reports below for more information:

[ACTION] trengo - Helpcenter - Actions Batch 1: https://www.notion.so/ACTION-trengo-Helpcenter-Actions-Batch-1-1-2b7bf548bb5e81e1bd7fc4c9af914ce4

jcortes · 2025-11-28T14:32:47Z

Hi @SIVALANAGASHANKARNIVAS and @vunguyenhung this PR is going to be closed in favor of #19277

SIVALANAGASHANKARNIVAS added 2 commits November 26, 2025 22:47

feat(trengo): Add list-help-centers action

6c14ddd

This file defines an action to list all help centers with optional max results.

adolfo-pd added the User submitted Submitted by a user label Nov 26, 2025

dannyroosevelt added this to Component (Source and Action) Backlog Nov 26, 2025

dannyroosevelt moved this to Ready for PR Review in Component (Source and Action) Backlog Nov 26, 2025

pipedream-component-development requested a review from GTFalcao November 26, 2025 17:23

coderabbitai bot reviewed Nov 26, 2025

View reviewed changes

components/trengo/actions/list-help-centers/list-help-centers.mjs Show resolved Hide resolved

coderabbitai bot reviewed Nov 26, 2025

View reviewed changes

components/trengo/trengo.app.mjs Outdated Show resolved Hide resolved

pipedream-component-development requested a review from michelle0927 November 26, 2025 20:50

michelle0927 mentioned this pull request Nov 26, 2025

[ACTION] trengo - Helpcenter #19277

Merged

pipedream-component-development requested a review from luancazarine November 26, 2025 21:22

update package version and remove unused methods

255da42

michelle0927 approved these changes Nov 26, 2025

View reviewed changes

michelle0927 moved this from Ready for PR Review to Ready for QA in Component (Source and Action) Backlog Nov 26, 2025

vunguyenhung moved this from Ready for QA to Changes Required in Component (Source and Action) Backlog Nov 27, 2025

jcortes requested review from jcortes and removed request for GTFalcao and luancazarine November 27, 2025 14:42

jcortes reviewed Nov 27, 2025

View reviewed changes

jcortes moved this from Changes Required to Ready for QA in Component (Source and Action) Backlog Nov 27, 2025

jcortes closed this Nov 28, 2025

github-project-automation bot moved this from Ready for QA to Done in Component (Source and Action) Backlog Nov 28, 2025

[ACTION] Trengo - Add Helpcenter API Methods and List Help Centers Action #19273

[ACTION] Trengo - Add Helpcenter API Methods and List Help Centers Action #19273

Uh oh!

Conversation

SIVALANAGASHANKARNIVAS commented Nov 26, 2025 • edited by coderabbitai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

WHY

Summary

API Methods Added:

Actions Added:

API Documentation

Summary by CodeRabbit

Release Notes

Uh oh!

vercel bot commented Nov 26, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pipedream-component-development commented Nov 26, 2025

Uh oh!

pipedream-component-development commented Nov 26, 2025

Uh oh!

coderabbitai bot commented Nov 26, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Sequence Diagram

Estimated code review effort

Pre-merge checks and finishing touches

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

michelle0927 left a comment

Choose a reason for hiding this comment

Uh oh!

vunguyenhung commented Nov 27, 2025

Uh oh!

vunguyenhung commented Nov 27, 2025

Uh oh!

jcortes left a comment

Choose a reason for hiding this comment

Uh oh!

vunguyenhung commented Nov 28, 2025

Uh oh!

jcortes commented Nov 28, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

SIVALANAGASHANKARNIVAS commented Nov 26, 2025 •

edited by coderabbitai bot

Loading

vercel bot commented Nov 26, 2025 •

edited

Loading

coderabbitai bot commented Nov 26, 2025 •

edited

Loading