Actions are the building blocks of all Tines automation stories. Actions can perform a number of functions, including interaction with 3rd-party tools and services. Once you drag an action onto the storyboard in Tines, you have started building your first story in Tines!
Actions emit events to other actions. Actions can either run on a predefined schedule or when they receive an event.
Please note: May 29th we introduced to customers our eighth action type, the AI Action. This video is being updated. In the meantime, you can learn about the eighth action and our AI-powered features here.
There are eight types of actions. Each action type:
is designed to perform a specific action.
has unique configuration options.
can receive and emit events to other action types.
Below is a brief description of each action type.
Action Type | Function |
Send Email Action | The Send Email action sends emails to recipients specified in the action options |
Event Transformation Action | The Event Transformation action has several modes that modify the contents of received events |
HTTP Request Action | The HTTP Request action sends HTTP requests using a variety of methods to a specified url |
Receive Email Action | 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. |
Trigger Action | The Trigger action compares the contents of a field from an incoming Event with predefined rules, when the rules match, an event emit is triggered |
Webhook Action | The Webhook action will emit events it receives through Webhooks (HTTP callbacks) |
Send to Story Action | The Send to Story action sends events to another Tines story (the sub-story). After the sub-story has completed its action, the Send to Story action will emit an event. |
AI Action | The AI Action invokes a secure and private large language model (LLM) on demand. |
👉 For a more detailed description of each action type see here.