Freshchat - add props to send-message-in-chat

[michelle0927]

Resolves #18639

Summary by CodeRabbit

• New Features

  • Send messages as either a user or an agent, with an option to specify the agent ID.
  • Choose message type: normal or private (default: normal).
  • Added runtime validation to prevent misconfiguration when sending as an agent, with clearer error feedback.
  • Message payload now reflects selected actor and message type for accurate delivery.

• Chores

  • Bumped component versions for Freshchat action and package.

[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			Oct 13, 2025 7:42pm
pipedream-docs-redirect-do-not-edit	Ignored			Oct 13, 2025 7:42pm

[coderabbitai]

Walkthrough

Adds new parameters to the Freshchat "Send Message in Chat" action to support agent-sent and private messages, introduces runtime validation for agent usage, adjusts payload construction based on actor type, includes message_type, and bumps component and action versions.

Changes

Cohort / File(s)	Summary of Changes
Freshchat action enhancements components/freshchat/actions/send-message-in-chat/send-message-in-chat.mjs	Added new props: actorType ("user" | "agent"), optional agentId, and messageType ("normal" | "private", default "normal"). Introduced validation requiring agentId when actorType is "agent" (throws ConfigurationError). Updated payload to select actor_id from userId or agentId, set user_id undefined for agents, and include message_type. Version bumped 0.0.2→0.0.3.
Package version bump components/freshchat/package.json	Version updated 0.1.0→0.1.1.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor Dev as Caller
  participant Act as SendMessageInChat Action
  participant FC as Freshchat API

  Dev->>Act: Invoke with { actorType, agentId?, userId, messageType }
  rect rgb(245,245,255)
    note over Act: Validate inputs
    Act->>Act: if actorType=="agent" and no agentId<br/>throw ConfigurationError
  end
  alt Valid
    Act->>Act: Build payload<br/>actor_id = agentId|userId<br/>user_id = undefined|userId<br/>message_type = messageType
    Act->>FC: POST /messages (payload)
    FC-->>Act: Response
    Act-->>Dev: Result
  else Invalid (missing agentId)
    Act-->>Dev: Error (ConfigurationError)
  end

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I thump a paw: new knobs to tweak,
Agent or user—pick who’ll speak.
A private whisper, hush the chat,
Payload packed—precise and flat.
Version hops like springtime feet,
Fresh carrots shipped; the change is neat! 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description only includes a link to the resolved issue and does not follow the repository’s description template, which requires at minimum a “## WHY” section explaining the motivation and context for the changes.	Please update the description to follow the template by adding a “## WHY” section that outlines the rationale for adding the new actor_type, actor_id, and message_type parameters and any relevant usage details.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title clearly states that new properties are being added to the Freshchat send-message-in-chat action and directly reflects the main change in the code. It is concise, specific, and immediately conveys the purpose of the update.
Linked Issues Check	✅ Passed	The implementation adds the actorType, agentId, and messageType props along with runtime validation and payload adjustments exactly as requested in issue #18639, ensuring messages can be sent as either a user or agent and marked private when needed.
Out of Scope Changes Check	✅ Passed	All modifications are confined to the Freshchat send-message-in-chat action and its package version bump, directly supporting the addition of the requested parameters with no unrelated code changes.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch issue-18639

---

📜 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 7f84b6d and 55ebea2.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

• components/freshchat/actions/send-message-in-chat/send-message-in-chat.mjs (3 hunks)
• components/freshchat/package.json (1 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: Lint Code Base
• GitHub Check: pnpm publish

---

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.}

[luancazarine]

Hi @michelle0927, LGTM! Ready for QA!