Workflows¶

Premium Feature

Workflows require a Premium subscription.

Workflows automate document generation with visual pipelines. Build a sequence of steps once, and Mossie runs it on schedule -- pulling data, processing it through your assistants, and saving the result as a ready-to-review document.

What Workflows Do¶

A workflow is a sequence of connected steps that runs automatically. Instead of manually gathering notes, running an assistant, and saving the output every week, you define the process once and let Mossie handle it.

Example: Every Friday at 3 PM, pull this week's activity log, run it through your "Weekly Summary" assistant, and save the result as a document.

Trigger Types¶

Every workflow needs a trigger -- the event that starts it running.

Trigger	Description
Manual	Run anytime by tapping Run Now
Scheduled	Runs automatically at a set time -- Daily, Weekly, or Monthly

For scheduled triggers, you specify:

Time of day -- When the workflow should run
Day -- Which day of the week (for weekly) or day of the month (for monthly)

Building a Workflow¶

Workflows are visual graphs of connected nodes. Each node performs one step, and you connect them to define the flow.

Node Types¶

Context Nodes¶

Pull data into the workflow:

Activity Log -- Your logged activities for a time period (this week, this month, etc.)
Student Notes -- Notes for a specific student or class
Calendar Events -- Upcoming events from your schedule

Assistant Nodes¶

Run a Custom Assistant on the incoming data:

Select any Custom Assistant you have created
The data from the connected Context node becomes the assistant's input
The assistant generates output based on its instructions

Template Nodes¶

Apply a document template to structure the output:

Choose from your saved templates
The template formats the content with consistent headings and sections

Output Nodes¶

Save the result:

Create Document -- Save as a new document in your workspace
Set a title pattern (e.g., "Weekly Summary - {date}")

Connecting Nodes¶

Drag from one node's output to another node's input to connect them. Data flows from left to right through the graph.

Example: Automated Weekly Summary¶

Here is a step-by-step example of building a useful workflow:

Add a Context node -- Select Activity Log and set the time range to This Week
Add an Assistant node -- Select your "Weekly Summary" Custom Assistant and connect it to the Context node
Add an Output node -- Choose Create Document and set the title to "Weekly Summary - {date}"
Set the schedule -- Weekly, Friday, 3:00 PM

When Friday afternoon arrives, Mossie:

Gathers your week's activity log
Runs it through your Weekly Summary assistant
Creates a new document with the result
Notifies you that the document is ready for review

Monitoring Workflows¶

Status¶

Each workflow shows:

Active or Paused -- Whether the workflow will run on schedule
Last run -- When it last executed
Next run -- When it will run next (for scheduled workflows)

Execution History¶

View past runs to see:

When each run occurred
Whether it succeeded or failed
The document it generated (tap to open)
Error details if something went wrong

Pausing and Resuming¶

Toggle a workflow between Active and Paused at any time. Paused workflows do not run on schedule but can still be triggered manually.

Limits¶

Maximum 10 nodes per workflow
Scheduled workflows on mobile require the app to have background access enabled in your device settings

Tips¶

Start simple -- One context source, one assistant, one output. Add complexity only when you need it.
Test manually first -- Use Run Now to verify the output before setting up a schedule.
Review generated documents -- Automated output is still a draft. Check it before sharing.
Name workflows clearly -- "Friday Weekly Summary" is easier to manage than "Workflow 1."
Reuse Custom Assistants -- The same assistant can appear in multiple workflows.