Short answer: Drop the "Zoom → Update 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 ID meetingId | string | Required | Meeting ID |
Topic topic | string | Optional | Topic. e.g. "Updated meeting topic" |
Start Time start_time | datetime | Optional | ISO 8601 format |
Duration (minutes) duration | number | Optional | Duration (minutes). e.g. "30" |
Agenda agenda | string | Optional | Agenda |
{"meetingId": "{{trigger.meetingId}}","topic": "Updated meeting topic","start_time": "{{trigger.start_time}}","duration": "30","agenda": "{{trigger.agenda}}"}
{"success": true}
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.