> For the complete documentation index, see [llms.txt](https://docs.agenticflow.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agenticflow.ai/workflows/media-action-forms.md).

# Model-Specific Media Forms

Higgsfield, ElevenLabs, and Kling nodes group related work under familiar actions such as **Generate Image** and **Generate Video**. Choose **Model / Action** inside the node, and the form shows the fields for that selection.

This is sometimes called a **dynamic payload**: the information sent to the provider changes with your choice. You fill ordinary workflow controls rather than writing a request by hand.

## Fill the form

1. Add a node from the provider’s category and select your connection.
2. Choose **Model / Action**.
3. Complete the **Configuration** fields. Some actions also ask you to choose a model inside this section.
4. Enter text, select named options, set numbers or switches, and add reference media as requested.
5. For lists such as dialogue lines or media references, add an item and complete its fields. Remove items you no longer need.
6. Save the workflow and test the step.

Only the controls supported by your selection apply. For example, one video model might offer a starting image and duration, while another expects several references or a motion video.

## Use values from earlier steps

Use the field’s variable control to insert a workflow input or an earlier node’s result. This also works inside reference lists and grouped fields, so you can use a generated image as the input to a video action.

When a model needs a list of images, supply the appropriate list or add individual references. When it needs one image, select one result. A text field, number, checkbox, and media list are different kinds of input; follow the selected field’s guidance.

If an action requests an identifier, such as a request, character, asset, or task ID, use the identifier returned by the matching earlier action.

## Dropdowns depend on your choices

The form uses readable titles for models, voices, styles, and presets when available. Some resources have no name or list available; those fields may still require an ID.

Changing the connection or a related field can refresh the available options. Select the connection first, wait for loading to finish, and use **Load more** when offered. If loading fails, choose **Retry**.

| What you see                | What it means                                                                  |
| --------------------------- | ------------------------------------------------------------------------------ |
| Select an option            | No value has been selected yet.                                                |
| Loading options…            | The choices are being retrieved.                                               |
| No options available.       | No choices were returned for this account and selection.                       |
| Saved selection unavailable | A saved value is not in the currently loaded choices. It has not been deleted. |

## What happens when you change a model or action?

The form keeps compatible values and removes fields that the new choice does not accept. Review the updated form and complete any newly required inputs before running.

For example, changing ElevenLabs **Text To Speech** to **Speech To Text** clears the previously selected speech model. Choose a transcription model and supply an audio recording for the new action.

Do not use switching models as a way to store two configurations. To compare alternatives while preserving both, create separate nodes or copy the workflow.

## Does saving survive a refresh?

**Yes, after the workflow has saved successfully.** Reopening the node restores its selected action and saved fields, including nested settings, lists, and references. Reloading dropdown choices does not erase the saved values.

A refresh and an action change are different: refreshing reloads the saved configuration; changing the action can intentionally remove incompatible fields. If a value appears unavailable after reopening, check the connection and loaded choices before replacing it.

Saved configuration is also different from the temporary results used by **Run Step**. Read [Run Step and reuse results](/workflows/workflow-single-run/run-step.md) before relying on earlier test outputs.

## Review the result

After **Run Step**, review the node’s output or error in **Build**. **History** provides the saved run details. A successful submission may contain a pending job rather than finished media; follow [media results and AI Drive](/workflows/workflow-single-run/media-results.md) to retrieve it.

These forms are also used for the grouped provider actions inside AI Switch branches and Workforce plugin nodes. Previously saved provider nodes remain editable without rebuilding them.

## Related guides

* [Media connections](/integrations/connection-providers/media.md)
* [Data flow and types](/workflows/data-flow-and-types.md)
* [Run Step and reuse results](/workflows/workflow-single-run/run-step.md)