> ## 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.

# CRM action

> Launch one of HubSpot's built-in action flows from the card.

# CRM action

**CRM action** uses HubSpot's native action button. Use it when HubSpot itself should open a familiar flow in the record's context.

## Availability

CRM action can be used in every placement, including the regular CRM sidebar. It must not be placed inside a Repeater.

## Add and configure

1. Add **CRM action** from **Actions**.
2. Enter a **Button label**.
3. Choose a **Built-in action**.

The available types are:

| Action                | Result                          |
| --------------------- | ------------------------------- |
| Add a note            | opens HubSpot's note flow       |
| Create a task         | opens the task flow             |
| Send an email         | opens the email flow            |
| Schedule a meeting    | opens meeting scheduling        |
| Preview the record    | opens the record preview        |
| Open a create form    | opens HubSpot's record creation |
| Open an external link | uses a URL context              |

## Data, rules, and steps

The button label can be dynamic. The whole building block can have a visibility rule and be assigned to a step.

The action itself is configured by its type, not by a Card Studio action sequence. You therefore cannot add a toast or CRM update afterwards in the same building block.

## Limitations and tips

The current designer does not expose fields for the variant, an alternative object type, or a URL context. So do not choose **Open an external link** if a specific address needs to be set; use [Link](/components/link) or [Buttons](/components/button-row) with the **Open a link** action instead.

Preview and the create form normally follow the current HubSpot context. Custom object scenarios should be tested in the actual portal.

The user's HubSpot permissions determine whether the note, task, email, and meeting flows can be opened or completed.