---
title: "Event-based Automations (Jobs/Events)"
slug: "event-based-automation"
status: "update"
updated: 2025-07-29T10:05:06Z
published: 2025-07-29T10:05:06Z
canonical: "docs.mapp.com/event-based-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.

# Event-based Automations (Jobs/Events)

Event-based automations in Mapp Engage are triggered when a defined event occurs – such as a contact opening a message or an import being completed. Each time the event occurs, the system automatically executes a predefined job.

They are ideal for responding to user behavior or system activity in real time.

---

## How It Works

Each event-based automation consists of:

- **An event** – defines the trigger (e.g. message opened, import finished)
- **A job** – defines what happens in response (e.g. update profile, export data)

Events and jobs must be compatible:

- Some apply per contact, others at system level.
- Some combinations are restricted and must follow the (C)/(S) logic.

For full details, see: [How Contact-Based and System-Based Automations Work (C/S Model)](/v1/docs/contact-c-vs-system-s-automations)

In most cases, event triggers are based on user behavior or system activity. Alternatively, event-based automations can also be triggered via specific API calls. This allows you to start automations programmatically (e.g. after a profile update or group subscription).

For full details, see: [API Calls for Event-Based Automations](/v1/docs/api-methods-for-event-based-automations)

---

## Typical Use Cases

- Send a follow-up message after a contact clicks a specific link
- Add contacts to a group after import completion
- Export message statistics after every sendout
- Increase profile score when a conversion is registered
- Trigger an internal notification after bounce or response