Zoom-Drive-Connector

This program downloads meeting recordings from Zoom and uploads them to a specific folder on Google Drive.

This software is particularly helpful for archiving recorded meetings and webinars on Zoom. It can also be used to distribute VODs (videos on demand) to public folder in Google Drive. This software aims to fill a missing piece of functionality in Zoom (post-meeting recording sharing).

Setup

Create a file called config.yaml with the following contents:

zoom:
  key: "zoom_api_key"
  secret: "zoom_api_secret"
  username: "[email protected]"
  delete: true
  meetings: 
    - {id: "meeting_id" , name: "Meeting Name", folder_id: "Some Google Drive Folder ID", slack_channel: "channel_name"}
    - {id: "meeting_id2" , name: "Second Meeting Name", folder_id: "Some Google Drive Folder ID2", slack_channel: "channel_name2"}
drive:
  credentials_json: "conf/credentials.json"
  client_secret_json: "conf/client_secrets.json"
slack:
  key: "slack_api_key"
internals:
  target_folder: "/tmp"

Note: It is advised to place this file in the conf folder (together with the json credentials) this folder needs to be referenced when you launch the Docker container (see below).

You will need to fill in the example values in the file above. In order to fill in some of these values you will need to create developer credentials on several services. Short guides on each service can be found below.

Zoom

To get the proper API key and secret, you will need to use the following "Getting Started Guide" on Zoom's developer site. Link here. Paste the API key and secret into config.yaml under the zoom section.

It is (currently) not possible to download the recordings via the API key only. As such you need to specify a user that is part of your organizations Zoom account. This can be a non-pro user. The e-mail of the user should be added to the username entry under the zoom section.

Google Drive

To upload files to Google Drive you have to login to your developer console, create a new project, set the required permissions and then download the access key. This can be done via the following steps:

1. Go to the Google API Console
2. Click on "Create new project".
3. Give it a name and enter any other required info.
4. Once back on the dashboard click on "Enable APIs and Services" (make sure your newly created project is selected).
5. Search for and enable: "Google Drive API".
6. Go back to the dashboard and click on "Credentials" in the left side bar.
7. On the credentials screen click on the "Create credentials" button and select "OAuth client ID".
8. Follow the instructions to set a product name, on the next screen only the Application name is required. Enter it and click on "save".
9. As application type, select "Other" and fill in the name of your client.
10. Now under "OAuth 2.0 client IDs" download the JSON file for the newly create client ID
11. Save this file as client_secrets.json in the conf directory.

The credentials file will be created during the first start (see below).

Slack

1. Register a new app using this link.
2. Under "Add features and functionality" select "Permissions".
3. Under 'Scopes' select chat:write:bot.
4. On the same page copy the "OAuth Access Token". Paste that value into the configuration file under the slack section.
5. Put the name of the Slack channel to post statuses in the config file.

Running the Program

The first time we run the program we have to authenticate it with Google and accept the required permissions. For this we run the docker container in the interactive mode such that we can enter the generated token. Instructions on how to pull Docker images from the Github registry can be found here.

$ docker pull docker.pkg.github.com/minds-ai/zoom-drive-connector/zoom-drive-connector:1.2.0
$ docker run -i -v /path/to/conf/directory:/conf \
    docker.pkg.github.com/minds-ai/zoom-drive-connector/zoom-drive-connector:1.2.0

Alternatively, you can clone the repository and run make build VERSION=1.2.0 to build the container locally. In this case, you will need to exchange the long image name with the short-form one (zoom-drive-connector:1.2.0).

This will print an URL, this URL should be copied in the browser. After accepting the permissions you will be presented with a token. This token should be pasted in the terminal. After the token has been accepted a credentials.json file will have been created in your configuration folder. You can now kill (ctrl-C) the Docker container and follow the steps below to run it in the background.

Run the following command to start the container after finishing the setup process.

$ docker run -d -v /path/to/conf/directory:/conf \
    docker.pkg.github.com/minds-ai/zoom-drive-connector/zoom-drive-connector:1.2.0

Making Changes to Source

If you wish to make changes to the program source, you can quickly create a Conda environment using the provided environment.yml file. Use the following commands to get started.

$ conda env create -f environment.yml
$ source activate zoom-drive-connector

Any changes to dependencies should be recorded in both environment.yml and requirements.txt with the exception of development dependencies, which only have to be placed in environment.yml. Make sure to record the version of the package you are adding using the double-equal operator.

To run the program in the conda environment you can use the following command line:

CONFIG=conf/config.yaml python -u main.py --noauth_local_webserver

Running Tests and Style Checks

All new functionality should have accompanying unit tests. Look at the tests/ folder for examples. All tests should be written using the unittests framework. Additionally, ensure that your code conforms with the given style configurations presented in this repository.

To run tests and style checks, run the following commands:

$ tox -p all --recreate
$ ./style_checks.sh  # Run this in the root of the repository.
$ # You can also check style for a single file by passing the name of the file.

Contributing

This project is open to public contributions. Fork the project, make any changes you want, and submit a pull request. Your changes will be reviewed before they are merged into master.

Authors

• Nick Pleatsikas
• Jeroen Bédorf

License

This project is licensed under Apache 2.0.