---
isPublished: true
knowledgeIndex: false
hidden: true
noindex: true
template: "page.peb"
title: "Room Member Action Flow Action"
description: "Add a Room Member using the compatibility action without outputs."
contentType: "reference"
audience: "admin,developer"
---

# Room Member Action

Add a Room Member using the compatibility action without outputs.
The namespaced Apex action name is `rooms__RoomMemberCreateAction`.
Check action availability and input fields in your installed package.

## Transaction summary

| Effect | Behavior |
| --- | --- |
| API callout | No immediate API callout in member preparation. Link and Room synchronization can call out later. |
| Record writes | Upserts Room Members and updates related Room, Contact, Lead, Checklist and Item state as applicable. Errors can create DialogueOne Event records. |
| Queued work | Yes, when synchronization is enabled. Member activity and invitation processing can continue later. |
| Email | Conditional. Invitation processing can send native email or queue delivery. |

This action uses the same member options as [Add Room Member](/content/build/flows/InviteRoomMemberAction.md), but returns no result fields.
For a new Flow that needs Success, Message and Member ID, use Add Room Member.
Use Contact ID or User ID. Lead ID alone is not accepted by this action.
A missing Room ID is logged and stops processing. A normal Flow continuation does not prove invitation delivery.

## Inputs

**Required** describes the Flow input setting. The processing rules above also apply.

| API name | Flow label | Required | Default or guidance |
| --- | --- | --- | --- |
| `roomId` | Room ID | Yes | Select the existing Room. It is required for processing. |
| `masterRecordId` | Record ID | No | Related business record. This does not replace Room ID. |
| `contactId` | Contact ID | No | Select a Contact, or use User ID for a User recipient. |
| `leadId` | Lead ID | No | Retained compatibility input. Lead ID alone is not accepted or forwarded as the recipient selector. |
| `userId` | User ID | No | Select a Salesforce User when the recipient is a User. |
| `role` | Role: Administrator, Collaborator, Viewer, or None | No | Default: `Collaborator`. Administrator and Viewer select their matching access. Do not use None to disable access; that value does not select a no-access role here. |
| `sendInvite` | Send Email Invitation | No | Default: `true`. Requests an invitation when synchronization and delivery are enabled. |
| `replyTo` | Reply To | No | Optional reply-to email address. |
| `senderDisplayName` | Sender Display Name | No | Optional email sender display name. |
| `useEmailSignature` | Use Native Email Signature | No | Default: `false`. Controls the native email signature option. |
| `emailTemplate` | Email Template Name (Optional. Portal notification used by default) | No | Optional email template name. Otherwise the configured Room invitation content is used. |
| `signerOrder` | Signer Order (default 0 ) | No | Default: `0`. Sets the member signer order. It does not prove that the document is signable. |
| `syncRoomAPI` | Sync Room with API (Default=true) | No | Default: `true`. Enables Room synchronization and invitation processing. When false, synchronize separately after record preparation. |

## Outputs

This action returns no Flow outputs. Connect its Fault path and verify the resulting records or delivery separately.

## Configure the Flow

1. Select the Room and one recipient identity.
2. Set role, explicit signer order, synchronization and invitation options.
3. Connect the Fault path. Inspect the member and delivery result separately.

Review the Flow context, Apex action access and the object and field permissions needed by this operation.
Record writes can run other Salesforce automation.
For API work, also review the configured Salesforce API connection user's required access.

## Troubleshooting

**The Flow needs Member ID.** Use Add Room Member, which returns a member reference.

**No email arrives.** Check Send Email Invitation, Sync Room with API, recipient email and Events.

**A later callout reports uncommitted work.** Member creation performs record writes and can publish events and queue work.

See the [Flow action index](/content/build/flows/index.md) for transaction guidance and related actions.
