Built-in automations
Not every automation in Helpin is a flow. Built-in automations are ready-made behaviors that you switch on and configure in settings, rather than build yourself. They keep project records up to date without an agent.
Built-in automations vs flows
Built-in automations | Flows | |
|---|---|---|
Who defines them | Helpin | You |
Where you manage them | Settings | Automation → Flows |
What you can change | Turn on or off, and a few options | Trigger, filters, action, agent and target |
Use an agent | No | Usually |
Use a built-in automation when it does exactly what you need. Build a flow when you need your own trigger, filters or an agent.
Epic automations
Epic automations move epics along as their tasks progress. They apply to the whole workspace.
Go to Settings → Automations (under Projects).
In Epic Automations, turn on the automations you want:
Auto Start Epic – when any task moves to a started state, the parent epic moves to a started state.
Auto Complete Epic – when all tasks in an epic reach a done state, the epic moves to a done state.
If your epic workflow has more than one started or done state, choose the target state from the list next to the switch.
If your epic workflow has no started or done state, Helpin can't turn the automation on and shows an error. Add the missing state to your epic workflow first.
Sprint automations
Sprint automations are set per team.
Go to Settings → Automations. Sprint Settings lists each team and its current sprint automations.
Select Edit → next to a team to open its sprint settings.
Under Automation, choose the options you want:
Roll over unfinished work – when a sprint ends, incomplete tasks move to the next sprint.
Auto-create sprints – Helpin creates upcoming sprints for you. Set how long Each sprint lasts and which day Sprints start on.
The same dialog has Enable sprints, which shows sprints in the sidebar and turns on sprint planning for the team.
Who can change them
Anyone who can open Settings → Automations can see these settings. Changing them requires permission to manage automations, which admins and owners have by default. See Automation permissions and access.
Related articles
Was this article helpful?