Skip to main content

Automations in JUNE

The Automation module in June allows you to fully automate processes based on database activity. This article provides an overview of the module's structure and explains the core concepts.

Written by Anni Wild

šŸ’” For our english speakers: please use english subtitles or AI translations, since the video is in german.


Prerequisite: Database Reference

Automations in June are always linked to a database. Before creating an automation, a database must therefore be selected. The configuration takes place in the sidebar under Data Platform. From there, navigate to the Automations section, select the desired database, and open the Automations tab.


Action Groups

Within the Automations area, automations can be organized into Action Groups (also referred to as Workflow Canvasses). New action groups can be created using the + icon at the top. It is recommended to give action groups meaningful names, e.g. "DOI" for double opt-in flows, to maintain a clear overview as the number of automations grows.


Structure of an Automation

Every automation follows the same three-part principle:

1. Trigger Defines the condition under which the automation starts.

2. Condition (optional) Restricts which contacts or segments the automation applies to.

3. Service (Action) Specifies what is executed once the trigger and condition are met.


Available Triggers

Category

Description

Data Activities

Contact is added to, updated in, or deleted from a database

Status Updates

New tag assigned, subscription change, etc.

User Activities

User interactions such as link clicks or email opens

Website Activities

Conversion goals or defined interactions from Google Analytics

Webhook Endpoints

Triggered by an external system

Email Activities

Bounce, spam filter activation, or reply to an email

Campaign Activities

Start, goal reached, or end of a campaign

Schedule Trigger

Time-based activation over a defined period

Cronjobs

Regular imports from external sources or recurring actions for databases/segments


Conditions

After selecting a trigger, a condition can be added via Add Condition, e.g. segment membership. Segments can be selected directly in the canvas or created from scratch.


Available Services

Category

Examples

Messages

Send emails

WhatsApp

Send WhatsApp messages

Database Actions

Update fields

Other

Time delay, A/B split

Integrations

Connect external services

Once a service is selected, its settings can be configured directly in the canvas, e.g. the content and recipients of an email.

Did this answer your question?