---
title: Actions
url: https://www.tines.com/docs/actions/
updated: 2026-03-19T15:54:11+00:00
---

*[tines.com](https://www.tines.com/llms.txt) › [Docs](https://www.tines.com/llms.txt)*

# Actions

*[View on tines.com](https://www.tines.com/docs/actions/)*

## Introduction

Actions are building blocks of automation in Tines. Actions can be configured to perform a variety of tasks, for example: receiving alerts from 3rd-party systems, sending/receiving emails, and interacting with APIs. They receive and emit events, and can run on a schedule or upon receiving an event.

## Action Types

There are eight types of actions. Each action type is designed to perform a specific task. Each action type can receive and emit events to other action types. The action types and a brief description of their function is shown below. For a detailed description of each action, see their dedicated article.

| Action Type | Function |
| --- | --- |
| [Webhook Action](/docs/actions/types/webhook/) | The Webhook action will emit events it receives through webhooks (HTTP callbacks). |
| [HTTP Request Action](/docs/actions/types/http-request/) | The HTTP Request action sends HTTP requests using a variety of methods to a specified URL. |
| [Receive Email Action](/docs/actions/types/imap/) | The Receive Email action, formally known as the IMAP action, emits events when it detects new emails on an IMAP server or when emails are sent to a uniquely generated email address. |
| [Send Email Action](/docs/actions/types/email/) | The Send Email action sends emails to recipients specified in the action options. |
| [AI Agent Action](https://www.tines.com/docs/actions/types/ai-action) | The AI Agent action invokes a secure and private large language model (LLM) on demand. |
| [Event Transformation Action](/docs/actions/types/event-transformation/) | The Event Transformation action has several modes that modify the contents of received events. |
| [Condition Action](/docs/actions/types/condition/) | The Condition action compares the contents of a field from an incoming event with predefined rules. When the rules match, an event is emitted. Further configuration can emit an event when the rules do not match. |
| [Send to Story Action](/docs/actions/types/send-to-story/) | The Send to Story action sends events to another Tines story (the sub-story). After the sub-story has completed its actions, the Send to Story action will emit an event. |