Zoom - Add GET request to certain Instant Webhook-Based Sources

[michelle0927]

Resolves #3342

Historical events will be emitted in the deploy hooks of the following sources/triggers:
Meeting Created
Meeting Ended
Meeting Started
Meeting Updated
Recording Completed
Webinar Created
Webinar Ended
Webinar Started
Webinar Updated

The following events require a paid subscription, and have not been tested.
Recording Completed
Webinar Created
Webinar Ended
Webinar Started
Webinar Updated

The following sources don't yet emit historical events because the Zoom API doesn't yet offer a way to retrieve generic events or deleted resources.
Custom Event
Phone Event
Meeting Deleted
Webinar Deleted

[vercel]

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

Name	Status	Preview	Updated
pipedream-docs	✅ Ready (Inspect)	Visit Preview	Jul 20, 2022 at 4:27PM (UTC)
pipedream-docs-redirect-do-not-edit	✅ Ready (Inspect)	Visit Preview	Jul 20, 2022 at 4:27PM (UTC)

[dylburger]

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
• Create subscription webhooks sources (vs polling sources) whenever possible
• Always emit a summary with events
• Use a built-in deduping strategy wherever possible
• When building webhook sources, follow these best practices
• When building polling sources, follow these best practices

[lcaresia]

LGTM!

[DilanAthukorala]

@michelle0927 Recording Completed source throws error upon source creation

[DilanAthukorala]

@michelle0927 For "Recording Completed" source, there are no events emitted after the recordings are completed.

[michelle0927]

@DilanAthukorala The "Recording Competed" source emits events for new cloud recordings (https://marketplace.zoom.us/docs/api-reference/zoom-api/events#/paths/recording.completed/post). The screenshot above shows a recording under Local Recordings. Do you have recordings under Cloud Recording that are not showing up? I don't have a Pro account, so I haven't been able to test that component.

[DilanAthukorala]

@michelle0927 Thank you, I was only able to test the components from my free account.

I was not able to test the following sources that requires paid subscription.

• Recording Completed
• Webinar Created
• Webinar Ended
• Webinar Started
• Webinar Updated
• Phone Events

Verification completed for the following sources and no issues observed.

• Meeting Created
• Meeting Ended
• Meeting Started
• Meeting Updated
• Meeting Deleted
• Custom Events

@dannyroosevelt There were only 50% of sources that could be tested with free account, can we sign off with the above test results considering these were updates to already existing sources?

[michelle0927]

/approve

[jcortes]

Approved!