Skip to content

New Components - harpa_ai #17690

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

New Components - harpa_ai #17690

wants to merge 2 commits into from

Conversation

michelle0927
Copy link
Collaborator

@michelle0927 michelle0927 commented Jul 17, 2025

Resolves #17565

Summary by CodeRabbit

  • New Features

    • Added "Run AI Command" action for executing AI commands on specified URLs with customizable parameters.
    • Introduced "Scrape Web Page" action to extract content from web pages, supporting targeted element selection.
    • Added "Search the Web" action to perform web searches using Harpa AI.
  • Improvements

    • Enhanced configuration options with new parameters for node selection, timeout, and results webhook.
    • Improved integration with Harpa AI services for streamlined requests and responses.
  • Chores

    • Updated package dependencies and version.

Copy link
Contributor

coderabbitai bot commented Jul 17, 2025

Walkthrough

This update introduces Harpa AI integration with three new action modules: "Run AI Command," "Search the Web," and "Scrape Web Page." It also adds utility functions, expands the app's property definitions and methods, and updates dependencies. The changes enable structured API interactions for automating web tasks, searching, and content extraction.

Changes

Files/Paths Change Summary
components/harpa_ai/actions/run-ai-command/run-ai-command.mjs Added "Run AI Command" action module for executing AI commands on URLs with configurable parameters.
components/harpa_ai/actions/scrape-web-page/scrape-web-page.mjs Added "Scrape Web Page" action module for scraping content or elements from web pages.
components/harpa_ai/actions/search-the-web/search-the-web.mjs Added "Search the Web" action module for performing web searches via Harpa AI.
components/harpa_ai/common/utils.mjs Introduced a recursive parseObject utility for parsing and normalizing input data.
components/harpa_ai/harpa_ai.app.mjs Added axios import, new propDefinitions (node, timeout, resultsWebhook), and API helper methods.
components/harpa_ai/package.json Updated version to 0.1.0, added @pipedream/platform dependency.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant ActionModule
    participant HarpaAIApp
    participant HarpaAIAPI

    User->>ActionModule: Trigger action (Run AI Command / Search / Scrape)
    ActionModule->>HarpaAIApp: sendAction({ parameters })
    HarpaAIApp->>HarpaAIAPI: POST /grid with parameters
    HarpaAIAPI-->>HarpaAIApp: Response
    HarpaAIApp-->>ActionModule: Response
    ActionModule-->>User: Summary & response
Loading

Poem

(\(\
( -.-) Three new actions hop in with cheer,
o_(")(") Harpa AI’s magic is finally here!
Search, scrape, or command—just say the word,
The web obeys, your wish inferred.
With clever code and bunny delight,
Automate your tasks—fast as light!

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

components/harpa_ai/actions/scrape-web-page/scrape-web-page.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:202:49)

components/harpa_ai/actions/run-ai-command/run-ai-command.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:202:49)

components/harpa_ai/actions/search-the-web/search-the-web.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:202:49)

  • 2 others
✨ 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.

Copy link

vercel bot commented Jul 17, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments
Name Status Preview Comments Updated (UTC)
docs-v2 ⬜️ Ignored (Inspect) Jul 17, 2025 8:05pm
pipedream-docs ⬜️ Ignored (Inspect) Jul 17, 2025 8:05pm
pipedream-docs-redirect-do-not-edit ⬜️ Ignored (Inspect) Jul 17, 2025 8:05pm

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (5)
components/harpa_ai/actions/run-ai-command/run-ai-command.mjs (1)

23-28: Consider adding input validation for the inputs array.

The inputs prop accepts a string array but lacks validation. Invalid input could cause issues when parsed by parseObject.

Consider adding validation:

 inputs: {
   type: "string[]",
   label: "Inputs",
   description: "An array of Strings, each one passed down into command in place of the user input. Inputs are used to bypass waiting for the user input in multi-step commands. For example [ \"REPORT\", \"DONE\" ] for the Summary command.",
   optional: true,
+  validate: (value) => {
+    if (value && !Array.isArray(value)) {
+      throw new Error("Inputs must be an array");
+    }
+    return true;
+  },
 },
