Skip to content

Conversation

@michelle0927
Copy link
Collaborator

@michelle0927 michelle0927 commented Jul 28, 2025

Resolves #17432

  • Added action "Create Note"
  • Source "New Note Created" already exists for Hubspot
  • Snippets are not accessible through the Hubspot API

Summary by CodeRabbit

  • New Features
    • Added the ability to create notes in HubSpot CRM, including support for associating notes with other HubSpot objects and specifying association types.
  • Chores
    • Updated the HubSpot integration version to 1.3.0.

@vercel
Copy link

vercel bot commented Jul 28, 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 28, 2025 5:49pm
pipedream-docs ⬜️ Ignored (Inspect) Jul 28, 2025 5:49pm
pipedream-docs-redirect-do-not-edit ⬜️ Ignored (Inspect) Jul 28, 2025 5:49pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 28, 2025

Walkthrough

A new HubSpot action module for creating notes has been added, allowing users to create note objects in HubSpot CRM and optionally associate them with other objects. The module includes input validation, property formatting, and API interaction logic. Additionally, the package version was incremented from 1.2.4 to 1.3.0.

Changes

Cohort / File(s) Change Summary
New "Create Note" Action
components/hubspot/actions/create-note/create-note.mjs
Introduced a new HubSpot action module for creating notes, including support for associations, input validation, and API integration.
Package Version Bump
components/hubspot/package.json
Updated package version from 1.2.4 to 1.3.0.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CreateNoteAction
    participant HubSpotAPI

    User->>CreateNoteAction: Provide note details and optional associations
    CreateNoteAction->>CreateNoteAction: Validate input and format properties
    CreateNoteAction->>HubSpotAPI: POST /crm/v3/objects/notes with note data
    HubSpotAPI-->>CreateNoteAction: Return created note object
    CreateNoteAction-->>User: Return summary and created note
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Assessment against linked issues

Objective Addressed Explanation
Add note → /crm/v3/objects/notes (#17432)
List snippets, Create or update snippet, Delete snippet (#17432) No changes related to snippet listing, creation, update, or deletion are present.

Assessment against linked issues: Out-of-scope changes

Code Change Explanation
Package version bump from 1.2.4 to 1.3.0 (components/hubspot/package.json) The version bump is not directly required for the "Add note" action, but is a standard practice for new features.

Poem

A note in the HubSpot garden grows,
With code and care, a new action shows.
Associations linked, reminders set,
CRM tasks are easier yet!
Version bumped, the change is neat—
This bunny hops to a productive beat! 🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch issue-17432

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 generate unit tests to generate unit tests for 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
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 (1)
components/hubspot/actions/create-note/create-note.mjs (1)

67-82: LGTM! Good validation logic with minor suggestion.

The function properly destructures props and validates that association parameters are provided together. Consider making the error message more descriptive for better user experience.

-      throw new ConfigurationError("Both `toObjectId` and `associationType` must be entered");
+      throw new ConfigurationError("Both `Associated Object` and `Association Type` must be provided together, or neither should be provided");
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 28e91bb and c189bda.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (2)
  • components/hubspot/actions/create-note/create-note.mjs (1 hunks)
  • components/hubspot/package.json (1 hunks)
🧰 Additional context used
🧠 Learnings (2)
components/hubspot/package.json (1)

Learnt from: jcortes
PR: #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/hubspot/actions/create-note/create-note.mjs (1)

Learnt from: jcortes
PR: #14467
File: components/gainsight_px/actions/create-account/create-account.mjs:4-6
Timestamp: 2024-10-30T15:24:39.294Z
Learning: In components/gainsight_px/actions/create-account/create-account.mjs, the action name should be "Create Account" instead of "Create Memory".

🧬 Code Graph Analysis (1)
components/hubspot/actions/create-note/create-note.mjs (1)
components/hubspot/common/constants.mjs (1)
  • ASSOCIATION_CATEGORY (31-35)
⏰ 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: pnpm publish
  • GitHub Check: Lint Code Base
  • GitHub Check: Publish TypeScript components
  • GitHub Check: Verify TypeScript components
🔇 Additional comments (8)
components/hubspot/package.json (1)

3-3: LGTM! Version bump aligns with new functionality.

The minor version increment from 1.2.4 to 1.3.0 appropriately reflects the addition of the new "Create Note" action, following semantic versioning conventions.

components/hubspot/actions/create-note/create-note.mjs (7)

1-3: LGTM! Proper imports for the action.

The imports correctly bring in the common create functionality, error handling, and the necessary constants. The use of relative paths and platform utilities follows Pipedream conventions.


5-11: LGTM! Well-structured action metadata.

The action follows Pipedream conventions with proper key naming, descriptive name matching the PR objectives, documentation reference, and appropriate versioning for a new action.


12-47: LGTM! Well-designed props with proper dependencies.

The props structure effectively uses Pipedream's propDefinition pattern to create dependent dropdowns. The optional association props (toObjectType, toObjectId, associationType) work together logically, with proper dependency relationships.


48-66: LGTM! Methods correctly implement note-specific logic.

The methods properly extend common functionality with note-specific behavior. The isRelevantProperty method appropriately filters out pipeline properties, and createEngagement correctly structures the HubSpot API call.


83-87: LGTM! Flexible property handling.

The code properly handles objectProperties as either a JSON string or object, providing good flexibility for users while maintaining the existing otherProperties fallback pattern.


91-105: LGTM! Correct association structure for HubSpot API.

The associations array is properly structured according to HubSpot's API requirements, using the imported ASSOCIATION_CATEGORY constant and conditional creation based on toObjectId presence.


111-116: LGTM! Proper API call and response handling.

The function correctly calls the createEngagement method, exports an appropriate summary message, and returns the engagement object as expected.

Copy link
Collaborator

@jcortes jcortes left a comment

Choose a reason for hiding this comment

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

Hi @michelle0927 lgtm! Ready for QA!

@vunguyenhung vunguyenhung merged commit 87fb36e into master Aug 1, 2025
11 checks passed
@vunguyenhung vunguyenhung deleted the issue-17432 branch August 1, 2025 00:37
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.

Hubspot

4 participants