> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hubspotcards.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Actions

> Run sequences, update the CRM, create tasks, call systems, navigate flows, and show feedback.

# Actions

Actions run when a user clicks a regular button, or when a flow is submitted. A list runs in order and stops at the first error.

An action list can contain up to 10 actions. Use **Move up** to change the order.

## Action types

### Update a property on the record

Choose a HubSpot property and a new value. The value can be fixed or dynamic.

If the card has a select field that uses associated records as its data source, you can choose to update the selected record instead of the record the card is on.

### Create a task

Enter a task title and an optional description. Both can contain dynamic text segments. The schema supports a due-date offset, but it cannot be set in the current designer.

### Send to external system

Choose a system and an operation. The current designer does not show a general input form for the operation, so only use operations where the required inputs are already optional or handled by the integration. An operation with required, unset inputs will fail at runtime.

### Show a message

Shows a toast in the UI. Use it after a successful update, or as an explanation in a conditional branch. The message can be dynamic. The tone is set by the action's default and cannot be changed in the current editor.

### Open a link

Enter an address, which can be fixed or dynamic. **Open a link must always be the last action**, because the user leaves the card's context.

### Reload data

Fetches the card's data again after a change. The current editor does not pick a specific source, so the action uses the default for reloading the card's data.

### Record a choice

Sets the value of another input field in the card's form. Choose a target field and a new value. Use it, for example, to set an internal status after a button click.

### Conditional branch

Define a rule and a list of actions for **When the condition is true**. Optionally add an **otherwise** branch. Branches can be nested at most two levels deep.

### Flow actions

On cards with steps, you can choose:

* go to next step;
* go to previous step;
* go to specific step;
* submit the flow.

These actions are hidden/invalid without a flow. Forward navigation validates required fields on the steps being passed. Backward navigation does not.

## Order matters

A typical safe sequence is:

1. update the CRM or send to a system;
2. reload data if the card should reflect the change immediately;
3. show a confirmation;
4. optionally open a link as the last action.

If the first action fails, the later confirmations are not shown. That prevents a false success message.

## Buttons or CRM action?

Use [CRM action](/components/crm-action-button) for HubSpot's built-in note, task, email, and meeting flows. Use [Buttons](/components/button-row) when you want to combine multiple actions, write to fields, use conditions, or work with external systems.

## Permissions and runtime errors

A valid card configuration does not guarantee that the current HubSpot user is allowed to perform the CRM action. Missing scopes, missing property permissions, or a connector error can still stop the sequence at runtime. Test with a user who has the same access level as your target audience.