Monta - bug fixes

[michelle0927]

Resolves #19519

Summary by CodeRabbit

• Bug Fixes

  • Fixed order and return data retrieval endpoints for improved API communication
  • Updated order list display to use correct order identifiers

• Chores

  • Updated package and component versions
  • Updated platform dependency to latest compatible version

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

[vercel]

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

1 Skipped Deployment

Project	Deployment	Review	Updated (UTC)
pipedream-docs-redirect-do-not-edit	Ignored		Dec 17, 2025 4:29pm

[coderabbitai]

Walkthrough

These changes fix two bugs in the Monta integration: correcting API endpoint paths from plural to singular forms (/orders/ → /order/, /returns/ → /return/) and updating the order list mapping to use WebshopOrderId instead of Id for proper order identification. Version numbers are bumped across action components and package metadata.

Changes

Cohort / File(s)	Summary
Action version bumps components/monta/actions/get-order/get-order.mjs, components/monta/actions/get-return/get-return.mjs, components/monta/actions/list-order-events/list-order-events.mjs	Version field updated from 0.0.1 to 0.0.2 in exported metadata across three action modules.
Package metadata updates components/monta/package.json	Package version bumped from 0.1.0 to 0.1.1; @pipedream/platform dependency updated from ^3.1.0 to ^3.1.1.
Monta app API and mapping fixes components/monta/monta.app.mjs	getOrder API path corrected from /orders/{orderId} to /order/{orderId}; getReturn API path corrected from /returns/{returnId} to /return/{returnId}; order list mapping changed to use WebshopOrderId instead of Id for option items.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• monta.app.mjs: Review the three API path corrections and mapping change to verify they align with the Monta API specification and resolve the reported bugs.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 2 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description only contains 'Resolves #19519' without following the template structure that requires a 'WHY' section with author-provided context.	Expand the description to include the 'WHY' section explaining the rationale for these changes, the bugs being fixed, and impact.
Title check	❓ Inconclusive	The title 'Monta - bug fixes' is related to changes but is vague and generic, using non-descriptive terms that don't convey specific details about which bugs were fixed.	Make the title more specific by mentioning the main bugs fixed, e.g., 'Monta: Fix order API route and update order ID mapping' or similar.
Out of Scope Changes check	❓ Inconclusive	Package version bump and dependency update appear tangential to bug fixes; other changes directly address the linked issue requirements.	Clarify whether the package version and dependency updates in package.json are necessary for these bug fixes or should be in a separate PR.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Changes address both bugs: API routes corrected from /orders/{id} to /order/{id} and /returns/{id} to /return/{id}, and order ID mapping switched from numeric ID to WebshopOrderId.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ 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-19519

---

📜 Recent review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6e9034e and 532ceff.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (5)

• components/monta/actions/get-order/get-order.mjs (1 hunks)
• components/monta/actions/get-return/get-return.mjs (1 hunks)
• components/monta/actions/list-order-events/list-order-events.mjs (1 hunks)
• components/monta/monta.app.mjs (2 hunks)
• components/monta/package.json (2 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2024-12-12T19:23:09.039Z

Learnt from: jcortes
Repo: PipedreamHQ/pipedream 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.

Applied to files:

• components/monta/package.json

⏰ 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: Lint Code Base
• GitHub Check: pnpm publish
• GitHub Check: Publish TypeScript components
• GitHub Check: Verify TypeScript components

🔇 Additional comments (8)

components/monta/package.json (2)

3-3: LGTM: Appropriate patch version bump.

The version increment from 0.1.0 to 0.1.1 correctly follows semantic versioning for bug fixes.

---

16-16: Version 3.1.1 of @pipedream/platform is available on npm and represents a standard patch update.

components/monta/actions/get-return/get-return.mjs (1)

7-7: LGTM: Appropriate version bump.

The version increment aligns with the bug fix release cycle.

components/monta/actions/get-order/get-order.mjs (1)

7-7: LGTM: Appropriate version bump.

The version increment aligns with the bug fix release cycle.

components/monta/actions/list-order-events/list-order-events.mjs (1)

7-7: LGTM: Appropriate version bump.

The version increment aligns with the bug fix release cycle.

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

11-21: Excellent fix: Using WebshopOrderId resolves the configureProp bug.

This change correctly addresses bug #2 from issue #19519. By using WebshopOrderId instead of Id, the configureProp now returns the external order identifier (e.g., "MP1") instead of the numeric internal ID (e.g., "286520610"), ensuring prefilled values work correctly with endpoints like /order/{id}/events.

---

54-61: Excellent fix: Corrected API endpoint path for getOrder.

This change correctly addresses bug #1 from issue #19519. By using the singular /order/ path instead of /orders/, the endpoint now matches the Monta API specification and returns 200 responses instead of 404 errors.

---

62-69: Excellent fix: Consistent API endpoint correction for getReturn.

This change correctly uses the singular /return/ path instead of /returns/, maintaining consistency with the getOrder fix and matching the Monta API specification. This prevents similar 404 errors for return operations.

---

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

[lcaresia]

LGTM!

[vunguyenhung]

Hi everyone, all test cases are passed! Ready for release!

Test reports

• [BUG] Monta can't find orders - Actions Batch 1: https://www.notion.so/BUG-Monta-can-t-find-orders-Actions-Batch-1-1-2ccbf548bb5e81eb8771e6917e0df83a