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

# Actions Overview

> Learn how to perform actions in your workflows, including sending emails, making HTTP requests, and posting to Slack.

# Actions Overview

Action steps perform specific tasks in your workflows. They execute operations like sending notifications, making API calls, or integrating with external services.

## When to Use Actions

Action steps are the core of workflow automation:

* **Notifications**: Send emails, Slack messages, or other alerts
* **API Integration**: Make HTTP requests to external services
* **Data Processing**: Transform or process data from previous steps
* **Service Integration**: Connect with third-party tools and platforms

## Available Action Steps

<CardGroup cols={3}>
  <Card title="HTTP Request" icon="plug" href="/workflows/actions/http-request">
    Make HTTP requests to any API endpoint with full control over method, headers, and body.
  </Card>

  <Card title="Send Email" icon="envelope" href="/workflows/actions/send-email">
    Send formatted emails with support for HTML, plain text, and JSON templates.
  </Card>

  <Card title="Slack Message" icon="slack" href="/workflows/actions/slack-message">
    Send rich messages to Slack channels with support for blocks and formatting.
  </Card>
</CardGroup>

## How Actions Work

Action steps:

1. **Receive data** from previous steps or trigger events
2. **Execute the action** (send email, make API call, etc.)
3. **Produce output** that can be used by subsequent steps
4. **Continue execution** to the next connected step

<Note>
  Action steps can use workflow variables to create dynamic, data-driven actions. Use the variable picker to insert variables into action configurations.
</Note>

## Action Output

Some action steps produce output that can be used in subsequent steps:

* **HTTP Request**: Returns the response body, status code, and headers
* **Send Email**: Returns email delivery status
* **Slack Message**: Returns message timestamp and channel information

<Tip>
  Use action output in subsequent steps to create workflows that react to API responses or service status.
</Tip>

## Error Handling

If an action step fails:

* The workflow execution stops
* Error details are logged for debugging
* You can use flow control steps to handle errors gracefully

<Warning>
  Always test action steps with valid data before deploying workflows to production. Invalid configurations can cause workflow failures.
</Warning>