---
title: "Basics"
slug: "automation"
updated: 2025-09-10T10:26:24Z
published: 2025-09-10T10:26:24Z
canonical: "docs.mapp.com/automation"
---

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

# Basics

This page provides detailed guidance on using Automations in Mapp Engage. While campaign-driven use cases are better handled through [Whiteboards](https://docs.mapp.com/docs/whiteboards), Automations remain essential for backend tasks, system-triggered actions, and recurring data operations.

---

## Automation Types

When creating an automation, you can choose from the following types:

### Time-Based Automations

Triggered at defined intervals – hourly, daily, weekly, or custom.

Example: Export all newsletter contacts every Monday at 08:00.

### Event-Based Automations

Triggered by specific system or contact events, such as:

- Contact enters or leaves a group
- A message is opened, clicked, or bounced
- An import finishes or a file is uploaded

There are two categories of events:

- **Contact events** (e.g. a specific user opens a message)
- **System events** (e.g. group message finished)

### Profile-Based Automations

Executed when a profile meets specific criteria – e.g. based on attribute values.

Used for:

- Calculating scores (lead scoring, age calculation)
- Mapping values to new fields
- Assigning categories

This type is especially useful for transforming or segmenting data after imports or form submissions.

---

## Automation Structure

All Automations follow a basic structure:

**Trigger → (Optional) Logic → Action**

Logic options include:

- **Wait**: delay between trigger and action
- **Split**: branch paths based on conditions
- **Goal**: define exit condition to stop the workflow early

---

## Available Actions

Automations support a variety of actions:

| **Action Type** | **Description** |
| --- | --- |
| Send Message | Send an email, SMS, or push (not recommended for journeys) |
| Add to Group | Add contact to one or more groups |
| Remove from Group | Remove contact from one or more groups |
| Update Profile | Modify a contact attribute or category |
| Export Data | Send data export via FTP or email |
| Import File | Launch a file import (e.g. scheduled sync) |
| Notify User | Send notification to internal user (email only) |
| Trigger Another Flow | Start a different automation (chaining) |

---

## Common Use Cases

Automations are useful for:

**Data Management**

- Remove inactive or bounced contacts from groups
- Update attributes based on external input
- Apply transformations to imported data

**Scheduled Jobs**

- Perform daily or weekly data exports/imports
- Generate and send internal reports
- Run regular group membership checks

**Backend & System Tasks**

- Notify admins about delivery issues or import errors
- Sync profile values across attributes or categories
- Handle post-import logic (e.g. scoring, validation)