Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.digifist.com/llms.txt

Use this file to discover all available pages before exploring further.

Automations are the core of Galantis’s revenue engine. They listen for events in Shopify or the Galantis platform and respond automatically with targeted WhatsApp messages — recovering abandoned checkouts, welcoming new customers, confirming orders, and re-engaging lapsed buyers without any manual work. Every automation is built with a visual, node-based flow editor. Flows are structured around a single trigger, optional branching conditions, action nodes that send WhatsApp templates, and delay nodes that control timing. Once active, an automation runs continuously against every customer who matches its trigger.

​
How automations work

A flow executes one customer at a time, moving through nodes sequentially:
  1. Trigger fires when a qualifying Shopify or platform event occurs for a customer
  2. Delay pauses execution for a defined duration before the next step
  3. Condition evaluates customer or order data and branches the flow YES or NO
  4. Action sends an approved WhatsApp template to the customer
Each node execution is recorded in the activity log with a status of PENDING, SCHEDULED, COMPLETED, FAILED, or SKIPPED — giving a full audit trail per customer per run.

​
Guides in this section

Flow Builder

The visual node-based editor — canvas layout, node types, and flow structure.

Triggers

All nine available triggers and the Shopify or platform events that fire them.

Actions

Action nodes, Delay nodes, and how WhatsApp templates are dispatched.

Conditions

All condition types, YES/NO branching logic, and AND/OR grouping.

Frequency Caps

Preventing over-messaging with per-automation send limits.

Exclusion Rules

Excluding specific lists or segments from an automation entirely.

Activity Tracking

Per-customer node execution history and the full audit trail.

Recipes

Pre-built flow examples for the most common automation use cases.

​
Before building your first automation

Two prerequisites apply to every automation:
  • At least one template with APPROVED status — automations can only send pre-approved WhatsApp templates. See Templates.
  • A clear understanding of the trigger event and the customer behavior it represents — see Triggers before configuring your first flow.
If you are setting up automations for the first time, the First Automation guide walks through a complete end-to-end setup.

​
Compliance

Automations validate customer consent status before dispatching any message. Customers with UNSUBSCRIBED or REDACTED marketing state are skipped automatically, and the skip is recorded in the activity log. Frequency caps apply on top of consent filtering — a customer who is opted in but has already received a message within the cap window will also be skipped. See Opt-in & Consent and Frequency Caps for full details.