> For the complete documentation index, see [llms.txt](https://flapjax.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flapjax.gitbook.io/docs/settings/workspace/action-setups.md).

# Action Setups

An **action setup** is a saved preset of an automation action's configuration. Configure an action once, whether a branded welcome email, a standard label assignment or a specific record update. Save it under a name. Apply that exact configuration to the same type of action in any automation, with no rebuilding.

Setups live under **Settings → Action Setups**.

Every setup is **shared across your whole organization**. A teammate saves one and everyone in the org can see and apply it. That keeps common actions consistent, with one vetted preset instead of everyone reconfiguring the same send.

***

### What a setup holds

Each setup stores three things.

* **Name**, a descriptive label your teammates will recognise, such as "Standard welcome email". Names must be unique inside your organization, and a duplicate name shows a "name taken" message.
* **Action type**, the kind of action the preset covers, such as Send Email or Assign Label. You choose it at creation and cannot change it later.
* **Configuration**, all the settings for that action, authored in the same editor you use inside the automation builder.

***

### Creating a setup

1. Go to **Settings → Action Setups**.
2. Click the **action type selector** and pick the type of action for your preset. The setup editor opens.
3. Give the setup a **name**.
4. Fill in the configuration with the embedded editor. It matches the form you see for that action inside an automation.
5. Click **Save**.

The new setup joins the list, ready for anyone in your organization to apply.

{% hint style="info" %}
**No trigger context here.** A setup attaches to no specific automation, so variables that depend on a trigger or an earlier action stay out of reach as you edit one. Person attributes are the exception and remain available. The editor still saves an incomplete configuration and shows a reminder, so you can wire up the run-specific pieces after you apply the setup to a real action.
{% endhint %}

***

### Editing a setup

Click a setup in the list to reopen the editor. Update the name or the configuration, then click **Save**.

Editing changes nothing about actions you already applied it to. Applying a setup copies its configuration onto the action at that moment.

***

### Per-user defaults

Mark any setup as **your default** for its action type. Add a new action of that type in an automation and Flapjax **pre-fills its configuration** from your default setup. Your standard configuration is in place the moment the action appears.

Defaults are personal. Your choices apply to you alone, even though the setups themselves are shared org-wide. Each person holds at most one default per action type. Set or clear a default from the setup's actions menu in the list, or from the star icon in the setup picker inside the builder.

***

### Applying a setup in the automation builder

Open an action's configuration panel in the [flow builder](/docs/automations/flow-builder.md) and use the **action setup picker**, the swatchbook button. Pick a setup and Flapjax copies its configuration onto the action, **overwriting** whatever was there.

The picker offers only setups matching the action's type, so a "Send Email" setup never lands on an SMS action. Applying a setup needs the **manage automations** permission.

***

### Which actions support setups

**Most action types support setups.** They cover the configurable actions worth standardising:

* **Communication**: Send Email, Send SMS, Send WhatsApp, Send Slack Channel, Send Teams Channel, Send Telegram Broadcast
* **People and labels**: Assign Label, Remove Label, Update Person, Add Note
* **Records**: Create Record, Update Record
* **Utilities**: Custom Action, Formula, and the delay actions

A small set of action types support no setups, since a preset would make no sense:

* **Flow-control and exit actions**: Branch If, Branch Switch, Randomize Path, Loop, Exit Sequence, Exit Workflow. Their configuration describes the shape of one automation's flow, so it cannot travel.
* **Actions with no configuration**, such as Delete Person, Create Person, Generate UUID and Export Record. Nothing exists to template.
* **Utilities whose whole configuration is a run-specific reference**, such as Validate Email, Validate Phone Number, Parse Date, Split Text, Adjust Time and Compare Dates. They point at values from the current run, which would not resolve in a different automation.

{% hint style="info" %}
The **Formula** action supports setups, and new Formula setups cannot start from the settings editor, since they need automation context to build. Existing Formula setups stay fully editable here.
{% endhint %}

***

### Permissions

Anyone who can reach the Action Setups page can view the list. Creating, editing, setting a default, deleting and applying setups all need the **manage automations** permission. Without it the page stays read-only.

***

### Related

* [Flow Builder](/docs/automations/flow-builder.md), where setups get applied
* [Automation Actions](/docs/automations/actions.md), the actions you can build setups for