Start with a ready-made recipe or build your own. A workflow is work Zip can repeat: find facts in permitted company records, check whether action is needed, write an output, and carry out supported steps. Run it yourself, put it on a schedule, or connect it to a watch. You can see its steps, choose who may use or edit it, and inspect every run.
Describe a repeatable job in Ask Zip and save it under Workflows. Search the saved list, open a recipe to read its steps, and press Run when you want it now. Edit steps opens the full editor so you can customize its instructions, sources, step order, schedule, delivery, and review points.
A step can find a fact and carry it forward without writing a page. An “Only if…” check can stop the remaining steps when no matching records exist, so a quiet week does not create an empty report or unnecessary task.
Write steps create readable content from the records the workflow may use. “Do something” steps can publish, send, assign a task, add a key date, or share a document where that action is supported. You set the destination and audience instead of leaving Zip to guess.
Run a saved workflow yourself, choose a day and time for a repeating run, or use a watch to start it when a monitored condition becomes newly true. A scheduled workflow runs under its creator’s company access; action steps follow the workflow’s unattended-action setting.
Edit steps takes you into the full workflow editor. The map shows when the job starts, what each step does, and where the result goes. Change the recipe before you run it: the wording, data it draws on, order, schedule, audience, and review points are yours to set.
Write a document section, work out an answer without writing, continue only if a condition is met, or do a supported action. Add, remove, and reorder steps as the job changes.
Rename it, rewrite its instructions, and choose company data or your own sources with Draw on. The map updates from the same recipe, so you can see the full sequence.
Run it when you press it, set a repeating day and time, or use a watch. Choose whether writing stays in the current document or becomes its own, and whether to publish or send it.
Mark a step Stop here and let me read it. Set who can use or edit the workflow, and review outward actions before they reach people when your settings require it.
Set an individual step to pause for review. “Ask before acting” can require a yes before changes or sends. On unattended schedules, action steps remain proposals until unattended action is enabled; the action is still checked against the person’s access.
Who can use a workflow decides who may see and run it. Who can edit it decides who may change its steps, schedule, or name. An owner or admin can set the company-wide editing rule and make an exception for a particular workflow.
Saved workflows retain their previous versions. If an edit removes a needed check or changes the audience, open the history in the editor and restore a version you trust.
Jobs started through Ask Zip remain in Your jobs after you close the chat. Open What I did for the steps and results. Scheduled workflows also keep a run result. Stop a live job, pause a repeating schedule, and undo supported logged actions when available.
One saved workflow, with a result your team can check each time it runs.
Work it out: look for onboarding tasks that are overdue within the company's permitted records and remember who needs attention.
Only if there are overdue tasks does the workflow continue. If there are none, the run records that outcome instead of sending a blank follow-up.
Write a summary and prepare a task or message for the people responsible. Review the recipients, wording, and due date whenever the step or action settings require approval.
Open the job to see what was completed, skipped, or left waiting for you. Change the saved recipe if the next run should work differently.
Browse by area, then open any name to see what it does, when it is set to run, and the steps in its recipe. These are starting points: run one yourself, adjust its schedule or delivery, and use Edit steps to tailor the work to your company.
What's been published, grouped by category — is one category doing all the talking.
Runs monthly.Where a human had to fix the AI, and what they told it — the system's own error rate.
Runs monthly.What's been uploaded and is actually available for Zipp to draw on.
Runs when you press it.What's been published but barely opened — a signal it's not landing.
Runs monthly.Summarizes where the current plan year stands, then posts a reminder to everyone.
Runs when you press it.How many days until the plan year needs to be decided, and what's still outstanding.
Runs when you press it.What's been published to the company recently, and by whom.
Runs monthly.Every deadline or event on the calendar in the next 30 days.
Runs weekly.The real, anonymous questions people are asking Zipp — the clearest signal of what's confusing.
Runs weekly.Everything waiting on a decision right now, and how long it's been waiting.
Runs weekly.Who's missing required training or a certification that's expired or expiring soon.
Runs monthly.Contracts where the chance to give notice has already closed — the ones locked in for another term.
Runs monthly.Every insurance policy or licence with a notice or end date coming up.
Runs monthly.Every audit currently running, its owner, and how close it is to done.
Runs weekly.Individual audit steps that are overdue right now.
Runs weekly.Everything set to renew itself if nobody intervenes — a deliberate decision list.
Runs monthly.The highest-value contracts and licences currently in force.
Runs monthly.Commitments with days_to_end closing in and auto_renew off — someone needs to decide.
Runs weekly.Every contract or licence where the notice window is closing within 30 days.
Runs weekly.The biggest individual spend line items, not totals — the outliers worth a second look.
Runs monthly.What the company spent last month, broken down by department and category.
Runs monthly.Where the money's actually going, by category rather than department.
Runs monthly.Is spend trending up or down, department by department.
Runs monthly.Money going out that isn't tied to any tracked commitment — a real audit gap.
Runs monthly.New parties added to the record recently.
Runs monthly.Who the company deals with, grouped by which department owns the relationship.
Runs when you press it.Cumulative spend per department for the year so far.
Runs monthly.What badges exist, whether each is active, and what triggers it — useful before a recognition push.
Runs when you press it.A clean, current roster for one department — names, titles, tenure.
Runs when you press it.Anyone marked inactive who's still showing up in other reports — a data-hygiene check.
Runs monthly.A plain-language summary of the most recent survey's results — themes, not who said what.
Runs when you press it.Headcount by department, then who's still ramping up in onboarding.
Runs monthly.Recognition given out in the last 7 days.
Runs weekly.Who started this week and what's on their plate.
Runs weekly.Who's been recognized, how often, and for what — and who hasn't been recognized at all.
Runs monthly.Every open request and how long it's been waiting, oldest first.
Runs weekly.What people are actually asking HR for, grouped by kind.
Runs monthly.How many people actually answered the last survey, out of how many it went to.
Runs when you press it.Who's celebrating a work anniversary this month, then a note to celebrate them.
Runs monthly.A plain-language summary of the current time-off policy, ready to repost.
Runs when you press it.What share of people who joined actually finished the current challenge.
Runs when you press it.Who joined the current wellness challenge and who's actually finishing it.
Runs when you press it.Licence seats or equipment with no recorded use at all.
Runs monthly.Equipment or seats whose cost is actually locked in by a commitment.
Runs when you press it.What equipment and licences each department is actually holding.
Runs when you press it.Equipment whose warranty has already run out.
Runs monthly.The most expensive things the company owns or leases seats of.
Runs when you press it.What the company owns and pays for, added up.
Runs monthly.Software seats nobody has opened in a long time — money going nowhere.
Runs monthly.Equipment whose warranty runs out in the next 60 days — worth a decision before it lapses.
Runs monthly.How people are scoring on certifications — is the bar too easy or too hard.
Runs monthly.Anyone whose certification has already lapsed — a real compliance gap.
Runs weekly.Anyone whose certification expires in the next 30 days.
Runs weekly.Anyone who should have a course assigned by now but doesn't.
Runs weekly.Training completion rates, broken down by department.
Runs monthly.Every onboarding/offboarding journey right now, grouped by whether it's on track.
Runs weekly.Onboarding that's been active for over 30 days and still isn't done.
Runs weekly.Tasks that say a role but have nobody actually assigned — the ones that quietly never happen.
Runs weekly.Roleplay/practice scores — who's ready for real conversations and who needs more reps.
Runs monthly.What's due in onboarding this week, across everyone currently ramping up.
Runs weekly.Whose training is coming up for spaced-repetition review in the next week.
Runs weekly.Who's stuck — low mastery scores or repeated attempts on the same course.
Runs monthly.Who's behind on onboarding tasks right now, and by how much.
Runs weekly.Which running project actually has the most moving parts.
Runs when you press it.A single cross-cutting view: onboarding tasks, project tasks, certifications and key dates all due this week.
Runs weekly.Every incident logged this month and its current status.
Runs monthly.Every workstream that's a launch or hiring round, and where it stands.
Runs weekly.What started this month that wasn't running before.
Runs monthly.Every active project, its owner and how close to done it is.
Runs weekly.Individual project tasks that are overdue right now, across everything running.
Runs weekly.What's actively running in each department right now.
Runs weekly.Projects that haven't had a task completed recently — the ones quietly stalling.
Runs weekly.One click, the whole business at a glance — people, money, pipeline and operations, each in a short section up top.
Runs weekly.One click, the full compliance picture — certifications, audits, contracts — ranked by real risk, not by date.
Runs monthly.One click, the full equipment and licence picture — total cost, waste, and risk — compiled and summarized.
Runs monthly.One click, the full HR picture — headcount, onboarding health, culture and open requests, compiled and summarized.
Runs monthly.One click, how everyone hired in the last 30 days is actually doing — onboarding, training and early engagement, compiled and summarized.
Runs weekly.One click, the full picture of what's running — status, what's stuck, what's new — compiled and summarized.
Runs monthly.One click, the full spend picture — by department, by category, the trend, and what's coming up — compiled and summarized.
Runs monthly.One click, the full pipeline picture — by stage, by owner, momentum and losses — compiled and summarized.
Runs monthly.What's expected to close in the next 30 days, and its total value.
Runs monthly.Deals nobody has touched in over two weeks — the ones at real risk.
Runs weekly.Open deals with the oldest last_activity_on — the ones quietly dying.
Runs weekly.Deals marked lost this quarter and the reasons given.
Runs monthly.Fresh pipeline — what's come in this month that wasn't there before.
Runs monthly.Every open deal, grouped by stage, with total value in each.
Runs weekly.Who's carrying how much open pipeline right now.
Runs weekly.Open pipeline value adjusted for how likely each deal actually is to close.
Runs weekly.Who's closing the most value this quarter.
Runs monthly.Which parties currently have an open deal against them.
Runs when you press it.A workflow can turn live company records into a document, a decision to stop, or a supported action in the employee experience. The saved recipe tells people what is supposed to happen; the job record shows what actually happened. Missing records, failed steps, and approvals that still need you remain visible.