Short answer: Drop the "RingCentral → Create RingCentral 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 Name name | string | Required | Project sync |
Type type | options | Optional | — |
Start Time (ISO 8601) startTime | string | Optional | 2026-01-15T14:00:00.000Z |
Duration (minutes) duration | number | Optional | — |
Password password | string | Optional | — |
{"name": "Project sync","type": "{{trigger.type}}","startTime": "2026-01-15T14:00:00.000Z","duration": "{{trigger.duration}}","password": "{{trigger.password}}"}
{"id": "br-12345","name": "Project sync","hostUri": "https://v.ringcentral.com/host/12345","joinUri": "https://v.ringcentral.com/join/12345","shortId": "1234567890"}
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.