Agendor - fix prop name

[verhovsky]

data is sent to the API directly, so it needs to match the expected spelling to have an effect.

Summary by CodeRabbit

• Bug Fixes
  • Fixed a property naming inconsistency in the create-organization feature to ensure proper functionality and API compatibility.

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

[vercel[bot]]

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

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
pipedream-docs-redirect-do-not-edit	Ignored			Dec 2, 2025 7:08am

[pipedream-component-development]

Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified.

[pipedream-component-development]

Thanks for submitting this PR! When we review PRs, we follow the Pipedream component guidelines. If you're not familiar, here's a quick checklist:

• [ ] Create components to address specific use cases whenever possible
• [ ] Component keys should follow the format app_name_slug-slugified-component-name
• [ ] Components should follow the standard directory structure
• [ ] Prefer Node.js client libraries to REST APIs
• [ ] When making API requests, handle pagination to ensure all data / events are processed
• [ ] Use secret props to capture sensitive data
• [ ] Props and methods should be defined in app files whenever possible
• [ ] Document methods with JS Docs
• [ ] Use optional props whenever possible, and set a default value where you can
• [ ] Use async options to accept user input wherever possible

[coderabbitai[bot]]

Walkthrough

Version bumps and typo fix across the agendor component. A property name was corrected from onwerUser to ownerUser in the create-organization action, with corresponding version increments in both the action and package.json.

Changes

Cohort / File(s)	Summary
Property name correction and action version bump components/agendor/actions/create-organization/create-organization.mjs	Fixed typo: renamed property from onwerUser to ownerUser; updated action version from 0.0.2 to 0.0.3
Package version bump components/agendor/package.json	Updated version from 0.1.1 to 0.1.2

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Verify the property name correction is applied consistently and doesn't break existing dependencies
• Confirm version increments align with semantic versioning practices

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Agendor - fix prop name' clearly and concisely summarizes the main change: fixing a misspelled property name (onwerUser to ownerUser) in the Agendor component.
Description check	✅ Passed	The PR description is minimal but sufficient, explaining why the prop name fix matters (API data shape compatibility), though it lacks the structured sections from the template.
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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2583778d230c5c0345ceb907bc6b60b062173315 and ef1de0c734fdaa32d3e0cea3344675bc06739048.

📒 Files selected for processing (2)

• components/agendor/actions/create-organization/create-organization.mjs (2 hunks)
• components/agendor/package.json (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2024-10-30T15:24:39.294Z

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

Applied to files:

• components/agendor/actions/create-organization/create-organization.mjs

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

🔇 Additional comments (3)

components/agendor/package.json (1)

3-3: LGTM! Version bump is appropriate.

The patch version increment correctly reflects the typo fix in this PR.

components/agendor/actions/create-organization/create-organization.mjs (2)

7-7: LGTM! Version bump is appropriate.

The patch version increment correctly reflects the property name fix.

---

57-62: Unable to verify the typo fix and API integration context.

The repository could not be accessed to verify the claims in this review comment. Specifically, I cannot confirm:

• Whether the property name was actually corrected from onwerUser to ownerUser
• The context of the app.createOrganization() call at line 128
• Whether any remaining references to the old property name exist elsewhere in the codebase

The code snippet provided shows only the final state with ownerUser, not the original state. Manual verification of the change history or repository access is required to confirm this fix.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[vunguyenhung]

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

Test reports

• Agendor - fix prop name - Actions Batch 1: https://www.notion.so/Agendor-fix-prop-name-Actions-Batch-1-1-2bdbf548bb5e815fb349fd168a652b67