Short answer: Drop the "Zoom → Create Meeting" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Meeting Topic topic | string | Required | Meeting Topic. Example: Weekly Team Sync |
Start Time start_time | string | Optional | ISO 8601 format (leave empty for instant meeting) |
Duration (minutes) duration | string | Optional | Duration (minutes). Example: 30 |
Meeting Type type | options | Optional | Meeting Type. Options: Instant, Scheduled, Recurring (no fixed time), Recurring (fixed time) |
Agenda agenda | string | Optional | Agenda. Example: 1. Project updates 2. Blockers 3. Action items |
Meeting Password password | string | Optional | Leave empty for auto-generated password |
{"topic": "e.g. Weekly Team Sync","start_time": "e.g. 2025-01-20T10:00:00Z","duration": "e.g. 30","type": "{{trigger.type}}","agenda": "e.g. 1. Project updates 2. Blockers 3. Action items"}
{"id": 123456789,"topic": "Weekly Team Sync","duration": 30,"join_url": "https://zoom.us/j/123456789?pwd=abc","password": "123456","start_url": "https://zoom.us/s/123456789?zak=xyz","start_time": "2025-01-20T10:00:00Z"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.