> For the complete documentation index, see [llms.txt](https://docs.bird.com/applications/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bird.com/applications/automation/flows/concepts/actions.md).

# Actions

An ‘action’ is a task that a flow performs. Actions can either be tasks within MessageBird or a task that takes place in an external [connector](/applications/integrations/integrations.md).

## Action types

There are six types of flow actions:

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Core actions</strong></td><td>Core actions are fundamental Flow actions that enable the processing of data and the execution of tasks.</td><td></td><td><a href="/pages/HZYoQYUtGmpf7Ozd7LM4">/pages/HZYoQYUtGmpf7Ozd7LM4</a></td></tr><tr><td><strong>Contact actions</strong></td><td>Contact actions enable you to create, retrieve, update, and delete contact information from Contacts.</td><td></td><td><a href="/pages/JKgtCqGsQjxRbMwsWUTm">/pages/JKgtCqGsQjxRbMwsWUTm</a></td></tr><tr><td><strong>Channel actions</strong></td><td>Channel actions enable you to send and receive messages through various communication channels, such as SMS and WhatsApp.</td><td></td><td><a href="/pages/UVmCM6sz2V9ffrsjXNim">/pages/UVmCM6sz2V9ffrsjXNim</a></td></tr><tr><td><strong>Conversation actions</strong></td><td>Conversation actions are a set of actions that allow you to manage conversations in Inbox.</td><td></td><td><a href="/pages/fIqUrOLzkvJ5qBQMKtid">/pages/fIqUrOLzkvJ5qBQMKtid</a></td></tr><tr><td><strong>Connector actions</strong></td><td>Connector actions are used to interact with external tools, such as CRM systems or cloud storage solutions, from Flows.</td><td></td><td><a href="/pages/UWRRxwNTIZOJhRsbo77e">/pages/UWRRxwNTIZOJhRsbo77e</a></td></tr><tr><td><strong>MessageBird API actions</strong></td><td>API actions are deveoper-level actions that interface directly with out APIs.</td><td></td><td><a href="/pages/3pdrNcJaQNH5Zs8UJORq">/pages/3pdrNcJaQNH5Zs8UJORq</a></td></tr><tr><td><strong>Voice actions</strong></td><td>Voice actions are a set of actions that allow you to automate Voice call events.</td><td></td><td><a href="/pages/0bbevgqUTnMV28uZqAuG">/pages/0bbevgqUTnMV28uZqAuG</a></td></tr></tbody></table>

## Set up an action

### Choose your flow event

1. In the flow editor, once you have set up your [trigger](/applications/automation/flows/concepts/triggers.md), click **Add new action**.
2. Browse the available actions, or use the search bar to find a specific action.
3. Select your action and complete the fields to tell the flow exactly what you want it to do. Depending on the type of action you choose, there might be dropdown menus, form fields, and radio buttons to select.
4. Once you're happy with how your action has been set up, click **Next**.

### Test your action

Run a quick test to see if your action is working. If there are errors, these will be flagged and displayed in the output for you to review and fix.

If you're happy with your action, you can click **Add new action** to continue to build your flow, or click the **Publish draft** to set your flow live.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bird.com/applications/automation/flows/concepts/actions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.