A trigger in any app. Conditions if you need them. Actions that follow. Personal workflows for you. Office workflows if you can publish them. The run log shows what fired.
Any app can be the start. Any app can be the next step.
Something was created, a status changed, a person was assigned, a form came back, a request was approved. Projects is one place this already runs. Help Desk, Vendors, Workforce, Time Off, and the rest of the stack work the same way.
Notify someone in Chats. Add people to a project with a project role. Assign a Help Desk ticket. Start onboarding tasks. Send a form. Send mail. Post to a feed. One workflow can take several steps, in order.
Only if the status is this. Only if the tag was added. Only if it came from that template. Leave the filters blank and it always runs. Branch if you need a different path when it does not match.
Trigger, conditions, then the actions in a line you can see. Click a step to set it. Add another action. Reorder. Turn the whole thing off without deleting it.
Build a workflow that only runs for you. If you have permission, publish one for the office so it runs for everyone. Personal stays yours. Office is the shared set.
Daily, weekly, monthly, or at a time you pick. Or wait a day after the trigger before the next action. Accruals, reminders, and follow-ups do not need someone to remember.
What fired, when, and whether it worked. Test a workflow before you turn it on. If a run fails, the error sits on the log and the people you named get told.
Post as the person who triggered it, or as the system. Drop in the project name, the client, the status, whoever was assigned. Starter templates for common office jobs, then you change them.
Pick the trigger. Filter it. Stack the actions. Turn it on.
Trigger
A record is created, a status moves, someone is assigned, a form comes back, or the clock hits the time you set. Pick the app and the event.
Filter
Add conditions so it does not fire on every change. Branch to a different set of actions when it does not match. Skip this if every event should run.
Act
Notify, assign, add people, send a form, post, create a task, send mail. Stack as many as you need. Each one can hit a different app.
On
Run a test. Keep it personal, or publish it for the office if you have permission. The log shows every run. Turn it off without deleting it.
The Workflows app is the trigger and the actions. The work still lives in the other apps.
A project is created or a status changes. Add the team with project roles, post to the feed, send a form, archive the chat when the job closes.
A request lands. Assign it, notify the queue, move the status. Nobody has to see it first to get it started.
Someone is hired. Assign the onboarding tasks, notify the manager, drop the files that belong on day one.
A bill comes in. Notify the approvers, request the missing document, post when it is paid.
A request is submitted, or the calendar hits the schedule. Notify the manager, or add time to a bank without someone doing it by hand.
Post the message, mention the people, run as the person who triggered it or as the system. The feed is often the action, not only the log.
Included with Base Assist. No seat fee.
Free
Included with Base Assist. No seat fee, no plan to pick.
The Workflows app is free. There is no plan to pick and no per-person charge. Actions that create a project, send mail, or touch another app still need that app licensed. Personal workflows are yours. Office workflows need permission to publish.
Need more than one app? Estimate a monthly total.
How the Workflows app is set up in Base Assist.
No. The Workflows app is included. No seat, no plan. The other apps it can trigger or act in are licensed on their own.
No. Projects is one place a workflow can start or finish. Help Desk, Workforce, Vendors, Time Off, Chats, and the rest of the stack work the same way. A workflow can start in one app and act in another.
Personal workflows run for you. Office workflows run for the firm. Anyone can build a personal one. Publishing an office workflow takes permission, so not every automation becomes company policy by accident.
Yes. The run log shows what fired, when, and whether it worked. Test before you turn it on. If a run fails, the error stays on the log and the people you named get told.
The Workflows app is free. If an action creates a project, sends mail, or assigns a ticket, you need that app. A workflow cannot do work in an app the office does not have.
Triggers, conditions, actions, personal and office workflows, schedules, and the run log.