feat(instant_reply): Add Instant Reply app — WhatsApp, Instagram & Messenger AI inbox#21089
Open
suleimandoescsec wants to merge 2 commits into
Open
feat(instant_reply): Add Instant Reply app — WhatsApp, Instagram & Messenger AI inbox#21089suleimandoescsec wants to merge 2 commits into
suleimandoescsec wants to merge 2 commits into
Conversation
Adds community integration for Instant Reply — a shared AI inbox for WhatsApp Business, Instagram DMs, and Facebook Messenger. Actions: - instant_reply-send-message: send free-form or template messages - instant_reply-create-contact: add a new contact to the inbox - instant_reply-update-contact: update contact fields and tags - instant_reply-add-note: attach internal notes to conversations Sources (triggers): - instant_reply-new-message: emit on every inbound message (60s poll) - instant_reply-new-lead: emit when a conversation is marked qualified (5m poll) Auth: API key (Bearer token via $auth.api_key) Fixes: #new-app
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
dannyroosevelt
moved this to Ready for PR Review
in Component (Source and Action) Backlog
Collaborator
|
Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified. |
Collaborator
Contributor
📝 WalkthroughWalkthroughAdds a new Instant Reply component: an authenticated app wrapper, multiple actions (messaging, contact management, campaigns, notes, journey trigger, lead-stage), four polling sources for webhook events, package manifest, and README documentation. ChangesInstant Reply Integration
Sequence Diagram(s)sequenceDiagram
participant Action as SendMessageAction
participant App as InstantReplyApp
participant API as Instant Reply API
Action->>App: this.instantReply.sendMessage(payload)
App->>API: POST /messages (Authorization: Bearer api_key)
API-->>App: response
App-->>Action: response
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 14
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@components/instant_reply/actions/add-note/add-note.mjs`:
- Around line 3-8: The exported action object (key "instant_reply-add-note") is
missing the required annotations object; add an annotations property to the
default export with readOnlyHint: false, destructiveHint: false, and
openWorldHint: true so the action correctly declares it creates data and makes
external API calls—update the object literal in the add-note module (the default
export) to include this annotations object.
In `@components/instant_reply/actions/create-contact/create-contact.mjs`:
- Around line 3-8: The exported action object (default export) is missing the
required annotations object; add an annotations property to the root exported
object with keys readOnlyHint: false, destructiveHint: false, and openWorldHint:
true so the "instant_reply-create-contact" action correctly declares it's a
writing action that makes external API calls; update the default export in
create-contact.mjs (the object containing key/name/description/version/type) to
include this annotations object.
In `@components/instant_reply/actions/send-message/send-message.mjs`:
- Around line 3-8: The exported action object (default export with key
"instant_reply-send-message" / name "Send Message") is missing the required
annotations object; add an annotations property to the exported object
containing { readOnlyHint: false, destructiveHint: false, openWorldHint: true }
so the runtime knows this action performs external API calls and mutates/sends
data.
- Around line 33-52: Remove the redundant hidden static prop declarations for
body, templateId, and templateVariables from the static props object and rely
only on the conditional definitions in additionalProps(); specifically delete
the entries named "body", "templateId", and "templateVariables" in the static
props block so that additionalProps() is the single source of truth for those
conditional props (leave additionalProps() and its definitions unchanged).
In `@components/instant_reply/actions/update-contact/update-contact.mjs`:
- Around line 3-8: The exported action object (key
"instant_reply-update-contact") is missing the required annotations object; add
an annotations property to the default export containing readOnlyHint: false,
destructiveHint: false, and openWorldHint: true so the action metadata correctly
reflects that it modifies data and makes external API calls.
In `@components/instant_reply/instant_reply.app.mjs`:
- Around line 144-149: Update getWebhookEvents to accept a $ parameter and
forward it into the internal request so the platform can attach request context
for logging and error propagation: modify the getWebhookEvents(signature) to
include ($ = {}) or ($, args = {}) and pass $ into the call to
this._makeRequest({ path: "/webhook-events", ...args, $ }) so callers (e.g.,
new-message.mjs/new-lead.mjs) can supply the $ request context; ensure the
change matches the pattern used by other app methods that call
this._makeRequest.
In `@components/instant_reply/package.json`:
- Line 3: The package.json "version" field in the instant_reply component is
incorrectly set to "0.1.0"; change it to "0.0.1" and ensure the same "version"
value is used in each action/source module file (update the version key in
create-contact.mjs, update-contact.mjs, send-message.mjs, and add-note.mjs) so
all new component files start at 0.0.1 per the component versioning guidelines.
In `@components/instant_reply/sources/new-lead/new-lead.mjs`:
- Line 7: The component's initial version is set incorrectly to "0.1.0"; update
the version field in the module metadata (the "version" entry in new-lead.mjs)
to "0.0.1" so the new component starts at the required initial version; locate
the literal version: "0.1.0" and replace it with "0.0.1".
- Line 6: The component description string in new-lead.mjs is missing the
required documentation link; update the description value (the description
property in the exported component object) to end with the markdown link "[See
the documentation](https://...)" pointing to the component docs (replace
https://... with the actual docs URL), ensuring the link is appended to the
existing sentence and preserves punctuation and spacing.
- Around line 39-45: The call to this.instantReply.getWebhookEvents currently
requests only the first page (limit: 100) and can drop older events if more than
100 leads appear between polls; update the logic around getWebhookEvents to
iterate through all pages in a single poll cycle (using the API's pagination
mechanism: page/cursor/offset) starting from since: new
Date(lastTs).toISOString() and aggregating results until the API indicates no
more pages, emitting all collected "lead.qualified" events; ensure you
propagate/advance the pagination token (or increment page/offset) from the
response and keep params.limit (or configurable page size) while preserving
lastTs usage for the poll boundary.
In `@components/instant_reply/sources/new-message/new-message.mjs`:
- Line 7: Change the component initial version from "0.1.0" to "0.0.1" by
updating the version field in the new-message component (the version: "0.1.0"
entry in new-message.mjs) so the component starts at the required initial
version "0.0.1".
- Line 51: Remove the redundant "|| undefined" fallback when building the
request payload: replace the property assignment that uses "channel:
this.channel || undefined" with simply "channel: this.channel" (locate the
object literal where channel is set in new-message.mjs). This relies on
`@pipedream/platform`'s axios behavior that strips undefined values and keeps the
payload cleaner; no other logic changes are required.
- Line 6: The component's description string (the description field in
new-message component) is missing the required documentation link; update the
description value so it ends with a markdown documentation link like "[See the
documentation](https://...)" (replace the ... with the correct docs URL)
ensuring the link is appended to the existing sentence and stays within the same
string literal.
- Around line 47-54: The current call to this.instantReply.getWebhookEvents with
params { type: "message.inbound", since: new Date(lastTs).toISOString(),
channel: this.channel || undefined, limit: 100 } only retrieves one page; change
the logic in the method that calls this.instantReply.getWebhookEvents (the
polling handler using lastTs and channel) to iterate and fetch all pages in a
loop: call getWebhookEvents repeatedly using the API's pagination mechanism
(e.g., nextCursor/nextPage token or page/offset param returned by
getWebhookEvents) until no more pages, accumulate all events before
processing/emitting them, and update lastTs based on the latest event timestamp
after all pages are fetched; ensure you handle empty pages, respect the existing
limit param, and surface or propagate any pagination token field returned by
getWebhookEvents.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 3ed8fa3e-0ee9-4082-be7d-85502fc6c447
📒 Files selected for processing (9)
components/instant_reply/README.mdcomponents/instant_reply/actions/add-note/add-note.mjscomponents/instant_reply/actions/create-contact/create-contact.mjscomponents/instant_reply/actions/send-message/send-message.mjscomponents/instant_reply/actions/update-contact/update-contact.mjscomponents/instant_reply/instant_reply.app.mjscomponents/instant_reply/package.jsoncomponents/instant_reply/sources/new-lead/new-lead.mjscomponents/instant_reply/sources/new-message/new-message.mjs
Comment on lines
+3
to
+8
| export default { | ||
| key: "instant_reply-add-note", | ||
| name: "Add Note to Conversation", | ||
| description: "Add an internal note to an Instant Reply conversation. Useful for logging external context (form submission data, payment status, CRM updates) alongside the conversation thread. [See the docs](https://www.instantreply.co/developers)", | ||
| version: "0.1.0", | ||
| type: "action", |
Contributor
There was a problem hiding this comment.
Add required annotations object.
Action components must include an annotations object. This action adds internal notes to conversations via POST /conversations/{id}/notes, so:
readOnlyHint: false(creates data)destructiveHint: false(adds a note; does not delete or irreversibly overwrite)openWorldHint: true(makes external API calls)
✅ Suggested fix
export default {
key: "instant_reply-add-note",
name: "Add Note to Conversation",
description: "Add an internal note to an Instant Reply conversation. Useful for logging external context (form submission data, payment status, CRM updates) alongside the conversation thread. [See the docs](https://www.instantreply.co/developers)",
version: "0.1.0",
type: "action",
+ annotations: {
+ readOnlyHint: false,
+ destructiveHint: false,
+ openWorldHint: true,
+ },
props: {🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/actions/add-note/add-note.mjs` around lines 3 - 8,
The exported action object (key "instant_reply-add-note") is missing the
required annotations object; add an annotations property to the default export
with readOnlyHint: false, destructiveHint: false, and openWorldHint: true so the
action correctly declares it creates data and makes external API calls—update
the object literal in the add-note module (the default export) to include this
annotations object.
Source: Coding guidelines
Comment on lines
+3
to
+8
| export default { | ||
| key: "instant_reply-create-contact", | ||
| name: "Create Contact", | ||
| description: "Create a new contact in your Instant Reply inbox. Use this to sync leads from forms, CRMs, or any trigger into Instant Reply. [See the docs](https://www.instantreply.co/developers)", | ||
| version: "0.1.0", | ||
| type: "action", |
Contributor
There was a problem hiding this comment.
Add required annotations object.
Action components must include an annotations object with readOnlyHint, destructiveHint, and openWorldHint fields. This action creates a new contact via an external API call, so:
readOnlyHint: false(writes data)destructiveHint: false(creates, does not delete or irreversibly overwrite)openWorldHint: true(makes external API calls)
✅ Suggested fix
export default {
key: "instant_reply-create-contact",
name: "Create Contact",
description: "Create a new contact in your Instant Reply inbox. Use this to sync leads from forms, CRMs, or any trigger into Instant Reply. [See the docs](https://www.instantreply.co/developers)",
version: "0.1.0",
type: "action",
+ annotations: {
+ readOnlyHint: false,
+ destructiveHint: false,
+ openWorldHint: true,
+ },
props: {🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/actions/create-contact/create-contact.mjs` around
lines 3 - 8, The exported action object (default export) is missing the required
annotations object; add an annotations property to the root exported object with
keys readOnlyHint: false, destructiveHint: false, and openWorldHint: true so the
"instant_reply-create-contact" action correctly declares it's a writing action
that makes external API calls; update the default export in create-contact.mjs
(the object containing key/name/description/version/type) to include this
annotations object.
Source: Coding guidelines
Comment on lines
+3
to
+8
| export default { | ||
| key: "instant_reply-send-message", | ||
| name: "Send Message", | ||
| description: "Send a WhatsApp, Instagram DM, or Messenger message to a contact. Use a free-form body within a 24-hour customer window, or pick a pre-approved template for outbound outreach. [See the docs](https://www.instantreply.co/developers)", | ||
| version: "0.1.0", | ||
| type: "action", |
Contributor
There was a problem hiding this comment.
Add required annotations object.
Action components must include an annotations object. This action sends messages via external messaging APIs (WhatsApp/Instagram/Messenger), so:
readOnlyHint: false(sends data)destructiveHint: false(sends messages; does not delete or irreversibly destroy data)openWorldHint: true(makes external API calls)
✅ Suggested fix
export default {
key: "instant_reply-send-message",
name: "Send Message",
description: "Send a WhatsApp, Instagram DM, or Messenger message to a contact. Use a free-form body within a 24-hour customer window, or pick a pre-approved template for outbound outreach. [See the docs](https://www.instantreply.co/developers)",
version: "0.1.0",
type: "action",
+ annotations: {
+ readOnlyHint: false,
+ destructiveHint: false,
+ openWorldHint: true,
+ },
props: {🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/actions/send-message/send-message.mjs` around lines
3 - 8, The exported action object (default export with key
"instant_reply-send-message" / name "Send Message") is missing the required
annotations object; add an annotations property to the exported object
containing { readOnlyHint: false, destructiveHint: false, openWorldHint: true }
so the runtime knows this action performs external API calls and mutates/sends
data.
Source: Coding guidelines
Comment on lines
+33
to
+52
| body: { | ||
| type: "string", | ||
| label: "Message Body", | ||
| description: "The text content of the message.", | ||
| hidden: true, | ||
| }, | ||
| templateId: { | ||
| propDefinition: [ | ||
| instantReply, | ||
| "templateId", | ||
| ], | ||
| hidden: true, | ||
| }, | ||
| templateVariables: { | ||
| type: "object", | ||
| label: "Template Variables", | ||
| description: "Key-value pairs for the template placeholders, e.g. `{ \"1\": \"Alice\", \"2\": \"order #123\" }`.", | ||
| optional: true, | ||
| hidden: true, | ||
| }, |
Contributor
There was a problem hiding this comment.
🧹 Nitpick | 🔵 Trivial | ⚡ Quick win
Remove redundant hidden props.
Props body, templateId, and templateVariables are declared in the static props object with hidden: true (lines 33-52) and then completely redefined in additionalProps() (lines 54-78). The static declarations serve no purpose here — additionalProps() alone should define these conditional props.
Simplify by removing the static hidden prop definitions.
♻️ Suggested fix
messageType: {
type: "string",
label: "Message Type",
description: "Send a free-form text message (only valid within 24 hours of the customer's last message) or a pre-approved template.",
options: [
{ label: "Free-form text", value: "text" },
{ label: "Template", value: "template" },
],
reloadProps: true,
},
- body: {
- type: "string",
- label: "Message Body",
- description: "The text content of the message.",
- hidden: true,
- },
- templateId: {
- propDefinition: [
- instantReply,
- "templateId",
- ],
- hidden: true,
- },
- templateVariables: {
- type: "object",
- label: "Template Variables",
- description: "Key-value pairs for the template placeholders, e.g. `{ \"1\": \"Alice\", \"2\": \"order `#123`\" }`.",
- optional: true,
- hidden: true,
- },
},
async additionalProps() {📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| body: { | |
| type: "string", | |
| label: "Message Body", | |
| description: "The text content of the message.", | |
| hidden: true, | |
| }, | |
| templateId: { | |
| propDefinition: [ | |
| instantReply, | |
| "templateId", | |
| ], | |
| hidden: true, | |
| }, | |
| templateVariables: { | |
| type: "object", | |
| label: "Template Variables", | |
| description: "Key-value pairs for the template placeholders, e.g. `{ \"1\": \"Alice\", \"2\": \"order #123\" }`.", | |
| optional: true, | |
| hidden: true, | |
| }, | |
| messageType: { | |
| type: "string", | |
| label: "Message Type", | |
| description: "Send a free-form text message (only valid within 24 hours of the customer's last message) or a pre-approved template.", | |
| options: [ | |
| { label: "Free-form text", value: "text" }, | |
| { label: "Template", value: "template" }, | |
| ], | |
| reloadProps: true, | |
| }, | |
| }, | |
| async additionalProps() { |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/actions/send-message/send-message.mjs` around lines
33 - 52, Remove the redundant hidden static prop declarations for body,
templateId, and templateVariables from the static props object and rely only on
the conditional definitions in additionalProps(); specifically delete the
entries named "body", "templateId", and "templateVariables" in the static props
block so that additionalProps() is the single source of truth for those
conditional props (leave additionalProps() and its definitions unchanged).
Comment on lines
+3
to
+8
| export default { | ||
| key: "instant_reply-update-contact", | ||
| name: "Update Contact", | ||
| description: "Update an existing contact's fields in Instant Reply. Use this to sync CRM updates, tag changes, or enriched data back into your inbox. [See the docs](https://www.instantreply.co/developers)", | ||
| version: "0.1.0", | ||
| type: "action", |
Contributor
There was a problem hiding this comment.
Add required annotations object.
Action components must include an annotations object. This action updates contact fields via PATCH /contacts/{id}, so:
readOnlyHint: false(modifies data)destructiveHint: false(updates are reversible; another update can restore previous values)openWorldHint: true(makes external API calls)
✅ Suggested fix
export default {
key: "instant_reply-update-contact",
name: "Update Contact",
description: "Update an existing contact's fields in Instant Reply. Use this to sync CRM updates, tag changes, or enriched data back into your inbox. [See the docs](https://www.instantreply.co/developers)",
version: "0.1.0",
type: "action",
+ annotations: {
+ readOnlyHint: false,
+ destructiveHint: false,
+ openWorldHint: true,
+ },
props: {🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/actions/update-contact/update-contact.mjs` around
lines 3 - 8, The exported action object (key "instant_reply-update-contact") is
missing the required annotations object; add an annotations property to the
default export containing readOnlyHint: false, destructiveHint: false, and
openWorldHint: true so the action metadata correctly reflects that it modifies
data and makes external API calls.
Source: Coding guidelines
Comment on lines
+39
to
+45
| const response = await this.instantReply.getWebhookEvents({ | ||
| params: { | ||
| type: "lead.qualified", | ||
| since: new Date(lastTs).toISOString(), | ||
| limit: 100, | ||
| }, | ||
| }); |
Contributor
There was a problem hiding this comment.
Implement pagination to fetch all new qualified leads.
The current implementation only fetches up to 100 events per poll (line 43) and does not handle pagination. If more than 100 leads are qualified between poll intervals, older events will be permanently skipped. As per coding guidelines: "For APIs that paginate, fetch/emit all pages of new items in a single poll cycle (don't stop after the first page)."
🔄 Recommended pagination pattern
async run() {
const lastTs = this._getLastTs();
let newLastTs = lastTs;
- const response = await this.instantReply.getWebhookEvents({
- params: {
- type: "lead.qualified",
- since: new Date(lastTs).toISOString(),
- limit: 100,
- },
- });
-
- const events = response?.data ?? [];
+ let page = 1;
+ let hasMore = true;
+
+ while (hasMore) {
+ const response = await this.instantReply.getWebhookEvents({
+ params: {
+ type: "lead.qualified",
+ since: new Date(lastTs).toISOString(),
+ limit: 100,
+ page,
+ },
+ });
+
+ const events = response?.data ?? [];
+ hasMore = events.length === 100;
+ page++;
- for (const event of events) {
- const ts = Date.parse(event.created_at);
- if (ts > lastTs) {
- this.$emit(event, this.generateMeta(event));
- if (ts > newLastTs) newLastTs = ts;
+ for (const event of events) {
+ const ts = Date.parse(event.created_at);
+ if (ts > lastTs) {
+ this.$emit(event, this.generateMeta(event));
+ if (ts > newLastTs) newLastTs = ts;
+ }
}
}
this._setLastTs(newLastTs);
},Note: Verify the Instant Reply API's pagination mechanism (page-based, cursor-based, or offset-based) and adjust accordingly.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/sources/new-lead/new-lead.mjs` around lines 39 - 45,
The call to this.instantReply.getWebhookEvents currently requests only the first
page (limit: 100) and can drop older events if more than 100 leads appear
between polls; update the logic around getWebhookEvents to iterate through all
pages in a single poll cycle (using the API's pagination mechanism:
page/cursor/offset) starting from since: new Date(lastTs).toISOString() and
aggregating results until the API indicates no more pages, emitting all
collected "lead.qualified" events; ensure you propagate/advance the pagination
token (or increment page/offset) from the response and keep params.limit (or
configurable page size) while preserving lastTs usage for the poll boundary.
Source: Coding guidelines
| export default { | ||
| key: "instant_reply-new-message", | ||
| name: "New Inbound Message", | ||
| description: "Emit an event each time a new inbound message arrives in your Instant Reply inbox — from WhatsApp, Instagram DM, or Messenger. Use this to trigger CRM updates, Slack notifications, or any downstream workflow.", |
Contributor
There was a problem hiding this comment.
Add required documentation link to component description.
As per coding guidelines, component description fields must end with [See the documentation](https://...). This link is required for all components.
📝 Suggested addition
- description: "Emit an event each time a new inbound message arrives in your Instant Reply inbox — from WhatsApp, Instagram DM, or Messenger. Use this to trigger CRM updates, Slack notifications, or any downstream workflow.",
+ description: "Emit an event each time a new inbound message arrives in your Instant Reply inbox — from WhatsApp, Instagram DM, or Messenger. Use this to trigger CRM updates, Slack notifications, or any downstream workflow. [See the documentation](https://www.instantreply.co/docs/api)",📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| description: "Emit an event each time a new inbound message arrives in your Instant Reply inbox — from WhatsApp, Instagram DM, or Messenger. Use this to trigger CRM updates, Slack notifications, or any downstream workflow.", | |
| description: "Emit an event each time a new inbound message arrives in your Instant Reply inbox — from WhatsApp, Instagram DM, or Messenger. Use this to trigger CRM updates, Slack notifications, or any downstream workflow. [See the documentation](https://www.instantreply.co/docs/api)", |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/sources/new-message/new-message.mjs` at line 6, The
component's description string (the description field in new-message component)
is missing the required documentation link; update the description value so it
ends with a markdown documentation link like "[See the
documentation](https://...)" (replace the ... with the correct docs URL)
ensuring the link is appended to the existing sentence and stays within the same
string literal.
Source: Coding guidelines
| key: "instant_reply-new-message", | ||
| name: "New Inbound Message", | ||
| description: "Emit an event each time a new inbound message arrives in your Instant Reply inbox — from WhatsApp, Instagram DM, or Messenger. Use this to trigger CRM updates, Slack notifications, or any downstream workflow.", | ||
| version: "0.1.0", |
Contributor
There was a problem hiding this comment.
Correct initial version to 0.0.1.
New components must start at version 0.0.1, not 0.1.0. As per coding guidelines: "new components start at 0.0.1".
🔧 Proposed fix
- version: "0.1.0",
+ version: "0.0.1",🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/sources/new-message/new-message.mjs` at line 7,
Change the component initial version from "0.1.0" to "0.0.1" by updating the
version field in the new-message component (the version: "0.1.0" entry in
new-message.mjs) so the component starts at the required initial version
"0.0.1".
Source: Coding guidelines
Comment on lines
+47
to
+54
| const response = await this.instantReply.getWebhookEvents({ | ||
| params: { | ||
| type: "message.inbound", | ||
| since: new Date(lastTs).toISOString(), | ||
| channel: this.channel || undefined, | ||
| limit: 100, | ||
| }, | ||
| }); |
Contributor
There was a problem hiding this comment.
Implement pagination to fetch all new events.
The current implementation only fetches up to 100 events per poll (line 52) and does not handle pagination. If more than 100 inbound messages arrive between poll intervals, older events will be permanently skipped. As per coding guidelines: "For APIs that paginate, fetch/emit all pages of new items in a single poll cycle (don't stop after the first page)."
🔄 Recommended pagination pattern
async run() {
const lastTs = this._getLastTs();
let newLastTs = lastTs;
- const response = await this.instantReply.getWebhookEvents({
- params: {
- type: "message.inbound",
- since: new Date(lastTs).toISOString(),
- channel: this.channel || undefined,
- limit: 100,
- },
- });
-
- const events = response?.data ?? [];
+ let page = 1;
+ let hasMore = true;
+
+ while (hasMore) {
+ const response = await this.instantReply.getWebhookEvents({
+ params: {
+ type: "message.inbound",
+ since: new Date(lastTs).toISOString(),
+ channel: this.channel || undefined,
+ limit: 100,
+ page,
+ },
+ });
+
+ const events = response?.data ?? [];
+ hasMore = events.length === 100;
+ page++;
- for (const event of events) {
- const ts = Date.parse(event.created_at);
- if (ts > lastTs) {
- this.$emit(event, this.generateMeta(event));
- if (ts > newLastTs) newLastTs = ts;
+ for (const event of events) {
+ const ts = Date.parse(event.created_at);
+ if (ts > lastTs) {
+ this.$emit(event, this.generateMeta(event));
+ if (ts > newLastTs) newLastTs = ts;
+ }
}
}
this._setLastTs(newLastTs);
},Note: Verify the Instant Reply API's pagination mechanism (page-based, cursor-based, or offset-based) and adjust accordingly.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/sources/new-message/new-message.mjs` around lines 47
- 54, The current call to this.instantReply.getWebhookEvents with params { type:
"message.inbound", since: new Date(lastTs).toISOString(), channel: this.channel
|| undefined, limit: 100 } only retrieves one page; change the logic in the
method that calls this.instantReply.getWebhookEvents (the polling handler using
lastTs and channel) to iterate and fetch all pages in a loop: call
getWebhookEvents repeatedly using the API's pagination mechanism (e.g.,
nextCursor/nextPage token or page/offset param returned by getWebhookEvents)
until no more pages, accumulate all events before processing/emitting them, and
update lastTs based on the latest event timestamp after all pages are fetched;
ensure you handle empty pages, respect the existing limit param, and surface or
propagate any pagination token field returned by getWebhookEvents.
Source: Coding guidelines
| params: { | ||
| type: "message.inbound", | ||
| since: new Date(lastTs).toISOString(), | ||
| channel: this.channel || undefined, |
Contributor
There was a problem hiding this comment.
🧹 Nitpick | 🔵 Trivial | 💤 Low value
Remove redundant || undefined fallback.
The @pipedream/platform axios implementation automatically strips undefined values from request parameters, so this.channel || undefined is equivalent to just this.channel. The explicit fallback adds no value.
♻️ Simplification
- channel: this.channel || undefined,
+ channel: this.channel,📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| channel: this.channel || undefined, | |
| channel: this.channel, |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/sources/new-message/new-message.mjs` at line 51,
Remove the redundant "|| undefined" fallback when building the request payload:
replace the property assignment that uses "channel: this.channel || undefined"
with simply "channel: this.channel" (locate the object literal where channel is
set in new-message.mjs). This relies on `@pipedream/platform`'s axios behavior
that strips undefined values and keeps the payload cleaner; no other logic
changes are required.
…tform features Actions added: list-conversations, get-conversation, send-campaign, update-lead-stage, trigger-journey Sources added: new-comment (Instagram/FB posts), campaign-completed app.mjs: fixed events endpoint path, added listCampaigns, listPipelineLeads, triggerJourney methods README updated with full feature coverage. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Actionable comments posted: 12
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@components/instant_reply/actions/get-conversation/get-conversation.mjs`:
- Around line 7-10: Update the action header: set version to "0.0.1" (it should
start at 0.0.1 for a new component) and add a required annotations block next to
the existing props block; for example add an annotations object with semantic
boolean keys such as public, system, and user (e.g., annotations: { public:
true, system: false, user: true }) so the action (referenced by the existing
props/instantReply and the get-conversation action) declares the semantic hints
expected by the component guidelines.
In `@components/instant_reply/actions/list-conversations/list-conversations.mjs`:
- Around line 7-10: Update the action metadata: change the version string from
"0.1.0" to "0.0.1" and add a top-level annotations object (next to
version/type/props) with the required boolean flags for this action (e.g.,
annotations: { /* semantic booleans */ }). Modify the file's header where the
symbols version and props (and the action definition in
components/instant_reply/actions/list-conversations/list-conversations.mjs) are
declared so the new annotations block is present and populated with semantically
correct boolean values.
In `@components/instant_reply/actions/send-campaign/send-campaign.mjs`:
- Around line 7-10: The action's metadata uses version "0.1.0" and is missing
the required annotations block; change the version field in this module to
"0.0.1" and add an annotations property next to props (near the instantReply
prop) containing the required boolean flags (use the semantically correct
booleans for this action per project conventions) so the action follows the
components/*/actions/** metadata conventions.
In `@components/instant_reply/actions/trigger-journey/trigger-journey.mjs`:
- Around line 7-10: The component's metadata must be initialized as a new
action: change the version from "0.1.0" to "0.0.1" and add an annotations object
alongside props (near the block containing props: { instantReply, }) that
includes the required semantic boolean flags (e.g., public, ui, or other
project-standard booleans) to declare this action's semantics; update the
top-level object where version/type/props are defined (the same block in
trigger-journey.mjs) to include annotations with correct booleans and the
downgraded version.
- Around line 16-27: Add a pre-call guard that validates the action inputs so
either triggerName or journeyId is provided (and non-empty) before calling the
downstream API: locate where the action reads props triggerName and journeyId
(the handler that performs the API call around the section using these
variables) and add a check that throws/returns a clear configuration error like
"Either triggerName or journeyId must be provided" if both are missing; apply
the same guard before the other API call block referenced in the comment (the
second block around lines 41–53) so invalid input fails fast with a descriptive
error instead of letting the request proceed.
In `@components/instant_reply/actions/update-lead-stage/update-lead-stage.mjs`:
- Around line 7-10: The component uses version: "0.1.0" and lacks the required
action metadata block; change the version to "0.0.1" and add an annotations
object for the action (e.g., a top-level annotations property near the existing
version/type/props) initializing the required boolean flags per action metadata
rules so the action is valid; update the file's version string and add the
annotations block alongside the existing version/type/props entries (referencing
the version and annotations symbols in the file).
In `@components/instant_reply/sources/campaign-completed/campaign-completed.mjs`:
- Line 7: This component's manifest sets the version field to "0.1.0" but new
source components must start at "0.0.1"; update the version key (version:
"0.1.0") in campaign-completed.mjs to version: "0.0.1" so the initial release
follows the project guideline for new components.
- Line 6: The component's description property (the "description" field in
campaign-completed.mjs) must be updated to append the required documentation
link; modify the description string so it ends with a docs link in the exact
format "[See the documentation](https://...)" (for example: description: "Emit
an event... [See the documentation](https://your-docs-link)"), preserving the
existing text and punctuation and ensuring there is a single space before the
bracketed link.
In `@components/instant_reply/sources/new-comment/new-comment.mjs`:
- Line 7: The version field currently reads "0.1.0" for the new source; update
the initial version string to "0.0.1" so the new component complies with the
guideline; locate the version property (version: "0.1.0") in new-comment.mjs and
change its value to "0.0.1" ensuring the quotes and syntax remain unchanged.
- Line 6: The component description string (the description property in
new-comment.mjs) must be updated to append the required docs link; modify the
description value so it ends with a space followed by "[See the
documentation](https://...)" (preserve the existing sentence and punctuation),
e.g., update the description property in the module to include that exact
markdown link at the end.
- Around line 64-70: The loop currently short-circuits on sentiment
(this.sentiment) before handling timestamps so filtered events never advance
newLastTs; move the timestamp parsing/ts logic ahead of the sentiment check and
always update newLastTs when ts > lastTs (e.g. newLastTs = Math.max(newLastTs,
ts)), then conditionally call this.$emit(event, this.generateMeta(event)) only
if the sentiment matches; reference the for (const event of events) loop,
this.sentiment, event.sentiment, ts, newLastTs, lastTs, this.$emit and
generateMeta when making the change.
- Around line 15-23: The property descriptions for the enum props platform and
sentiment are too generic; update the description text for the platform property
and the sentiment property so they include inline concrete examples matching
their options (e.g., platform: "Which platform to monitor for comments, e.g.
'instagram' or 'messenger'." and sentiment: "Only emit events for comments with
this sentiment, e.g. 'positive', 'neutral', or 'negative' — leave blank for
all."). Edit the description strings for the platform and sentiment fields in
the configuration object so the examples are explicit and match the options
arrays.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: a8f02add-1fb6-47a9-9bac-54c2a941d15a
📒 Files selected for processing (9)
components/instant_reply/README.mdcomponents/instant_reply/actions/get-conversation/get-conversation.mjscomponents/instant_reply/actions/list-conversations/list-conversations.mjscomponents/instant_reply/actions/send-campaign/send-campaign.mjscomponents/instant_reply/actions/trigger-journey/trigger-journey.mjscomponents/instant_reply/actions/update-lead-stage/update-lead-stage.mjscomponents/instant_reply/instant_reply.app.mjscomponents/instant_reply/sources/campaign-completed/campaign-completed.mjscomponents/instant_reply/sources/new-comment/new-comment.mjs
Comment on lines
+7
to
+10
| version: "0.1.0", | ||
| type: "action", | ||
| props: { | ||
| instantReply, |
Contributor
There was a problem hiding this comment.
Add required action annotations and initialize this new action at 0.0.1.
Line 7 uses version: "0.1.0" for a brand-new component, and there is no annotations block near Lines 8-10. Per the action/component guidelines, new components should start at 0.0.1 and actions should declare semantic hints.
Suggested patch
- version: "0.1.0",
+ version: "0.0.1",
type: "action",
+ annotations: {
+ openWorldHint: true,
+ readOnlyHint: true,
+ destructiveHint: false,
+ },As per coding guidelines, new components start at 0.0.1, and components/*/actions/**/*.mjs actions must include annotations with semantically correct booleans.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| version: "0.1.0", | |
| type: "action", | |
| props: { | |
| instantReply, | |
| version: "0.0.1", | |
| type: "action", | |
| annotations: { | |
| openWorldHint: true, | |
| readOnlyHint: true, | |
| destructiveHint: false, | |
| }, | |
| props: { | |
| instantReply, |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/actions/get-conversation/get-conversation.mjs`
around lines 7 - 10, Update the action header: set version to "0.0.1" (it should
start at 0.0.1 for a new component) and add a required annotations block next to
the existing props block; for example add an annotations object with semantic
boolean keys such as public, system, and user (e.g., annotations: { public:
true, system: false, user: true }) so the action (referenced by the existing
props/instantReply and the get-conversation action) declares the semantic hints
expected by the component guidelines.
Source: Coding guidelines
Comment on lines
+7
to
+10
| version: "0.1.0", | ||
| type: "action", | ||
| props: { | ||
| instantReply, |
Contributor
There was a problem hiding this comment.
Add required action annotations and initialize this new action at 0.0.1.
Line 7 sets version: "0.1.0" for a new action, and there is no annotations block near Lines 8-10. This should be corrected to match the action/component standards.
Suggested patch
- version: "0.1.0",
+ version: "0.0.1",
type: "action",
+ annotations: {
+ openWorldHint: true,
+ readOnlyHint: true,
+ destructiveHint: false,
+ },As per coding guidelines, new components start at 0.0.1, and components/*/actions/**/*.mjs actions must include annotations with semantically correct booleans.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| version: "0.1.0", | |
| type: "action", | |
| props: { | |
| instantReply, | |
| version: "0.0.1", | |
| type: "action", | |
| annotations: { | |
| openWorldHint: true, | |
| readOnlyHint: true, | |
| destructiveHint: false, | |
| }, | |
| props: { | |
| instantReply, |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/actions/list-conversations/list-conversations.mjs`
around lines 7 - 10, Update the action metadata: change the version string from
"0.1.0" to "0.0.1" and add a top-level annotations object (next to
version/type/props) with the required boolean flags for this action (e.g.,
annotations: { /* semantic booleans */ }). Modify the file's header where the
symbols version and props (and the action definition in
components/instant_reply/actions/list-conversations/list-conversations.mjs) are
declared so the new annotations block is present and populated with semantically
correct boolean values.
Source: Coding guidelines
Comment on lines
+7
to
+10
| version: "0.1.0", | ||
| type: "action", | ||
| props: { | ||
| instantReply, |
Contributor
There was a problem hiding this comment.
Add required action annotations and initialize this new action at 0.0.1.
Line 7 currently starts this new action at 0.1.0, and there is no annotations block near Lines 8-10. Both should be updated to align with required action metadata/versioning conventions.
Suggested patch
- version: "0.1.0",
+ version: "0.0.1",
type: "action",
+ annotations: {
+ openWorldHint: true,
+ readOnlyHint: false,
+ destructiveHint: false,
+ },As per coding guidelines, new components start at 0.0.1, and components/*/actions/**/*.mjs actions must include annotations with semantically correct booleans.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/actions/send-campaign/send-campaign.mjs` around
lines 7 - 10, The action's metadata uses version "0.1.0" and is missing the
required annotations block; change the version field in this module to "0.0.1"
and add an annotations property next to props (near the instantReply prop)
containing the required boolean flags (use the semantically correct booleans for
this action per project conventions) so the action follows the
components/*/actions/** metadata conventions.
Source: Coding guidelines
Comment on lines
+7
to
+10
| version: "0.1.0", | ||
| type: "action", | ||
| props: { | ||
| instantReply, |
Contributor
There was a problem hiding this comment.
Add required action annotations and initialize this new action at 0.0.1.
Line 7 sets 0.1.0 for a new component, and annotations are missing near Lines 8-10. This action should include semantic hint annotations and start at 0.0.1.
Suggested patch
- version: "0.1.0",
+ version: "0.0.1",
type: "action",
+ annotations: {
+ openWorldHint: true,
+ readOnlyHint: false,
+ destructiveHint: false,
+ },As per coding guidelines, new components start at 0.0.1, and components/*/actions/**/*.mjs actions must include annotations with semantically correct booleans.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/actions/trigger-journey/trigger-journey.mjs` around
lines 7 - 10, The component's metadata must be initialized as a new action:
change the version from "0.1.0" to "0.0.1" and add an annotations object
alongside props (near the block containing props: { instantReply, }) that
includes the required semantic boolean flags (e.g., public, ui, or other
project-standard booleans) to declare this action's semantics; update the
top-level object where version/type/props are defined (the same block in
trigger-journey.mjs) to include annotations with correct booleans and the
downgraded version.
Source: Coding guidelines
Comment on lines
+16
to
+27
| triggerName: { | ||
| type: "string", | ||
| label: "Journey Trigger Name", | ||
| description: "The stable slug you configured on the journey (e.g. 'new_signup', 'trial_expired'). Either this or Journey ID is required.", | ||
| optional: true, | ||
| }, | ||
| journeyId: { | ||
| type: "string", | ||
| label: "Journey ID", | ||
| description: "UUID of the WhatsApp journey. Use Trigger Name instead if you want a stable identifier that doesn't change when you recreate journeys.", | ||
| optional: true, | ||
| }, |
Contributor
There was a problem hiding this comment.
Validate triggerName/journeyId before the API call.
Both props are optional, but Line 19 says one is required. Add a pre-call guard so invalid input fails fast with a clear configuration error instead of an opaque downstream API failure.
Suggested patch
async run({ $ }) {
+ if (!this.triggerName && !this.journeyId) {
+ throw new Error("Provide either Journey Trigger Name or Journey ID.");
+ }
+
const response = await this.instantReply._makeRequest({
$,
method: "POST",As per coding guidelines, pre-call validation is the right place to handle user configuration mistakes for actions.
Also applies to: 41-53
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/actions/trigger-journey/trigger-journey.mjs` around
lines 16 - 27, Add a pre-call guard that validates the action inputs so either
triggerName or journeyId is provided (and non-empty) before calling the
downstream API: locate where the action reads props triggerName and journeyId
(the handler that performs the API call around the section using these
variables) and add a check that throws/returns a clear configuration error like
"Either triggerName or journeyId must be provided" if both are missing; apply
the same guard before the other API call block referenced in the comment (the
second block around lines 41–53) so invalid input fails fast with a descriptive
error instead of letting the request proceed.
Source: Coding guidelines
| key: "instant_reply-campaign-completed", | ||
| name: "Campaign Completed", | ||
| description: "Emit an event each time a broadcast campaign finishes sending. Use this to trigger post-campaign reports, CRM updates, or follow-up sequences.", | ||
| version: "0.1.0", |
Contributor
There was a problem hiding this comment.
Set the initial version to 0.0.1 for a new source component.
Line 7 uses 0.1.0, but this is a newly added component and should start at 0.0.1.
Suggested fix
- version: "0.1.0",
+ version: "0.0.1",As per coding guidelines, “new components start at 0.0.1.”
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| version: "0.1.0", | |
| version: "0.0.1", |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/sources/campaign-completed/campaign-completed.mjs`
at line 7, This component's manifest sets the version field to "0.1.0" but new
source components must start at "0.0.1"; update the version key (version:
"0.1.0") in campaign-completed.mjs to version: "0.0.1" so the initial release
follows the project guideline for new components.
Source: Coding guidelines
| export default { | ||
| key: "instant_reply-new-comment", | ||
| name: "New Comment Received", | ||
| description: "Emit an event each time a new comment is received on one of your Instagram or Facebook posts. Use this to trigger auto-replies, sentiment alerts, or CRM tagging workflows.", |
Contributor
There was a problem hiding this comment.
Append the required docs link to the component description.
Line 6 needs to end with [See the documentation](https://...).
Suggested fix
- description: "Emit an event each time a new comment is received on one of your Instagram or Facebook posts. Use this to trigger auto-replies, sentiment alerts, or CRM tagging workflows.",
+ description: "Emit an event each time a new comment is received on one of your Instagram or Facebook posts. Use this to trigger auto-replies, sentiment alerts, or CRM tagging workflows. [See the documentation](https://www.instantreply.co/docs)",As per coding guidelines, component description must end with [See the documentation](https://...).
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| description: "Emit an event each time a new comment is received on one of your Instagram or Facebook posts. Use this to trigger auto-replies, sentiment alerts, or CRM tagging workflows.", | |
| description: "Emit an event each time a new comment is received on one of your Instagram or Facebook posts. Use this to trigger auto-replies, sentiment alerts, or CRM tagging workflows. [See the documentation](https://www.instantreply.co/docs)", |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/sources/new-comment/new-comment.mjs` at line 6, The
component description string (the description property in new-comment.mjs) must
be updated to append the required docs link; modify the description value so it
ends with a space followed by "[See the documentation](https://...)" (preserve
the existing sentence and punctuation), e.g., update the description property in
the module to include that exact markdown link at the end.
Source: Coding guidelines
| key: "instant_reply-new-comment", | ||
| name: "New Comment Received", | ||
| description: "Emit an event each time a new comment is received on one of your Instagram or Facebook posts. Use this to trigger auto-replies, sentiment alerts, or CRM tagging workflows.", | ||
| version: "0.1.0", |
Contributor
There was a problem hiding this comment.
Set the initial version to 0.0.1 for this new source.
Line 7 should start at 0.0.1 since this component is newly introduced.
Suggested fix
- version: "0.1.0",
+ version: "0.0.1",As per coding guidelines, “new components start at 0.0.1.”
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/sources/new-comment/new-comment.mjs` at line 7, The
version field currently reads "0.1.0" for the new source; update the initial
version string to "0.0.1" so the new component complies with the guideline;
locate the version property (version: "0.1.0") in new-comment.mjs and change its
value to "0.0.1" ensuring the quotes and syntax remain unchanged.
Source: Coding guidelines
Comment on lines
+15
to
+23
| description: "Which platform to monitor for comments", | ||
| options: ["instagram", "messenger"], | ||
| optional: true, | ||
| }, | ||
| sentiment: { | ||
| type: "string", | ||
| label: "Sentiment Filter", | ||
| description: "Only emit events for comments with this sentiment. Leave blank for all.", | ||
| options: ["positive", "neutral", "negative"], |
Contributor
There was a problem hiding this comment.
Make enum prop descriptions explicit with inline examples for agent use.
Lines 15 and 22 are generic; include concrete enum examples directly in each description to improve agent reliability.
Suggested fix
- description: "Which platform to monitor for comments",
+ description: "Platform to monitor for comment events. Example: `instagram` or `messenger`.",
@@
- description: "Only emit events for comments with this sentiment. Leave blank for all.",
+ description: "Only emit comments matching this sentiment. Example: `positive`, `neutral`, or `negative`. Leave blank to emit all sentiments.",As per coding guidelines, prop descriptions should be agent-friendly and include concrete inline examples for enums.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/sources/new-comment/new-comment.mjs` around lines 15
- 23, The property descriptions for the enum props platform and sentiment are
too generic; update the description text for the platform property and the
sentiment property so they include inline concrete examples matching their
options (e.g., platform: "Which platform to monitor for comments, e.g.
'instagram' or 'messenger'." and sentiment: "Only emit events for comments with
this sentiment, e.g. 'positive', 'neutral', or 'negative' — leave blank for
all."). Edit the description strings for the platform and sentiment fields in
the configuration object so the examples are explicit and match the options
arrays.
Source: Coding guidelines
Comment on lines
+64
to
+70
| for (const event of events) { | ||
| if (this.sentiment && event.sentiment !== this.sentiment) continue; | ||
| const ts = Date.parse(event.created_at); | ||
| if (ts > lastTs) { | ||
| this.$emit(event, this.generateMeta(event)); | ||
| if (ts > newLastTs) newLastTs = ts; | ||
| } |
Contributor
There was a problem hiding this comment.
Advance checkpoint even for sentiment-filtered events.
Line 65 short-circuits before timestamp handling, so skipped events don’t move newLastTs. This can cause repeated polling of the same events and starvation of older matching events behind the limit window.
Suggested fix
for (const event of events) {
- if (this.sentiment && event.sentiment !== this.sentiment) continue;
const ts = Date.parse(event.created_at);
- if (ts > lastTs) {
- this.$emit(event, this.generateMeta(event));
- if (ts > newLastTs) newLastTs = ts;
- }
+ if (ts > newLastTs) newLastTs = ts;
+ if (ts <= lastTs) continue;
+ if (this.sentiment && event.sentiment !== this.sentiment) continue;
+ this.$emit(event, this.generateMeta(event));
}Based on learnings, checkpoint/cursor state should be updated for both emitted and non-emitted items to avoid replay; as per coding guidelines, polling sources should store cursor state to prevent re-emitting old events.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@components/instant_reply/sources/new-comment/new-comment.mjs` around lines 64
- 70, The loop currently short-circuits on sentiment (this.sentiment) before
handling timestamps so filtered events never advance newLastTs; move the
timestamp parsing/ts logic ahead of the sentiment check and always update
newLastTs when ts > lastTs (e.g. newLastTs = Math.max(newLastTs, ts)), then
conditionally call this.$emit(event, this.generateMeta(event)) only if the
sentiment matches; reference the for (const event of events) loop,
this.sentiment, event.sentiment, ts, newLastTs, lastTs, this.$emit and
generateMeta when making the change.
Sources: Coding guidelines, Learnings
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is Instant Reply?
Instant Reply is a shared AI inbox for WhatsApp Business, Instagram DMs, and Facebook Messenger. Teams use it to qualify leads, automate replies with AI, send broadcasts, and sync conversations to HubSpot or Pipedrive.
What this PR adds
Actions
instant_reply-send-messageinstant_reply-create-contactinstant_reply-update-contactinstant_reply-add-noteSources (Triggers)
instant_reply-new-messageinstant_reply-new-leadAuthentication
API key — users generate their key at
instantreply.co/dashboard/settings/api. Connects viaAuthorization: Bearerheader.Example use cases
Checklist
type: "app"andpropDefinitions$.export("$summary", ...)dedupe: "unique"and poll via$.service.dbpackage.jsonmatches Pipedream conventions (@pipedream/platform ^1.6.8)$auth.api_keySummary by CodeRabbit
New Features
Documentation