---
title: "Automations overview"
description: "Understand Interlinked Automations, the bounded follow-ups they support, their safety controls, and the difference between drafts and active rules."
section: "Automations and campaigns"
url: https://interlinked-ai.com/en/resources/docs/automations-overview
lang: en
lastUpdated: 2026-08-13
reviewedAt: 2026-08-13
---

# Automations overview

## What Automations are

Open **Automations** in the **AI & Automation** section of the panel. Automations handle a focused follow-up after a bounded event. They complement an AI agent; they do not replace the agent’s normal conversation flow.

Each rule has one trigger, one defined action, and safety limits you can review before activation. Examples currently shown in the panel include:

- **Abandoned cart follow-up** on WhatsApp;
- **Appointment reminder** on WhatsApp;
- **Instagram comment reply**; and
- **Facebook comment private reply**.

Availability depends on the connected channel, agent assignment, permissions, and workspace state. Automations is marked **BETA** in the sidebar, and some comment capabilities may require an additional validation or live test before broader use.

<div class="docs-media-placeholder">
  <p class="mono-label">Screenshot: Automations page with the Automations and Broadcasts tabs, status filters, and New automation action</p>
</div>

## What is already included in normal agent behavior

Story replies and mentions that arrive as inbound conversations are handled by the active agent’s normal routing and policies. They are not a separate story automation in the current panel.

Automations also do not create a hidden replacement for your workflow. The agent, channel, and customer conversation remain the source of the customer-facing response.

## Review the lifecycle

Rules use these statuses:

| Status | Meaning |
| --- | --- |
| **Draft** | Saved for review but not running. |
| **Active** | Eligible to run when its trigger and safety checks match. |
| **Paused** | Temporarily stopped; its configuration remains available. |
| **Needs attention** | The rule needs a channel, permission, template, agent, or other requirement reviewed. |
| **Archived** | Stopped and kept for reference. Historical executions remain visible. |

Use [Automation status and activation](/en/resources/docs/automation-status-and-activation) for the exact transitions and [Create and test an automation](/en/resources/docs/create-and-test-an-automation) for the setup steps.

## Safety controls matter

Depending on the trigger, the wizard can limit replies per user per day, stop when a human takes over, ignore the agent’s own replies, ignore nested comments, cancel an appointment reminder when the booking changes, cap cart attempts, or use an approved WhatsApp template only when the required conditions are met.

These controls are part of the customer experience. Keep the action narrow and avoid overlapping rules that could send duplicate messages.

## Automations and broadcasts are different

The **Broadcasts** tab is a history view for approved WhatsApp template campaigns created from CRM. A broadcast is a recipient campaign; an automation reacts to a future event. Marketing broadcasts require eligible recipients, an approved template, and current marketing consent for every recipient.

Read [WhatsApp marketing campaigns](/en/resources/docs/whatsapp-marketing-campaigns) for campaign eligibility and delivery statuses.

<div class="docs-callout docs-callout-warning">
  <p><strong>NEEDS VALIDATION</strong></p>
  <p>Channel permissions, template approval, and comment capabilities are controlled partly by the connected provider. The panel’s activation readiness message is the current source of truth for your workspace.</p>
</div>