Flows
Every RME capability is available to Flow Builder through invocable actions — no code required.
Packaged actions
| Action | Purpose |
|---|---|
| Send Message (RME) | Send on any channel, with or without a template |
| Schedule Message (RME) | Send later, in a window, or at an optimal time |
| Cancel Scheduled Message (RME) | Cancel by message id |
| Check Consent (RME) | Boolean check per channel and category |
| Add to Suppression (RME) | Suppress an address or number |
| Render Template (RME) | Return merged subject and body without sending |
| Get Delivery Status (RME) | Current status and last event for a message |
Send Message inputs
| Input | Type | Notes |
|---|---|---|
| Channel | Text | EMAIL, SMS, RCS, WHATSAPP, VOICE, PUSH |
| Channels | Text Collection | Ordered preference when using a strategy |
| Strategy | Text | FIRST_REACHABLE, FIRST_CAPABLE, ALL, LEAST_COST, PREDICTED |
| Template Name | Text | Developer name of an active template |
| Recipient Contact Id | Text | Applies consent, suppression, and history linkage |
| Recipient Address | Text | Email address or E.164 phone number |
| Context Record Id | Text | Record used for merge fields |
| Category | Text | Transactional, Service, Operational, Marketing |
| From Domain | Text | Must be a verified sending domain |
Outputs: Message Id, Status, Resolved Channel, Error Code, Error Message.
Record-triggered example
Trigger: Case — Status changed to Closed
↓
Decision: Contact has email? ── No ──► Send Message (SMS)
│ Yes
▼
Send Message (RME)
Channel = EMAIL
Template Name = Case_Closed_Survey
Contact Id = {!$Record.ContactId}
Context Record = {!$Record.Id}
Category = Service
↓
Decision: Status = SENT ── No ──► Create Task "Follow up manually"
│ Yes
▼
Update Case: Survey_Sent__c = TRUE
Handling errors
Always branch on the Status output rather than relying on a fault path alone. RME returns SUPPRESSED, NO_CONSENT, INVALID_ADDRESS, and PROVIDER_ERROR as normal outputs so a Flow can respond intelligently instead of failing.
Bulk-safe design
The action is bulkified. Prefer a scheduled-path or batch-friendly Flow over a per-record loop when messaging large populations, and use the Apex bulk API for volumes above roughly 10,000 recipients.
Subscribing to delivery events
Build a platform-event-triggered Flow on RME_Delivery_Event__e to react to bounces, replies, and clicks in real time. See Platform Events.
Continue to Apex APIs.
Was this helpful?
Last updated 1 month ago