components/harpa_ai/actions/scrape-web-page/scrape-web-page.mjs (1)

17-22: Consider adding validation for the grab selectors array.

Similar to the inputs array in run-ai-command, the grab prop could benefit from input validation to ensure it's a proper array of CSS selectors.

Consider adding validation:

 grab: {
   type: "string[]",
   label: "Grab",
   description: "An array of HTML Element selectors to scrape from the page. Refer to the [Scraping Web Page Elements and Data](https://harpa.ai/grid/grid-rest-api-reference#scraping-web-page-elements-and-data) section for more details.",
   optional: true,
+  validate: (value) => {
+    if (value && !Array.isArray(value)) {
+      throw new Error("Grab must be an array of CSS selectors");
+    }
+    return true;
+  },
 },
components/harpa_ai/actions/search-the-web/search-the-web.mjs (1)

11-15: Consider adding validation for the query parameter.

The query parameter is required but lacks validation for empty strings or overly long queries that might cause API issues.

Consider adding validation:

 query: {
   type: "string",
   label: "Query",
   description: "The search term or a query string to search for. Supports search parameters like **site:example.com** or **intitle:keyword**.",
+  validate: (value) => {
+    if (!value || value.trim().length === 0) {
+      throw new Error("Query cannot be empty");
+    }
+    if (value.length > 1000) {
+      throw new Error("Query is too long");
+    }
+    return true;
+  },
 },
components/harpa_ai/harpa_ai.app.mjs (2)

13-17: Consider using integer type for timeout property.

The timeout property should use integer type instead of string since it represents a duration value. This provides better type safety and validation.

-    timeout: {
-      type: "string",
-      label: "Timeout",
-      description: "Synchronous action execution timeout",
-      optional: true,
-    },
+    timeout: {
+      type: "integer",
+      label: "Timeout",
+      description: "Synchronous action execution timeout (in seconds)",
+      optional: true,
+      min: 1,
+    },

35-38: Fix header casing for Content-Type.

The Content-Type header should use proper casing according to HTTP standards.

-          "Content-type": "application/json",
+          "Content-Type": "application/json",
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 50c8bfe and b11dcbb.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (6)
  • components/harpa_ai/actions/run-ai-command/run-ai-command.mjs (1 hunks)
  • components/harpa_ai/actions/scrape-web-page/scrape-web-page.mjs (1 hunks)
  • components/harpa_ai/actions/search-the-web/search-the-web.mjs (1 hunks)
  • components/harpa_ai/common/utils.mjs (1 hunks)
  • components/harpa_ai/harpa_ai.app.mjs (1 hunks)
  • components/harpa_ai/package.json (2 hunks)
