# Actions and Action Groups

### What They Are

**Actions** and **Action Groups** are the backend operation layer of Flexi Kanban. They define the logic that runs in response to events on the board — whether triggered by a user interaction, a card movement, a form submission, a scheduled job, or an external API call.

Where Handlers define *what should happen* when a user interacts with the board, Actions define *how it happens* — the actual operations that execute in Salesforce behind the scenes.

***

### Actions

An **Action** is a reusable backend operation that performs a specific task in Salesforce. Actions are configured independently and can be referenced from multiple places across your Flexi Kanban setup.

A single Action might:

* Update one or more fields on a Salesforce record
* Create or delete a record
* Send a notification or email
* Call a Salesforce Flow or Apex class
* Interact with other Salesforce platform capabilities

Because Actions are reusable, the same Action can be triggered from a card element Handler, a Custom Button, a card movement rule, a form submission, or a scheduled job — without duplicating configuration.

***

### Action Groups

An **Action Group** is a sequence of Actions executed in a defined order. All Actions within a group share the same runtime context and Variables, which means data and values can be passed between them as they execute in sequence.

Action Groups are useful when a single event needs to trigger a coordinated series of operations — for example, updating a record, sending a notification, and logging an activity, all as one atomic workflow triggered by a card moving to a new column.

***

### How Actions Are Triggered

Actions and Action Groups can be triggered in several ways:

* **By a Handler** — when a user clicks a card element, Custom Button, or form element configured with an Execute Action handler type
* **By card movement** — automatically when a card is dragged from one column to another
* **Manually** — invoked directly by a user from the board
* **In batch** — run across a set of records at once
* **On schedule** — executed automatically at a configured time or interval
* **Via API** — triggered externally by another system or integration

This flexibility makes Actions a central part of building automated, event-driven workflows on top of your Flexi Kanban boards.

***

### A Practical Example

A sales team uses a Flexi Kanban board to manage their opportunity pipeline. When a rep moves an Opportunity card from **Proposal Sent** to **Negotiation**, an Action Group fires automatically:

1. **Action 1** — updates the Opportunity's `Stage` and `Last Stage Change Date` fields
2. **Action 2** — creates a follow-up Task assigned to the opportunity owner
3. **Action 3** — sends an internal Slack notification to the sales manager

All three operations execute in sequence, triggered by the single card movement, with no manual steps required from the rep.

***

### When to Use Actions and Action Groups

Use Actions when:

* You need a reusable backend operation that can be triggered from multiple places
* You want card movement to automatically update records or trigger Salesforce automation
* You need to connect board interactions to broader Salesforce platform capabilities

Use Action Groups when:

* A single trigger needs to execute multiple operations in a defined sequence
* You need to pass data and context between operations as they run

Learn more in [Actions and Action Groups](https://claude.ai/chat/3ff2e1a4-8052-48a2-8c2f-8ff0fe64eda1).