Workflows
A workflow is automation that runs on your time data. Instead of hand-categorising entries, remembering to send the weekly report, or manually assigning time to projects, you define a rule once and the platform handles it — routine work done by rule, not by hand.
Workflows are the automation layer of the TimeCampus extensibility model, sitting on top of channels (data in), applets (functionality), and widgets (visualization).
The workflow model
Every workflow follows the same four-part shape:
| Part | What it is | Example |
|---|---|---|
| Trigger | The event that starts the workflow | A new time entry is recorded; it's Friday 17:00 |
| Conditions | Checks that must hold for the workflow to proceed | The entry mentions a client name; weekly tracked time exceeds a threshold |
| Actions | What the workflow does | Categorise the entry; assign it to a project; send a reminder |
| Outputs | What the workflow produces | A notification; a scheduled report; an updated record |
Read it as a sentence: when the trigger fires, if the conditions hold, do the actions, producing the outputs.
What workflows are for
The recurring jobs workflows are designed to take off your plate:
- Smart categorisation — classify time entries automatically based on their context, so the Timeline and Analytics stay accurate without manual sorting
- Project assignment — route time to the right project by rule, keeping budgets and billable time honest with zero bookkeeping
- Reminders — nudge yourself: log the afternoon, take the break, close out the week
- Notifications — get told when something crosses a line you care about, through the platform's in-app and email notification channels
- Scheduled reports — have your weekly summary or client timesheet generated and delivered on a schedule instead of assembled by hand — see Reports
- Integration automation — connect workflow outputs to the tools around TimeCampus
The Workflows page
Open Workflows in the app at app.timecampus.com. This is where your workspace's automations live — the surface for defining a workflow's trigger, conditions, actions, and outputs, and for seeing what's set up.
Workflows are workspace-scoped and governed by the same access control as everything else: what a workflow can touch is bounded by your workspace, and managing automations requires the appropriate permissions.
Workflows and privacy
Workflows operate on the same data you already see — nothing more:
- A workflow can only act on data within your workspace, under your role's permissions
- Workflows don't create new capture; what data exists is governed by your channels and privacy settings
- Automation actions are subject to the same audit trail as manual actions — see Access control
What works today vs. what's rolling out
The Workflows page is part of the app surface today.
The workflow engine — persisted workflow definitions (trigger, conditions, actions, outputs), automatic execution, and a run history you can inspect — is still being built. Today the Workflows page is a UI surface: you can see where automations will live, but defining a workflow doesn't yet persist a rule or execute anything. Smart categorisation that learns from your corrections and the broader AI-assisted automation described on the roadmap ship progressively with the engine.
If automation is central to how you'd adopt TimeCampus, the triggers → conditions → actions → outputs model above is the committed shape — plan your rules against it.