🧰 Additional context used
🧠 Learnings (4)
components/harpa_ai/package.json (1)
Learnt from: jcortes
PR: PipedreamHQ/pipedream#14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like `fs` to `package.json` dependencies, as they are native modules provided by the Node.js runtime.
components/harpa_ai/actions/run-ai-command/run-ai-command.mjs (2)
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12731
File: components/hackerone/actions/get-members/get-members.mjs:3-28
Timestamp: 2024-10-08T15:33:38.240Z
Learning: When exporting a summary message in the `run` method of an action, ensure the message is correctly formatted. For example, in the `hackerone-get-members` action, the correct format is `Successfully retrieved ${response.data.length} members`.
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12731
File: components/hackerone/actions/get-members/get-members.mjs:3-28
Timestamp: 2024-07-04T18:11:59.822Z
Learning: When exporting a summary message in the `run` method of an action, ensure the message is correctly formatted. For example, in the `hackerone-get-members` action, the correct format is `Successfully retrieved ${response.data.length} members`.
components/harpa_ai/actions/scrape-web-page/scrape-web-page.mjs (2)
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12731
File: components/hackerone/actions/get-members/get-members.mjs:3-28
Timestamp: 2024-07-04T18:11:59.822Z
Learning: When exporting a summary message in the `run` method of an action, ensure the message is correctly formatted. For example, in the `hackerone-get-members` action, the correct format is `Successfully retrieved ${response.data.length} members`.
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12731
File: components/hackerone/actions/get-members/get-members.mjs:3-28
Timestamp: 2024-10-08T15:33:38.240Z
Learning: When exporting a summary message in the `run` method of an action, ensure the message is correctly formatted. For example, in the `hackerone-get-members` action, the correct format is `Successfully retrieved ${response.data.length} members`.
components/harpa_ai/harpa_ai.app.mjs (4)
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12697
File: components/salesforce_rest_api/sources/common-webhook-methods.mjs:1-71
Timestamp: 2024-10-08T15:33:38.240Z
Learning: The `common-webhook-methods.mjs` object is designed to be extended, similar to an abstract class, and intentionally does not implement certain methods like `generateWebhookMeta` and `getEventType` to enforce implementation in subclasses.
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#12697
File: components/salesforce_rest_api/sources/common-webhook-methods.mjs:1-71
Timestamp: 2024-07-24T02:06:47.016Z
Learning: The `common-webhook-methods.mjs` object is designed to be extended, similar to an abstract class, and intentionally does not implement certain methods like `generateWebhookMeta` and `getEventType` to enforce implementation in subclasses.
Learnt from: GTFalcao
PR: PipedreamHQ/pipedream#16954
File: components/salesloft/salesloft.app.mjs:14-23
Timestamp: 2025-06-04T17:52:05.780Z
Learning: In the Salesloft API integration (components/salesloft/salesloft.app.mjs), the _makeRequest method returns response.data which directly contains arrays for list endpoints like listPeople, listCadences, listUsers, and listAccounts. The propDefinitions correctly call .map() directly on these responses without needing to destructure a nested data property.
Learnt from: js07
PR: PipedreamHQ/pipedream#17375
File: components/zerobounce/actions/get-validation-results-file/get-validation-results-file.mjs:23-27
Timestamp: 2025-07-01T17:07:48.193Z
Learning: For "dir" props in Pipedream components, whether to mark them as optional depends on the action's file I/O behavior - if an action always writes files as output, the "dir" prop should not be marked as optional.
🧬 Code Graph Analysis (2)
components/harpa_ai/actions/run-ai-command/run-ai-command.mjs (3)
components/harpa_ai/actions/search-the-web/search-the-web.mjs (1)
  • response (36-45)
components/harpa_ai/actions/scrape-web-page/scrape-web-page.mjs (1)
  • response (43-53)
components/harpa_ai/common/utils.mjs (2)
  • parseObject (1-25)
  • parseObject (1-25)
components/harpa_ai/actions/search-the-web/search-the-web.mjs (2)
components/harpa_ai/actions/scrape-web-page/scrape-web-page.mjs (1)
  • response (43-53)
components/harpa_ai/actions/run-ai-command/run-ai-command.mjs (1)
  • response (61-74)
🔇 Additional comments (8)
components/harpa_ai/package.json (2)

3-3: Appropriate version bump for new features.

The version update from "0.0.1" to "0.1.0" correctly reflects the addition of new action components and functionality.


15-17: Correct dependency addition.

The addition of @pipedream/platform as a dependency is appropriate for the new HTTP request functionality used in the action components.

components/harpa_ai/actions/run-ai-command/run-ai-command.mjs (1)

60-77: Well-structured action implementation.

The action follows Pipedream best practices with proper async/await handling, consistent parameter passing, and appropriate summary message formatting.

components/harpa_ai/actions/scrape-web-page/scrape-web-page.mjs (1)

42-56: Consistent action implementation.

The action follows the same pattern as other Harpa AI actions with proper use of sendAction, parseObject, and summary export.

components/harpa_ai/actions/search-the-web/search-the-web.mjs (1)

35-48: Clean and consistent implementation.

The action follows the established pattern with proper use of sendAction and maintains consistency with other Harpa AI actions.

components/harpa_ai/harpa_ai.app.mjs (3)

1-1: LGTM!

The import statement correctly uses the Pipedream platform axios module.


27-29: LGTM!

The base URL method is correctly implemented and follows standard Pipedream patterns.


42-48: LGTM!

The sendAction method is well-implemented, correctly using the private _makeRequest method with appropriate defaults and customization options.

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.

[Components] Harpa AI
2 participants