Skip to content

Conversation

@jocarino
Copy link
Contributor

@jocarino jocarino commented May 29, 2025

WHY

Adding missing actions for zoom admin
Listing past meeting participants
Get meeting recordings

Summary by CodeRabbit

  • New Features
    • Added the ability to fetch all recordings for a specific Zoom meeting, with optional download access tokens.
    • Introduced functionality to list all participants of a past Zoom meeting.

@vercel
Copy link

vercel bot commented May 29, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
pipedream-docs-redirect-do-not-edit ⬜️ Ignored (Inspect) May 30, 2025 3:21pm

@vercel
Copy link

vercel bot commented May 29, 2025

Someone is attempting to deploy a commit to the Pipedreamers Team on Vercel.

A member of the Team first needs to authorize it.

@adolfo-pd adolfo-pd added the User submitted Submitted by a user label May 29, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 29, 2025

"""

Walkthrough

Two new Zoom Admin actions are introduced: one to fetch all recordings for a specific meeting, and another to list all participants of a past meeting. Supporting these, the Zoom Admin app module now provides methods for listing meeting recordings and past meeting participants via the Zoom API, both supporting pagination. The package version was updated accordingly.

Changes

File(s) Change Summary
components/zoom_admin/actions/get-meeting-recordings/get-meeting-recordings.mjs Added new action to fetch all recordings for a given Zoom meeting, with optional access token.
components/zoom_admin/actions/list-past-meeting-participants/list-past-meeting-participants.mjs Added new action to list all participants of a past Zoom meeting.
components/zoom_admin/zoom_admin.app.mjs Added listPastMeetingParticipants and listMeetingRecordings methods to the app interface.
components/zoom_admin/package.json Updated package version from 0.7.3 to 0.8.0.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GetMeetingRecordingsAction
    participant ZoomAdminApp
    participant ZoomAPI

    User->>GetMeetingRecordingsAction: Trigger action with meeting ID
    GetMeetingRecordingsAction->>ZoomAdminApp: Call listMeetingRecordings(meetingId, params)
    ZoomAdminApp->>ZoomAPI: GET /meetings/{meetingId}/recordings (with pagination)
    ZoomAPI-->>ZoomAdminApp: Return recordings data
    ZoomAdminApp-->>GetMeetingRecordingsAction: Return recordings
    GetMeetingRecordingsAction-->>User: Return recordings list (optionally with access token)
Loading
sequenceDiagram
    participant User
    participant ListPastMeetingParticipantsAction
    participant ZoomAdminApp
    participant ZoomAPI

    User->>ListPastMeetingParticipantsAction: Trigger action with meeting ID
    ListPastMeetingParticipantsAction->>ZoomAdminApp: Call listPastMeetingParticipants(meetingId)
    ZoomAdminApp->>ZoomAPI: GET /past_meetings/{meetingId}/participants (with pagination)
    ZoomAPI-->>ZoomAdminApp: Return participants data
    ZoomAdminApp-->>ListPastMeetingParticipantsAction: Return participants
    ListPastMeetingParticipantsAction-->>User: Return participants list
Loading

Poem

🐇
New actions hop into the Zoomy scene,
Fetching recordings, keeping meetings clean.
Participants listed, each name in a row,
With paginated leaps, the data will flow!
Rabbits rejoice in this admin delight—
Meetings and moments, all fetched just right.
🌱
"""

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

components/zoom_admin/actions/list-past-meeting-participants/list-past-meeting-participants.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:799:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:723:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:706:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:307:38)
at #link (node:internal/modules/esm/module_job:170:49)

components/zoom_admin/zoom_admin.app.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:799:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:723:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:706:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:307:38)
at #link (node:internal/modules/esm/module_job:170:49)

components/zoom_admin/actions/get-meeting-recordings/get-meeting-recordings.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:799:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:723:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:706:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:307:38)
at #link (node:internal/modules/esm/module_job:170:49)


📜 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 ddef5b4 and 88b83fb.

📒 Files selected for processing (4)
  • components/zoom_admin/actions/get-meeting-recordings/get-meeting-recordings.mjs (1 hunks)
  • components/zoom_admin/actions/list-past-meeting-participants/list-past-meeting-participants.mjs (1 hunks)
  • components/zoom_admin/package.json (1 hunks)
  • components/zoom_admin/zoom_admin.app.mjs (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • components/zoom_admin/package.json
🚧 Files skipped from review as they are similar to previous changes (3)
  • components/zoom_admin/actions/list-past-meeting-participants/list-past-meeting-participants.mjs
  • components/zoom_admin/zoom_admin.app.mjs
  • components/zoom_admin/actions/get-meeting-recordings/get-meeting-recordings.mjs
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Verify TypeScript components
  • GitHub Check: Publish TypeScript components
  • GitHub Check: Lint Code Base
✨ Finishing Touches
  • 📝 Generate Docstrings

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

@pipedream-component-development
Copy link
Collaborator

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
Copy link
Collaborator

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:

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

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 42d5532 and 420c600.

📒 Files selected for processing (3)
  • components/zoom_admin/actions/get-meeting-recordings/get-meeting-recordings.mjs (1 hunks)
  • components/zoom_admin/actions/list-past-meeting-participants/list-past-meeting-participants.mjs (1 hunks)
  • components/zoom_admin/zoom_admin.app.mjs (1 hunks)
🔇 Additional comments (4)
components/zoom_admin/zoom_admin.app.mjs (2)

395-404: Method implementation looks good.

The listPastMeetingParticipants method correctly follows the established patterns in the codebase, uses the appropriate API endpoint, and handles pagination consistently with other methods.


405-415: Method implementation looks good.

The listMeetingRecordings method correctly follows the established patterns, uses the appropriate API endpoint, and properly spreads additional parameters while maintaining pagination support.

components/zoom_admin/actions/list-past-meeting-participants/list-past-meeting-participants.mjs (1)

1-33: Well-structured action implementation.

The action follows all established patterns:

  • Proper imports and metadata
  • Correct prop definitions using the app's meeting propDefinition
  • Appropriate use of the paginate utility with the correct data key ("participants")
  • Consistent error message formatting and export pattern
components/zoom_admin/actions/get-meeting-recordings/get-meeting-recordings.mjs (1)

1-42: Well-implemented action with proper parameter handling.

The action implementation is excellent:

  • Follows established patterns and structure
  • Properly handles the optional downloadAccessToken parameter by passing it in the params object
  • Uses correct data key ("recordings") for pagination
  • Maintains consistency with the meeting prop definition and export patterns

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 @jocarino lgtm! However you also need to increment the minor version in package.json in the meantime I'm going to move it to Ready for QA! Thanks for this contribution!

@jcortes jcortes moved this from Ready for PR Review to Ready for QA in Component (Source and Action) Backlog May 29, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog May 29, 2025
@vunguyenhung vunguyenhung moved this from In QA to Ready for Release in Component (Source and Action) Backlog May 29, 2025
@vunguyenhung
Copy link
Collaborator

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

Test report
https://vunguyenhung.notion.site/feat-add-zoom-admin-actions-202bf548bb5e8162a2e4f50fbc470622

@jocarino
Copy link
Contributor Author

hi @jcortes lmk if you need anything else from me (Obrigado!)

@jcortes
Copy link
Collaborator

jcortes commented May 30, 2025

Closed this PR in favor of #16895

@jcortes jcortes closed this May 30, 2025
@github-project-automation github-project-automation bot moved this from Ready for Release to Done in Component (Source and Action) Backlog May 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

User submitted Submitted by a user

Development

Successfully merging this pull request may close these issues.

5 participants