Automations that finish the job

[Amit134]

A new hire starts on Monday. Before they can do anything, someone has to set up their account, add them to the right groups, and give them access to the apps they need. You know the steps. You may have even written them down. But without an automation, every step is a request that waits for a person to pick it up and finish it by hand.

With Flow, you describe those steps once, in plain language: what has to happen, what information is needed, who approves, and which systems are involved. Flow drafts the automation, and your team reviews it, tests it, and publishes it.

After that, onboarding starts with a request in Slack or Microsoft Teams. Flow runs the steps you set, asks for approval where your rules call for it, and leaves a record for IT.

 

Knowledge answers questions. Automations take action.

Flow handles two kinds of work, and the difference decides how each one gets built.

	Knowledge	Automations
Best for	Questions answered in company documents and best practices	Requests with a clear outcome, like access to a SaaS app
What Flow does	Pulls from multiple connected sources and answers in chat	Runs a published workflow that acts inside connected systems
What the employee gets	An answer in the thread	A finished task and a confirmation in the same thread
Guardrails	Admins choose the sources Flow draws from and publish instructions for how it uses them	Each action is checked against access, scope, and any required approval before it runs

Say an HR team wants holiday questions answered from its own policy documents. You don’t need a fully built knowledge base to start, and you stay in charge of how much latitude Flow has. Where that knowledge comes from is a story for another blog.

Why the first automation matters

The first automation is where the loop starts. Someone asks for something that keeps coming back (think of all the token credit increase requests). A team member describes the steps in plain language like a simple standard operating procedure, Flow builds the workflow, and the team tests and approves it before it gets published. The next person who asks gets the outcome without anyone stepping in.

That is where the value compounds. Each automation takes one repeat request off the people who handle requests today. A request is automatically completed following a clear rule, approvals still happen where the rule calls for them, and every run leaves a record. That gives your team time back for work that needs judgment. Start with the request that comes up most often and has the clearest outcome.

“Flow could help FNMOC cut through red tape and reduce reliance on informal, personality-based processes by enabling users to build workflows directly through Microsoft Teams. Rather than navigating layers of coordination or disconnected systems, using Flow, our teams could turn recurring needs into transparent, repeatable processes where the work already occurs. For smaller ServiceNow organizations, Flow offers a practical way to gain more value from the platform without the extensive resources of larger enterprises—especially in environments where systems and services are often siloed.”

Jeffery Compoc, Deputy N6, Fleet Numerical Meteorology and Oceanography Center (FNMOC), U.S. Navy

Flow can handle more complex automations

Not every request stays in one place. Onboarding a new employee reaches into identity, messaging, and business tools, and each step depends on the one before it.

A multi-system automation does that handoff: the output of one system becomes the input to the next. Create an account in one system, then use it to set up access in another. You describe the whole sequence in plain language, including the approvals, and Flow drafts it for your team to review, test, and publish. Here is a prompt for the employee onboarding example discussed above:

“Create an automation for new-hire onboarding that takes only the new hire’s work email. Using the employee information already available in Flow, create accounts for them in Google Workspace, Okta, and Zoom. When all three accounts are ready, notify the employee and the person who started the automation with a summary of the accounts created.”

Flow is designed to finish the job, not only route it, and every conversation still lands in a record that IT can use for audit and reporting.

Connections are what let Flow act

Automation can only act where it can reach. Flow connects to identity providers like Okta, Microsoft Entra ID, and Google Workspace, and to more than 100 IT and business applications across ITSM, knowledge, and incident management. Those connections are what turn a plain language rule into an action in the systems employees already use. They are also what let one automation work across several systems.

Admins stay in control: they choose which team can use each connection and which actions are allowed. No need to replace your tools. Connect Flow to your existing applications and start resolving. What you do need is admin access to connect those systems. Loop in the admins early so setup doesn’t stall.

 

How easy is it to get started?

Getting a first automation live takes five steps:

1. Point Flow at your identity provider and invite your team.
2. Add Flow to Slack or Microsoft Teams.
3. Connect the systems your team already uses, including knowledge sources and ticketing.
4. Describe the automation in plain language. Flow builds it.
5. Test it, get it approved, and publish it. Once published, the automation can start from a chat message, a schedule, a webhook, an API call, or an event in a connected system.
   
   

No developer, code, or long project is required. Pick the request your team answers most often and can describe in a sentence. That could be your first automation.

For product updates and direct access to the team building Flow, visit the Flow Community.

FAQ

Can an automation start without someone typing in chat?

Yes. A chat message is one trigger. Published automations can also start from a schedule, a webhook, an API call, or an event in a connected system.

Is an automation checked before it runs?

Yes. Flow runs automations after testing and approval. Every action a model proposes is checked against scope, approvals, and kill switches before it runs.

Do I need a developer to build an automation?

No. You describe what you want in plain language, and Flow builds it. There is no need for a developer, code, or a long project.

Which systems can Flow automate?

Flow supports over 100 integrations, including Okta, Zoom, Office365, Notion, and Workday. It connects to identity providers like Okta, Microsoft Entra ID, and Google Workspace, and it works with the systems your team already uses.

Can Flow work across multiple systems in a single automation?

Yes. Describe the steps, the systems involved, and any approvals in plain language, and Flow drafts the automation for you to review, test, and publish. Automations call each connected system through connector actions, and admins choose which teams can use each connection and which actions are allowed. It isn’t active for your team until you publish it.