Platform Automation Flows
Navigate to Communications → Automations to manage platform-level automation flows. These are completely separate from gym-level member automations.
Purpose
Platform automations handle the operational relationship between Bliply and gym owners/leads. They automate lifecycle communications that would otherwise require manual follow-up.
Current Flows (10)
| Flow | Trigger | Email Template | When It Fires |
|---|---|---|---|
| No SaaS Contract Reminder | no_saas_contract | No SaaS Contract Reminder | 7 days after activation with no signed contract |
| Gym Set Inactive Notice | gym_set_inactive | Gym Set Inactive Notice | When gym status changes to Inactive |
| Demo Reminder (24h) | demo_reminder | Demo Reminder | 24 hours before scheduled demo |
| Demo Attended Follow-Up | demo_attended | Demo Attended Follow-Up | After demo is marked "Completed" |
| Demo No-Show Follow-Up | demo_no_show | Demo No-Show Follow-Up | After demo is marked "No Show" |
| Migration Stale Reminder | migration_stale | Migration Stale Reminder | 14 days of no migration progress |
| Payment Failed Notice | payment_failed | Payment Failed Notice | When Stripe reports a failed charge |
| Subscription Renewal Reminder | subscription_renewal | Subscription Renewal Reminder | 14 days before subscription renewal date |
| Trial Expiring Notice | trial_expiring_soon | Trial Expiring Notice | 7 days before trial period ends |
| Support Ticket Resolved | ticket_resolved | Support Ticket Resolved | When a ticket status is set to "Resolved" |
Flow Architecture
Each platform automation flow uses a trigger → action → exit node architecture:
- Trigger Node — Defines the event and any time-based configuration (e.g.
no_saas_contract_days: 7,renewal_days_before: 14) - Action Node — Executes an action such as:
- Send Email — References a Platform Email Template by name for late-binding resolution
- Send SMS — Sends via the platform Twilio integration
- Send WhatsApp — Choose to send via Twilio or WhatsApp Business Cloud API on a per-action basis. Configure both providers in Settings → Integrations.
- Exit Node — Marks flow completion
Status Management
| Status | Meaning |
|---|---|
| Draft | Flow exists but will not fire — use for testing or staging |
| Active | Flow is live and will trigger on matching events |
| Paused | Temporarily disabled — existing runs may still complete |
Monitoring
Each flow shows run history: how many times it has fired, success/failure counts, and the most recent run timestamp. Check this periodically to ensure automations are working correctly.