---
isPublished: true
knowledgeIndex: false
hidden: true
noindex: true
template: "page.peb"
title: "Author Experience draft Flow Action"
description: "Read or revise an Experience draft through an approved administrative authoring integration."
contentType: "reference"
audience: "admin,developer"
---

# Author Experience draft

Read or revise an Experience draft through an approved administrative authoring integration.
The namespaced Apex action name is `rooms__ExperienceAuthoringAction`.
Check action availability and input fields in your installed package.

## Transaction summary

| Effect | Behavior |
| --- | --- |
| API callout | Conditional. Authoring operations can make API callouts. |
| Record writes | Conditional. Creation and save operations can insert or update draft-related Room and Item records. |
| Queued work | No background job is explicitly started by this action. Inspect the returned authoring result. |
| Email | The action is for draft authoring, not recipient email delivery. |

Administrative action. Use only with an integration that supplies the supported authoring request.
Submit exactly one request per invocation. Request JSON must not be blank and must be within 250 KB.
Do not treat a saved draft as a published Experience or an invitation.
The action returns JSON text, not separate Flow Success or Message fields.

## Inputs

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

| API name | Flow label | Required | Default or guidance |
| --- | --- | --- | --- |
| `requestJson` | requestJson | Yes | Supported authoring request JSON supplied by the administrative integration. Exactly one request; maximum 250 KB. |

## Outputs

| API name | Flow label | Meaning |
| --- | --- | --- |
| `responseJson` | responseJson | JSON result. Parse it and inspect success and message; do not infer success from a nonblank string. |

## Configure the Flow

1. Use the approved authoring integration to prepare Request JSON.
2. Submit one request.
3. Parse Response JSON and check its success and message before using the updated draft.
4. Reload the draft after a conflict before preparing another edit.

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

**Invalid request.** Check JSON validity, request size and the single-request limit.

**Revision or edit conflict.** Reload the current draft and prepare the requested edit against that state.

**Uncommitted work pending.** Some authoring operations call out. Do not place prior writes or another authoring request in the same transaction without appropriate transaction control.

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