HyoNovaDocumentation

Automation

Planned — company-wide automation workflows with triggers, actions and approvals. What runs automatically today, in Work reminders and Mail automations.

PlannedOn the HyoNova roadmap. Not built yet and has no release date.ConceptFor: Owners, Admins, Managers, EvaluatorsLast updated:
On this page

Automation workflows are planned as rules that run your company's routine processes for you: when something happens, HyoNova does the next steps — and stops for a person's approval where a decision matters.

What runs automatically today#

Two things in HyoNova already happen without someone clicking each step:

  • Task reminders in Work. Once a day, people assigned to an open task receive a reminder in Notifications when the task is due tomorrow, and another when it is overdue. Each reminder is sent once per task per day. See Tasks.
  • Mail automations. In Hyo Mail, an email journey can start when a contact joins a list, an attribute changes, a date in an attribute is reached, a sign-up form is submitted, or a campaign is opened or clicked, then send emails, wait, change lists and update attributes. These journeys are about email and Mail contacts only. See Mail automations.

Apart from these and ordinary notifications — such as when you are assigned a task or mentioned in a comment — nothing changes a task, moves work between people or creates records automatically. A person makes every move in the Work task flow.

Automation is not the Work task flow#

  • The Work task flow is available today. Every task moves between Open, In progress, Blocked, Completed and Cancelled, and a person always makes each move. See Tasks.
  • Automation workflows are planned. They would be rules your company designs, started by an event, that can act across HyoNova — not only in email — without someone clicking each step.

For a comparison with the planning views, see Planning views and what's next.

The planned building blocks#

Building blockWhat it is intended to beExample
TriggerThe event that starts a workflowA task becomes overdue; a new customer is added; a form is submitted
ActionA step HyoNova performsCreate a task, assign it, notify a person, update a status
ApprovalA pause until a named person approves or rejectsA manager approves before an expense is reimbursed

The examples show the kind of process automation is meant for. The actual triggers and actions available will be published when automation is released.

Principles#

  • People stay in charge of decisions. Approval steps are part of the design, so a workflow can wait for a person before it continues.
  • Permissions still apply. Workflows are intended to respect your company's roles and permissions.
  • Nothing happens silently. Workflows are intended to leave a record you can check, as Mail automations do today with their runs.

How automation is intended to connect#

  • Work. Create and route tasks; follow up on blocked or late work beyond today's reminders.
  • Customers and Support. Follow up with customers and act on support events beyond the routing rules that HyoNova Support already has.
  • Mail. Start an email journey from an event elsewhere in HyoNova, not only from Mail's own triggers.
  • Serene. Planned AI agents could carry out defined steps, always with human approval. See Serene AI.

Status#

FeatureStatusNotes
Automation workflowsPlannedOn the HyoNova roadmap. Not built yet and has no release date.Triggers and actions that run company processes, with approvals.
↑↓ to navigate · Enter to open · Esc to close