Block 1 - When clicking ‘Execute workflow’
- Type / Role
- n8n-nodes-base.manualTrigger - manualTrigger
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
This workflow automates the management of Zoom OAuth tokens and the creation of new Zoom users through the Zoom API. This workflow automates the process of creating a new Zoom user by first ensurin...
n8n-nodes-base.manualtrigger, n8n-nodes-base.datatable, n8n-nodes-base.sort, n8n-nodes-base.limit, n8n-nodes-base.if, n8n-nodes-base.stickynote, n8n-nodes-base.merge, n8n-nodes-base.httprequest
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Davide.
Original n8n.io sourceThis workflow automates the management of Zoom OAuth tokens and the creation of new Zoom users through the Zoom API.
This workflow automates the process of creating a new Zoom user by first ensuring a valid OAuth access token is available. It is designed to handle the fact that Zoom access tokens are short-lived (1 hour) by using a longer-lived refresh token (90 days) stored in an n8n Data Table.
It includes two main phases:
Token Generation & Management
User Creation in Zoom
✅ Full Automation of Zoom Authentication
✅ Centralized Token Storage
✅ Error Prevention
4.✅ Automatic User Provisioning
✅ Scalability
✅ Transparency & Modularity
refresh_token) is then used in an HTTP Request to Zoom's OAuth endpoint to generate a fresh, valid access_token.access_token and refresh_token are saved back to the Data Table for future use. The workflow then generates a random password for the new user, merges this password with the initial user data, and finally sends a POST request to the Zoom API to create the new user. If the creation is successful, Zoom automatically sends an invitation email to the new user.Prepare the Data Table:
accessToken and refreshToken.Configure Zoom OAuth App:
account_id.client_id and client_secret in Base64 format (as client_id:client_secret)."XXX" in the Authorization header with this Base64-encoded string.Generate Initial Tokens (First Run Only):
Configure User Data:
"XXX" placeholders for first_name, last_name, and email.After these setup steps, the main workflow (triggered via "When clicking 'Execute workflow'") can be run whenever you need to create a new Zoom user. It will automatically refresh the token and use the provided user data to create the account.
Contact me for consulting and support or add me on Linkedin.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 26 workflow blocks. Download the JSON for the full node graph.
| Workflow | Automate Zoom 🎦 user onboarding with OAuth token management and data tables |
|---|---|
| Complexity | advanced |
| Nodes | 26 |
| Categories | HR |
| Author | Davide |
| Published | 12 Nov 2025 |
Use the JSON export at /data/workflows/10747/10747.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
This workflow automates the management of Zoom OAuth tokens and the creation of new Zoom users through the Zoom API. This workflow automates the process of creating a new Zoom user by first ensurin...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your HR use case.