# Apps

> Complete workflows that live inside Campaigns and take over work you repeat every month, using your existing contacts, channels and sending rules.

Source: https://docs.amomic.in/apps/overview

---

A [campaign](/campaigns/overview) reaches a list once. Most of the work a business repeats isn't one-off: it comes around every month, and doing it by hand is the whole problem.

An app, shown in the console as an *automation*, is a complete workflow that lives inside Campaigns and does that repeating work. It keeps its own records, runs on a schedule, and sends through Campaigns when it has something to send.

Apps are part of Campaigns, so they need the **Growth** or **Enterprise** plan.

## What an app is allowed to do

An app isn't a plugin with its own rules. It sends **through Campaigns**, so every message it produces obeys:

- your [sending rules](/campaigns/sending-rules): quiet hours, sending window and weekly per-person cap;
- every opt-out, always;
- approved templates only, outside WhatsApp's 24-hour window.

An app gets convenience, not an exemption. Its messages appear as campaigns with the same per-recipient outcomes as your own.

::: info Apps never change what your agents say
Installing one adds a workspace surface and a schedule. It doesn't touch your agents, their knowledge or their instructions.
:::

## Available now

::: cards
::: card Duesly
**Recurring payments, collected on WhatsApp.** Add the customers who pay you on a cycle, and Duesly raises each payment, reminds them when it's due, follows up if it isn't paid, and stops asking after two follow-ups. [Read the guide](/apps/duesly)
:::
:::

::: note Looking for Google Calendar?
Google Calendar is connected to an appointment booking calendar, not installed as an app. Follow [Connect Google Calendar](/console/google-calendar).
:::

## Installing an app

Admins install Duesly from the **Campaigns** page:

::: steps
::: step Open Campaigns
In the sidebar, open **Campaigns**. Under **What do you need to get done?**, the **Recurring collections** card is Duesly.
:::
::: step Set it up
Press **Set up Duesly**. It installs and opens Duesly's **Settings** tab. You can also open the app's page directly and press **Start setup**.
:::
::: step Finish setup
An app usually needs a little setup before it runs. Until then the card reads **Setup needed**, the app shows the one thing to do next, and nothing is sent.
:::
:::

Duesly needs a connected WhatsApp number, because that's where the reminders go.

There is also an **Automations** page at `console.amomic.in/campaigns/apps` listing every app with what it does, what it needs, and its state: **Not installed**, **Finish setup**, **Running** or **Paused**.

![The Automations page listing Duesly as Running, with what it does for you and Needs whatsapp connected](https://docs.amomic.in/screens/apps/automations.light.webp)

*Every app, what it automates, and what it needs.*

## Pausing

**Pause reminders** in the app's header stops its automations without touching its data. Nothing is sent automatically and no new payments are raised; everything already recorded stays, and **Resume** picks up where it left off. Buttons you press yourself, such as **Remind now**, still send while it's paused.

This is the control to reach for when something went out wrong: stop everything now, keep the history, fix it, turn it back on.

## Uninstalling

There's no uninstall control in the console, and the public API doesn't offer one either. Pausing is the way to stop an app. If you want an app removed from your workspace, or its records deleted, contact support.

## Roles

Installing, setting up, pausing and every action inside an app are admin actions. Members can open an installed app and read its records.

## From your own code

An installed app's data is available over the API. See [Duesly API](/api/apps-duesly).