What workflows are available and where do I find them?

Harriet workflows are configured by your team—there are no locked-in templates, but common patterns for onboarding, leave, and data collection are straightforward to set up.

Workflows in Harriet are configured by your team—there are no locked-in templates, which means you build exactly the process you need. However, there are common patterns that HR and IT teams set up most often, and the right combination of skills and triggers makes them straightforward.

Where to find active workflows

Dashboard banner: the top of the Harriet dashboard shows available workflows you can run directly from there.
Chat: type or ask "run a workflow" to see workflows available to you. Only workflows your admin has enabled for your channel appear.
Workflow run history: if you have manage-workflows permission, you can see all runs (in-progress, complete, and failed) in the workflows admin section.
Ticket: if a workflow was triggered by a ticket, its progress is visible on that ticket's timeline.

Common workflow patterns

Ticket-triggered triage

Trigger: new ticket arrives in a specific inbox.
Steps: send an acknowledgement, ask for missing information, assign to the right team.

Onboarding checklist

Trigger: webhook from HRIS when a new starter record is created, or a ticket from HR.
Steps: create an IT access ticket, generate the welcome document pack, send a Slack message to the manager.

Leave or absence handling

Trigger: ticket from an employee requesting leave.
Steps: look up policy by country and employment type, verify entitlement in HRIS, collect any missing dates from the employee, send confirmation.

Compliance and deadline tracking

Trigger: scheduled (e.g. every Monday morning).
Steps: pull items nearing a deadline from a connected system, create tickets for overdue items, notify relevant managers.

Information gathering from a third party

Trigger: ticket or chat.
Steps: main agent gathers what it can from internal systems; delegates outreach to a data-gathering sub-agent that contacts a specific person by Slack DM or email; resumes with the result when they reply.

Example

Your HR team creates a Parental Leave workflow. When a ticket arrives in the Parental Leave inbox, the workflow asks the employee for their planned start and return dates, looks up entitlement, and creates an internal task for payroll—automatically, every time, with no HR admin needing to monitor the inbox.

Guardrails

Building a workflow requires manage workflows permission.
Triggering a workflow from chat requires it to be enabled on that channel by your admin.
If you cannot see a workflow you expect, ask your Harriet admin to check its skill and channel assignments.