Skip to main content

Automations

Automate coaching workflows. Keep the steps visible.

Build client follow-ups in LaunchSite OS with event triggers, delays, conditions, and actions. Configure a workflow, review what it will do, then activate it and inspect its run history.

Automations
Low energy follow-up Active · Saved just now
Test runSave changes
BuilderRun historySettings
Add action
Choose a step to edit · Drag the handle to arrange
END
END

A workflow you can read

Every step on the canvas,in the order it runs.

The branch that fires when energy drops below five is drawn where you can see it. Select any step to edit exactly what it does, without leaving the diagram.

Automations
Low energy follow-up Active · Saved just now
Test runSave changes
BuilderRun historySettings
Add action
Choose a step to edit · Drag the handle to arrange
END
END

The pieces

Triggers, delays, conditions, actions.

Real practice events start the workflow: a check-in lands, a phase advances, a client goes quiet. What happens next is yours to arrange.

  • 01Triggers fire from events that actually happened
  • 02Delays wait in real time, not on your calendar
  • 03Conditions branch on the client’s own data
  • 04Actions message, assign, or flag for your review

Automations

Multi-step flows that run automatically based on client triggers.

Team Browse templates Build with AI New Automation
Search automations... All Statuses
Total Automations6Across your clients
Active4Across your clients
Paused2Across your clients
Completed38In the last 30 days
Low energy follow-up Trigger: Check-in submitted · 5 steps
Missed check-in reminder Trigger: Check-in inactivity · 3 steps
New client welcome Trigger: Client created · 4 steps

Approval gate

Hold supported message drafts for review.

When a workflow uses an approval hold, its message draft waits for your decision. Other activated actions and scheduled messages can send automatically according to their configuration, so review the channels and steps before turning a workflow on.

  • 01Held drafts wait in a review queue you control
  • 02Edit before approving, or reject outright
  • 03An approval-held step resumes from your decision

Approve before sending 2 waiting

Hold every automated message until you have read it. Nothing is sent until you approve it here.

Approval on
2 messages need a decision Quiet hours are respected
Ava Brooks·In-app·Low energy follow-up

Checking in after today’s update

Hi Ava, I noticed your energy was lower today. How are you feeling this evening?

Approve and sendEdit messageDiscard
Marcus Reed·Email·Missed check-in reminder

Your weekly check-in is ready

When you have a minute, open your check-in and let me know how the week went.

Approve and sendEdit messageDiscard

How automation behaves here

You configure the workflow.The system runs its steps.

An activated workflow can send a message or perform another configured action without you opening the app. Choose its scope deliberately and review its history; a completed send cannot be recalled by pausing the workflow.

  • 01Every workflow is readable as a diagram before it runs
  • 02State-changing steps run from an explicit coach instruction
  • 03Approval holds apply to supported steps when configured
  • 04Runs keep durable history, so you can explain what happened
  • 05Any workflow can be paused or edited without losing its history

Good to know

Choosing the right follow-up workflow

What is an event workflow?

An event such as a submitted check-in starts a sequence. You arrange supported actions, delays, and conditions to decide what happens next. For example, a check-in can start a follow-up that branches on an answer and sends a configured message.

How are scheduled messages different?

Scheduled, birthday, and holiday messages use their configured time and audience. Review the recipients, message, and channels before activation. Their delivery is separate from event workflows, so an event workflow’s approval hold does not also hold scheduled sends.

Your practice, operating clearly

Automate the follow-up you forget when the week gets busy.

Start with one workflow and watch what it catches.