Short answer: Drop the "RingCentral → RingCentral Send Fax" 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 |
|---|---|---|---|
To Fax Number to | string | Required | +15551234567 |
Resolution faxResolution | options | Optional | — |
Cover Page Text coverPageText | string | Optional | — |
Attachment URL attachmentUrl | string | Optional | Publicly accessible URL to the document (PDF, TIFF, DOC, etc.). |
{"to": "+15551234567","faxResolution": "{{trigger.faxResolution}}","coverPageText": "{{trigger.coverPageText}}","attachmentUrl": "{{trigger.attachmentUrl}}"}
{"id": "67890","faxResolution": "High","messageStatus": "Queued"}
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.