---
isPublished: true
knowledgeIndex: false
hidden: true
noindex: true
template: "page.peb"
title: "Room Activity Action Flow Action"
description: "Queue an activity entry for the Room activity tab."
contentType: "reference"
audience: "admin,developer"
---

# Room Activity Action

Queue an activity entry for the Room activity tab.
The namespaced Apex action name is `rooms__RoomActivityAction`.
Check action availability and input fields in your installed package.

## Transaction summary

| Effect | Behavior |
| --- | --- |
| API callout | No immediate API callout. Activity submission calls out in queued work. |
| Record writes | No direct business-record write in the action. The later process records Room activity. |
| Queued work | Yes. Success means activity submission was queued, not that the activity is visible. |
| Email | No email is sent. |

Supply Headline, Event Type and Room ID. Add member and person references when relevant.
Event Type is a required compatibility input, but its supplied value is not preserved as the submitted activity type.
Do not use this action for a workflow that depends on preserving a specific activity type.
Verify the final activity entry in the Room. The response has no activity identifier.

## Inputs

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

| API name | Flow label | Required | Default or guidance |
| --- | --- | --- | --- |
| `headline` | Headline | Yes | Activity headline. |
| `description` | Description | No | Optional activity details. |
| `type` | Event Type (See DialogueOne Events) | Yes | Required compatibility input. Its supplied value is not preserved as the submitted activity type. |
| `roomId` | Room ID | Yes | The target Room. |
| `memberId` | Room Member ID | No | Optional Room Member reference. |
| `whoId` | Who ID (Contact, Lead, User ID) | No | Optional Contact, Lead or User reference. |

## Outputs

| API name | Flow label | Meaning |
| --- | --- | --- |
| `success` | Success | Whether queue submission reported success. |
| `message` | Message | An immediate submission error when available. |

## Configure the Flow

1. Select the Room and provide the activity text and event type.
2. Set optional member or person references.
3. Store Success and Message, then verify the Room activity result.

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

**Success is true but the activity is absent.** Inspect later activity processing and Events. The action does not wait for completion.

**A later callout fails.** Queued work can leave pending work in the current transaction. Review transaction control.

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