---
title:  How to Set Up In-App Automations
description: "In-App Automations let you set up \"when this happens, do that\" rules for your app. You build each rule once in the Control Panel, and from then on it runs by itself for every member, on every device. No coding needed."
---

[Skip to content](https://help.appdocumentation.com/-how-to-set-up-in-app-automations#main-content)

English - United States

Show submenu for translations

![app-documentation](https://help.appdocumentation.com/hubfs/app-documentation-1.svg)

Open main navigation

Close main navigation

- English - United States
  
  Show submenu for translations

 How can we help you?

- There are no suggestions because the search field is empty.

1. [App Documentation](https://help.appdocumentation.com/?hsLang=en-us)
2. [Manage Your App](https://help.appdocumentation.com/manage-your-app?hsLang=en-us)

# How to Set Up In-App Automations

## Make your app do things on its own when your members take action, like signing up, making a purchase, or opening a notification.

 **How to Set Up In-App Automations** 

#### In-App Automations let you set up "when this happens, do that" rules for your app. You build each rule once in the Control Panel, and from then on it runs by itself for every member, on every device. No coding needed.

---

**Example:** When a member in the United States opens your app, automatically ask them to rate it.

| **Step** | **Setting** |
| --- | --- |
| **When this happens** (Trigger) | App launched |
| **Only continue if** (Condition) | Location › Country equals United States |
| **Do this** (Action) | Rate App |

---

### Glossary

- **Automation:** a rule that runs on its own when something happens in your app.
- **Trigger:** the event that starts the automation, such as a member logging in or buying something. Every automation has exactly one.
- **Condition (optional):** a filter that decides whether the automation should keep going. For example, "only continue if the member is in the United States."
- **Action:** what the automation does, such as opening a feature, sending a push notification, or showing the Rate App prompt. Every automation must end with at least one.
- **Run:** one time an automation was started by its trigger.

Steps always run in order, from top to bottom.

---

### Requirements

- Administrator access to your app's Control Panel.

- A plan that includes automations. The number of automations you can create depends on your plan:

| **Plan** | **Automations** |
| --- | --- |
| Trial | 1 |
| Premium | 1 |
| Professional | 3 |
| Enterprise | 10 |

- **A published app.** Automations work in the Control Panel preview right away, but they only run on your members' devices once your app is published.

---

### How to create an automation

#### Step 1: Open In-App Automations

1. Log in to the Control Panel.
2. Go to **In-App Automations**. You'll see two tabs:
3. **Automation Flows:** where you build automations and turn them on or off.
4. **Automation Runs:** a history of every time an automation ran.
5. Click **New automation**. A blank automation called "Untitled automation" opens.

#### Step 2: Choose a trigger

1. Click **Choose a Trigger**.
2. Choose the type of event:
3. **App Events:** something that happens in your app, like a member signing up or opening a notification.
4. **Plugin Events:** something that happens inside one of your features, like a chat room being created.
5. Click **Next**.
6. Pick the event from the list. For **Plugin Events**, choose the feature first, then the event.
7. Click **Save Trigger**.

**App events you can choose from:**

| **Event** | **Starts when** |
| --- | --- |
| **App launched** | A member opens the app. |
| **First home run** | The home screen opens for the first time on a device. |
| **User registered** | A member signs up. |
| **User logged in** | A member logs in. |
| **Purchase started** | A member starts an in-app purchase. |
| **Purchase completed** | An in-app purchase goes through. |
| **Tag assigned** | A tag is added to a member. |
| **Tag removed** | A tag is removed from a member. |
| **Push notification opened** | A member opens a push notification. |
| **Push notification action tapped** | A member taps the button inside a push notification. |
| **Short link opened** | The app is opened from a short link. |
| **File uploaded** | A member uploads a file. |

**Plugin events** come from features that support automations. When you choose **Plugin Events**, you'll only see features that offer at least one event.

**Tip:** To change the trigger later, click the three dots menu on the trigger card and choose **Change trigger**.

#### Step 3: Add a condition (optional)

Use a condition when you only want the automation to continue for certain members or situations.

1. Click the **+** on the line under the trigger and choose **Add Condition**.
2. Fill in the rule:
3. **Variable:** what to check, such as the member's country or tags.
4. **Check to perform:** how to compare it, such as **equals**, **contains**, or **is not empty**.
5. **Value:** what to compare it to, such as "United States." Some checks, like **is empty**, don't need a value.
6. Add more rules if needed. **All** rules must be true for the automation to continue.
7. Click **Save**.

**Good to know:**

- If a condition isn't met, the automation simply stops at that step. Nothing went wrong; there was just nothing to do.
- Text checks ignore capital letters by default, so "VIP" and "vip" match. Turn on **Case-sensitive** if the difference matters.
- To check for one thing **or** another, create a separate automation for each.
- When checking a member's tags, the rule looks at all of their tags. "Tag name equals vip" is true if any of the member's tags is vip.

#### Step 4: Add an action

1. Click **+** and choose **Add Action**.
2. Choose what the action should do. You can:
3. Open a feature or a web link
4. Send a push notification
5. Show the Rate App prompt
6. Start an in-app purchase
7. Send an email or text message, call a number, or start a chat
8. Get directions
9. Open the Login, Search, Notes, Bookmarks, Notifications, or Settings screen
10. Open a social media link
11. Do something inside a feature without opening it, like adding a member to a group (only shown when your app has a feature that supports this)
12. Fill in the action's details.
13. Give it a clear **Action Name**, such as "Welcome push." This name appears on the step and lets later steps use its result.
14. Click **Save**.

**Note:** If an action fails, the automation stops there and the steps after it don't run.

#### Step 5: Add more steps (optional)

- Click **+** at the bottom to add another condition or action.
- To add a step between two others, click the **+** on the line between them.
- To change a step, click its **three dots** menu and choose **Edit**, **Duplicate**, or **Delete**.

**Remember:** Every automation must end with an action.

#### Step 6: Personalize your actions (optional)

You can fill in details from the event automatically, like greeting a member by name. When setting up an action or condition, pick a value from the variables list and it will be added as a placeholder in double curly braces.

| **Placeholder** | **What it fills in** |
| --- | --- |
|  | The member's first name |
|  | The city the member is in |
|  | Information from a feature's event, here a chat room |
|  | The result of an earlier step named "Welcome push" |

For example, a push notification message could say: *Hi , welcome back!*

**Good to know:** Each step's placeholder name comes from its Action Name, in lowercase with underscores instead of spaces. "Send welcome email" becomes send\_welcome\_email. If you rename a step, check any later steps that use it.

**Expressions (advanced):** Choose **Add Expression** from the **+** menu to create a value from the data you have, like a custom message or a calculation, and pass it to later steps. Use a test to see what an expression produces.

#### Step 7: Test your automation

1. Click **Test** in the top bar.
2. Enter sample information for the event, such as a member's email and country.
3. Choose how to test:

| **Mode** | **What it does** |
| --- | --- |
| **Dry run** | Check every step with your sample information. **Nothing is sent or saved.** |
| **Live run** | Runs every action for real, exactly as it would for a member. **This can't be undone.** |

Review the results. For each condition, you'll see the **Expected** value next to the **Actual result**, so you can see why it passed or stopped.

**Note:** You don't need to save before testing, and testing never saves your changes.

#### Step 8: Save and turn it on

1. Click **Save**.
2. Keep the suggested name or enter your own. Each automation needs a unique name of up to 100 characters.
3. Turn on **Activate immediately after saving** to start it right away, or leave it off to save it as a draft.

**Note:** You need to publish your app to reflect automation changes to devices.

---

### How to manage your automations

Go to the **Automation Flows** tab to see all your automations. Each one shows its trigger, its actions, and how often it has run, for example "Last ran 2 hours ago · 140 runs in the last 30 days."

| **To** | **Do this** |
| --- | --- |
| Turn an automation on or off | Use the **Activate** switch. A turned-off automation keeps its settings but doesn't run. |
| Edit it | Click **Edit** or the automation's name. |
| Make a copy | Click **Duplicate**. This is hidden once you've reached your plan's limit. |
| Delete it | Click **Delete** and confirm. **This can't be undone.** |

**Versions:** Each time you save an automation, its version number goes up (V1, V2, V3…). Every run shows which version ran, so you can tell whether it used your latest changes.

---

### How to view run history

Go to the **Automation Runs** tab to see every time an automation ran, newest first.

1. Filter by date, automation, or status. Click **Date** to change the order.
2. Check the **Status**:
3. **Success:** the automation finished, or stopped because a condition wasn't met.
4. **Error:** a step failed and the automation stopped there.
5. Check the **Execution Steps** column to see how far each run got.
6. Click **View** to see every step, with the information that went in (**Data In**) and came out (**Data Out**). This is the quickest way to find out why an automation stopped.

**Note:** Run history is kept for 30 days.

---

### What your members will see

Nothing, until an action runs. Members never see triggers or conditions. They only see the result of your actions, such as a feature opening, a push notification, the Rate App prompt, or a purchase screen.

Automations run on the member's device while they're using the app. If the same event happens again before the automation has finished on that device, the new one is skipped.

---

### Pro tips

- **Always start with a dry run.** It checks every step without sending anything to your members.
- **Save as a draft first.** Leave **Activate immediately after saving** off while you're building, then turn it on from **Automation Flows** when you're ready.
- **Plan for missing information.** Member and location details are only available when the member is logged in and has agreed to tracking. Add an **is not empty** condition before steps that rely on them.
- **Match tags the way they're saved.** Tags are saved in lowercase with dashes instead of spaces. To match "VIP Member," use vip-member.
- **Give actions clear names.** "Welcome push" is much easier to find and reuse than "Action 1."

---

### Troubleshooting

**My automation didn't run.** Check the following:

1. Is it turned on? Check the **Activate** switch.
2. Is your app published? Automations only run on members' devices in the published app.
3. Are you testing **User registered** or **User logged in**? These only work in the published app, not in the Control Panel preview.
4. Did a condition stop it? Check **Automation Runs**. A run that stopped at a condition shows as **Success** with fewer steps completed.
5. Was it already running? A new event is skipped while the same automation is still running on that device.

**Member or location details are empty.** They're only available when the member is logged in and has agreed to tracking.

**My tag condition never matches.** Use the saved form of the tag: lowercase, with dashes instead of spaces.

**I can't save my automation.** The step that needs attention is highlighted. Common messages:

| **Message** | **What to do** |
| --- | --- |
| Choose a trigger to save the automation | Add a trigger. |
| Add an action after the last condition | Add an action at the end. |
| This condition has no rules | Add a rule to the condition, or delete it. |
| This action has no action item | Edit the action and choose what it does. |
| The feature this action calls is no longer in the app | The feature was removed. Edit the action and choose another one. |
| An automation with this name already exists | Choose a different name. |

**"None of your features supports automation yet."** None of your features offer events yet. Use an **App Event** instead, or add a feature that supports automations.

**"Automation Limit Reached."** You've used all the automations your plan includes. Upgrade your plan, or delete an automation to make room.

**I can't find older runs.** Run history is only kept for 30 days.

---

### For developers

Custom features can offer their own events as automation triggers, and their own operations as actions. If you work with a developer, ask them to declare the events in the feature's contract file and send them from the feature's code using the SDK. Once they do, the events appear under **Plugin Events** in the trigger list.

---

### Related articles

- [How to use the Push Notification Action Item](https://help.appdocumentation.com/how-to-use-the-push-notification-action-item?hsLang=en-us)
- [How to use behavioral tags](https://help.appdocumentation.com/how-to-use-behavioral-tags?hsLang=en-us)
- [How to manage in-app purchases in the Control Panel](https://help.appdocumentation.com/how-to-manage-in-app-purchases-in-the-control-panel?hsLang=en-us)

- [Control Panel](https://help.appdocumentation.com/control-panel?hsLang=en-us#main-content)

    - [Navigating the Control Panel](https://help.appdocumentation.com/control-panel?hsLang=en-us#navigating-the-control-panel)
    - [Global Tools](https://help.appdocumentation.com/control-panel?hsLang=en-us#global-tools)
    - [Terms & Policies](https://help.appdocumentation.com/control-panel?hsLang=en-us#terms-policies)
- [Build Your App](https://help.appdocumentation.com/build-your-app?hsLang=en-us#main-content)

    - [Global Settings](https://help.appdocumentation.com/build-your-app?hsLang=en-us#global-settings)
    - [Building Your Apps's Navigation](https://help.appdocumentation.com/build-your-app?hsLang=en-us#building-your-appss-navigation)
    - [Building Your Login Flow](https://help.appdocumentation.com/build-your-app?hsLang=en-us#building-your-login-flow)
    - [Building a PWA](https://help.appdocumentation.com/build-your-app?hsLang=en-us#building-a-pwa)
- [Add Functionality To Your App](https://help.appdocumentation.com/add-functionality-to-your-app?hsLang=en-us#main-content)

    - [Plugins to drive engagement & community](https://help.appdocumentation.com/add-functionality-to-your-app?hsLang=en-us#plugins-to-drive-engagement-community)
    - [Plugins to drive monetization](https://help.appdocumentation.com/add-functionality-to-your-app?hsLang=en-us#plugins-to-drive-monetization)
    - [Plugins to run operations & workflows](https://help.appdocumentation.com/add-functionality-to-your-app?hsLang=en-us#plugins-to-run-operations-workflows)
    - [Plugins to show content & media](https://help.appdocumentation.com/add-functionality-to-your-app?hsLang=en-us#plugins-to-show-content-media)
- [Make Money With Your App](https://help.appdocumentation.com/make-money-with-your-app?hsLang=en-us#main-content)

    - [Overview](https://help.appdocumentation.com/make-money-with-your-app?hsLang=en-us#overview)
    - [iOS/Apple](https://help.appdocumentation.com/make-money-with-your-app?hsLang=en-us#ios-apple)
    - [Android/Google](https://help.appdocumentation.com/make-money-with-your-app?hsLang=en-us#android-google)
- [Publish Your App](https://help.appdocumentation.com/publish-your-app?hsLang=en-us#main-content)

    - [Overview](https://help.appdocumentation.com/publish-your-app?hsLang=en-us#overview)
    - [Android/Google](https://help.appdocumentation.com/publish-your-app?hsLang=en-us#android-google)
    - [iOS/Apple](https://help.appdocumentation.com/publish-your-app?hsLang=en-us#ios-apple)
- [Manage Your App](https://help.appdocumentation.com/manage-your-app?hsLang=en-us#main-content)

    - [Managing Your App’s Users](https://help.appdocumentation.com/manage-your-app?hsLang=en-us#managing-your-apps-users)
    - [Push Notifications](https://help.appdocumentation.com/manage-your-app?hsLang=en-us#push-notifications)
    - [Analytics](https://help.appdocumentation.com/manage-your-app?hsLang=en-us#analytics)
- [Connect External Partners](https://help.appdocumentation.com/connect-external-partners?hsLang=en-us#main-content)

    - [Android/Google](https://help.appdocumentation.com/connect-external-partners?hsLang=en-us#android-google)
    - [iOS/Apple](https://help.appdocumentation.com/connect-external-partners?hsLang=en-us#ios-apple)
    - [Zapier](https://help.appdocumentation.com/connect-external-partners?hsLang=en-us#zapier)
    - [Meta](https://help.appdocumentation.com/connect-external-partners?hsLang=en-us#meta)
    - [Segment](https://help.appdocumentation.com/connect-external-partners?hsLang=en-us#segment)

Copyright © 2026, App Documentation