Flow by ServiceNow and Flow Designer are separate ServiceNow products that share a word. Flow Designer is the low-code workflow builder inside a ServiceNow instance, now part of Workflow Studio. Flow by ServiceNow is a standalone conversational AI service desk for Slack, Microsoft Teams, and email that ServiceNow launched on 1 October 2026, with its own plain-language automation builder and no ServiceNow instance required.
Flow by ServiceNow vs Flow Designer at a glance.
Flow by ServiceNow and Flow Designer differ on every point a buyer compares first: where each runs, who uses it, and how automation gets built.
| Flow by ServiceNow | Flow Designer | |
|---|---|---|
| What it is | A standalone conversational AI service desk. | The low-code workflow builder inside a ServiceNow instance. |
| Where it runs | On its own multi-tenant cloud architecture, built off the ServiceNow platform. | Inside a ServiceNow instance, as part of Workflow Studio. |
| Needs a ServiceNow instance | No. | Yes. |
| Where people use it | Employees ask in Slack, Microsoft Teams, and email. Agents work from one queue. | Platform teams build flows inside the instance. |
| How automation gets built | A team member describes the fix in plain language, and Flow drafts the steps. | Builders assemble triggers, actions, flow logic, and subflows on a low-code canvas. |
| Who can build | Anyone on the team, with no developer or admin required, inside admin guardrails. | Platform teams on ServiceNow. |
| Status | Launched 1 October 2026, in controlled availability. | The default ServiceNow process automation builder, replacing the legacy Workflow Editor. |
| How they connect | An optional connection to a ServiceNow instance syncs tickets, assets, knowledge, and Assists. | Lives in that instance. ServiceNow documents no link between Flow automations and Flow Designer flows. |
Is Flow by ServiceNow the same as Flow Designer?
Flow by ServiceNow and Flow Designer are two different products. ServiceNow posted an orientation note on launch day to separate them: building automation inside a ServiceNow instance is Flow Designer, and talking to an AI assistant in Slack, Teams, or email is Flow by ServiceNow.
Where each one runs.
Flow Designer runs inside a ServiceNow instance and is now part of Workflow Studio. Flow by ServiceNow is built completely off the ServiceNow platform, in the words of its head of product. Flow runs on its own multi-tenant cloud architecture and needs no ServiceNow instance.
How each one builds automation.
ServiceNow Flow Designer is the default ServiceNow process automation builder, where platform teams build triggers, actions, flow logic, and subflows. Building an automation in Flow Designer means choosing a trigger, mapping fields, running tests, and publishing.
Flow by ServiceNow takes a different route. A team member describes the fix in plain language, and Flow drafts the steps, wires up the connector actions, and flags anything missing. Builders review each step, adjust it, and test it in simulation or subprod before publishing.
Who each one is for.
Flow Designer serves platform teams who build and maintain workflows on a ServiceNow instance. Flow by ServiceNow serves service desk teams, including teams with no ServiceNow instance at all. ServiceNow says no developer or admin is required to build a Flow automation, so a service desk lead with no builder experience can describe a process and get a working automation.
Where the two connect.
Flow by ServiceNow connects to the ServiceNow platform only when an existing customer links Flow to an instance. The optional connection syncs tickets, assets, knowledge, and Assists in both directions, through an OAuth integration user that reads CMDB and knowledge records and writes incidents and requests. Satellite teams on a connected instance can draw on CMDB context for better answers.
Flow Designer vs the legacy Workflow Editor.
Flow Designer replaces the legacy Workflow Editor. Flow Designer flows are built from reusable components and need far less scripting than Workflow Editor workflows. As of the Zurich release, new customers no longer receive the legacy workflows ServiceNow ships, and only Workflow Studio receives new features.
What is Flow by ServiceNow?
IT requests often arrive through three channels and get tracked consistently in none of them. One employee posts in the help channel asking why the VPN will not connect. Another emails about a license needed by Thursday. A third files a ticket, then sends a direct message asking whether anyone saw the ticket. The people answering spend more time switching between channels than resolving requests.
Flow by ServiceNow is a standalone conversational AI service desk built for that fragmentation. Flow works inside Slack, Microsoft Teams, and email, where requests already arrive, and resolves each request in the same thread. Employees ask in the tool they already use, so there is no portal to roll out and no form to fill in. Fast Company reports that a small team built Flow in three months, and ServiceNow describes it as a startup within ServiceNow.
| Attribute | Flow by ServiceNow |
|---|---|
| Launch and availability | Launched 1 October 2026. Controlled availability, with access by request. General availability in North America and EMEA expected in Q4 2026. |
| Prerequisites | No ServiceNow instance, CMDB, or ITIL alignment. |
| Time to deploy | Live in less than a day, according to ServiceNow. |
| Pricing | New customers: $2 per conversation and $1 per automation run, with a $10K annual minimum. Existing ServiceNow customers: 10 Assists per conversation and 5 Assists per automation run. |
| Integrations | 100+ prebuilt integrations across identity, knowledge, asset, and ticketing systems, plus the apps Flow acts on. |
| Relationship to ServiceNow ITSM | A separate product. Existing customers can run both, and change management, problem management, and CMDB-driven processes stay on ITSM. |
Flow skips the groundwork a ServiceNow ITSM rollout usually involves. Flow's head of product lists no CMDB, no middleware, no ITIL alignment, and no knowledge migration, and the Flow product manifesto adds no sub-production instance.
ServiceNow says Flow goes live in less than a day, and the Flow product site promises one admin, one day, no code. Setup takes longer when the person doing it is not the admin of the systems being connected. Setup runs in four steps: invite the team or connect company sign-on, add Flow to Slack or Teams, connect the apps that hold knowledge, assets, and tickets along with the apps Flow should automate, then start resolving requests.
Flow is in controlled availability, with access by request at letsflow.ai and priority for North America. ServiceNow's launch announcement expects general availability in North America and EMEA in Q4 2026, and a company representative told CIO.com that wider availability follows in Q1 2027.
ServiceNow's launch announcement quotes four organizations: CFO Advisors, the U.S. Navy's Fleet Numerical Meteorology and Oceanography Center, Serenity EHS, and VividCharts. ServiceNow expects Flow to cut ticket volume by 40% and let teams build an automation in five minutes, and has described both figures as expectations during controlled availability.
What Flow does.
Flow by ServiceNow combines six capabilities:
- Answer: Resolves questions in the thread from the knowledge base you already have, with nothing to migrate.
- Fulfill: Runs automations across 100+ prebuilt integrations once an app is connected and the automation is built.
- Hand off: Passes complex or sensitive issues to a person with full context.
- Unify: Keeps every request in one agent queue, whichever channel it came through.
- Build: Drafts a Flow automation from a plain-language description, ready for review and testing.
- Analyze: Tracks request volume and resolution time, and flags repeat requests as automation and knowledge candidates.
Answers from the knowledge base you already have.
Many inbound service desk messages are questions with documented answers, such as how to connect to the fourth-floor printer or where the VPN configuration guide lives. Flow reads each question, pulls the answer from your existing knowledge base, and replies in the thread. The knowledge base stays where it is, with nothing to migrate.
Answer quality tracks article accuracy, which is why knowledge cleanup belongs in any AI readiness plan, whether the answers come from Flow or from ServiceNow's platform AI.
Fulfillment across 100+ prebuilt integrations.
Flow connects to identity, knowledge, asset, and ticketing systems, plus the apps the team wants Flow to act on, through 100+ prebuilt integrations. Each connection is scoped to the team that needs it. Once an app is connected and the team has built the automation, a request for access to that app ends with access granted. Requests without an automation get an answer from knowledge or go to a person.
Handoff to a person, with full context.
Flow hands complex or sensitive issues to a person with full context, and the agent replies inline in the same thread. The requester does not have to repeat anything. Handoff quality decides whether employees keep using a chat assistant or learn to route around it.
One queue for the service desk team.
Requests and incidents from every channel land in a single queue. Agents reply from Flow, and Flow posts the reply in the channel they choose. An email in the morning and a Slack follow-up in the afternoon stay one conversation. Flow also answers everyone in a multi-person thread.
How Flow automations start and run.
Flow by ServiceNow builds automations from plain-language descriptions, as covered in the comparison with Flow Designer above. After resolving a request, an agent can turn the fix into an automation with one click or a slash command. Published automations can start from a chat message, a schedule, a webhook, an API call, or an event in a connected system, and every run is logged.
Other bots and AI assistants can reach Flow over APIs or MCP, and Flow can reach the rest of the stack the same way. Automations built in Flow also surface in ServiceNow EmployeeWorks over MCP.
Repeat requests flagged for automation.
Flow's analytics track request volume, the share of requests resolved without a person, resolution time, and repeat requests. Flow flags repeat requests as automation and knowledge candidates, such as twelve employees in a month asking for the same tool. Someone on the team then describes the fix, and Flow builds the automation.
Service desks can adopt these capabilities one at a time and expand as request data shows where the team's hours go.
What Flow by ServiceNow costs.
Flow by ServiceNow pricing is published, with one model for new customers and one for existing ServiceNow customers. ServiceNow's pricing page lists a 30-day free trial with no credit card required. ServiceNow's launch announcement says sign-ups during controlled availability get early access to a free trial, and CIO.com reports no charge during controlled availability.
| New customers | Existing ServiceNow customers | |
|---|---|---|
| Per conversation | $2 | 10 Assists |
| Per automation run | $1 | 5 Assists |
| Commitment | $10K annual minimum commit that auto-renews, with $1K top-ups. | Drawn from Assists the customer already owns or buys from its account team or partner. |
| How to buy | In product by credit card, or through sales. | No new SKU and no new procurement cycle. |
A conversation is one issue, charged once whether AI or a person handles it. Automations that run inside a conversation are free. The automation charge applies when an automation is triggered outside an employee conversation, such as through MCP, an API, or another agent.
ServiceNow's launch announcement says existing customers qualify on any ServiceNow pricing plan that includes AI capabilities. ServiceNow's pricing page describes Assists as the ServiceNow AI usage credits customers already own.
Who Flow is built for.
Flow by ServiceNow fits teams that field a high volume of repetitive requests and cannot staff a platform implementation. ServiceNow starts Flow with the IT service desk and plans to expand it to other teams. Five profiles fit best.
Small and mid-sized companies with fragmented support.
Small and mid-sized companies often run IT support across chat, email, and spreadsheets with no system tying them together. ServiceNow's own example is a 200-person company running IT out of Slack DMs, email, and a spreadsheet. Flow consolidates that intake without a migration, because it picks up requests where they already arrive.
First-time ITSM buyers.
First-time ITSM buyers have outgrown informal support but are not ready to commit to a full platform implementation. Their choice used to be staying chaotic or signing up for a project that consumes a quarter. Flow skips the CMDB and ITIL groundwork, so teams start with working automation and build process maturity afterward.
Existing ServiceNow customers with Assists.
Existing ServiceNow customers can run Flow on Assists they already own or purchase from their account team or partner, with no new SKU and no new procurement cycle. ServiceNow's guidance is to keep EmployeeWorks as the front door across chat and Build Agent for conversational development, and to bring Flow in for a satellite team's service desk. Fast Company reports that ServiceNow's president said EmployeeWorks and Otto continue to serve larger enterprises.
Satellite IT teams inside large enterprises.
Large enterprises rarely run a single IT function. Remote teams and newly acquired business units carry their own support load, often with no path to their own instance. ServiceNow positions Flow for teams that cannot wait three months for an implementation on the main platform. Connecting Flow to the central instance gives those teams CMDB context for better answers.
HR and Legal teams.
HR and Legal teams handle the same kind of work as an IT service desk: repeated questions answered from documentation, and requests routed to the right owner. ServiceNow's product site lists IT, HR, Legal, and any team that fields requests as Flow's audience. The launch announcement says Flow begins in ITSM and expands across every team, and ServiceNow's published materials describe no HR-specific or Legal-specific features. Because Flow operates in chat, extending it beyond IT needs no new departmental portal.
The requests Flow resolves.
ServiceNow's own examples of Flow requests are password resets, access requests, policy questions, and infrastructure provisioning, with employee onboarding named on the Flow product site.
| Request type | Examples | How Flow handles it |
|---|---|---|
| Password resets and software access | A locked-out account, a seat in a SaaS app, read access to a reporting dashboard. | Once an admin has built the automation, runs it against the connected identity or SaaS system, inside admin-set limits. |
| Employee onboarding | Accounts, licenses, group memberships, and hardware before the start date. | Runs the onboarding automation across connected systems, once the team has built it. |
| Policy and how-to questions | Reimbursement limits, time-off requests, which VPN profile to use overseas. | Answers in the thread from the knowledge base. |
| Provisioning | Environments, licenses, shared resources, and group access tied to a role change. | Routes any sign-off an admin requires, then runs the automation. |
Each of these requests follows a predictable pattern, which makes it a strong fit for automation.
Employee onboarding is a coordination problem more than a technical one: many small steps across many systems, each with a different owner. Built as a Flow automation, onboarding runs the same way every time instead of depending on whoever remembers the runbook.
How Flow changes who builds automation.
ServiceNow automation has historically been gated behind specialists who know the platform's object model and scripting conventions. Every automation request funneled into one queue. The backlog grew, and the business built workarounds that left technical debt behind.
Service desk leads can build automation.
Flow by ServiceNow moves automation building from platform specialists to the people who run the service desk. The expertise that matters shifts from platform syntax to process knowledge, which service desk teams already have. For a three-person IT team, automating password resets and access requests recovers the task time and the interruptions around it.
Admins keep control of what gets built.
Flow admins decide what each team can touch or read and what needs a human sign-off, and every run is logged. Each connection is scoped to the team that needs it, and end users build inside those limits. Low-code automation without that control produces hundreds of orphaned flows that nobody can audit.
One question is still open. Fast Company reports that ServiceNow's president did not specify how Flow reverses or contains a harmful automated action once it has run. Flow's repeat-request flags also tie the automation roadmap to request data instead of whoever argues loudest in planning meetings.
Where Flow by ServiceNow fits next to ServiceNow ITSM.
Flow by ServiceNow is a separate product from ServiceNow ITSM. ServiceNow says customers who need change management, problem management, or a CMDB-driven process stay on ITSM, and existing customers can run both.
| Flow by ServiceNow | ServiceNow ITSM | |
|---|---|---|
| Setup | Live in less than a day, according to ServiceNow. | ServiceNow contrasts Flow with a multi-month partner rollout on the main platform. |
| Prerequisites | No ServiceNow instance, CMDB, or ITIL alignment. | Runs on a ServiceNow instance. |
| Processes | Service desk requests, knowledge answers, and automations. | Adds change management, problem management, and CMDB-driven processes. |
| Who builds automation | Anyone on the team, in plain language, inside admin guardrails. | Platform teams in Flow Designer or with Build Agent. |
Teams can start in Flow and build process maturity from there. Teams weighing the two options can run a structured AI proof of concept against their highest-volume request types before committing to either. Teams building on the ServiceNow platform itself can compare Build Agent and Now Assist for Creator in our guide to AI tools for ServiceNow delivery.
Frequently asked questions.
What is the difference between Flow by ServiceNow and Flow Designer?
Flow by ServiceNow and Flow Designer are separate products. Flow Designer is the low-code workflow builder inside a ServiceNow instance, now part of Workflow Studio. Flow by ServiceNow is a standalone AI service desk for Slack, Microsoft Teams, and email, built off the ServiceNow platform, with its own plain-language automation builder.
What is Flow by ServiceNow?
Flow by ServiceNow is a standalone conversational AI service desk that resolves employee requests in Slack, Microsoft Teams, and email. ServiceNow launched Flow on 1 October 2026 as a separate product with its own architecture and its own plain-language automation builder. Flow needs no ServiceNow instance, CMDB, or ITIL alignment, and is in controlled availability.
What is the difference between Flow Designer and Workflow in ServiceNow?
Flow Designer is the default ServiceNow process automation builder, replaces the legacy Workflow Editor, and is now part of Workflow Studio. Flow Designer flows are built from reusable components and need far less scripting. As of the Zurich release, new customers no longer receive ServiceNow's legacy workflows, and only Workflow Studio receives new features.
How much does Flow by ServiceNow cost?
Flow by ServiceNow costs new customers $2 per conversation and $1 per automation run, with a $10K annual minimum commit. Existing ServiceNow customers pay 10 Assists per conversation and 5 Assists per automation run, from Assists they already own or purchase from their account team or partner. ServiceNow lists a 30-day free trial, and automations that run inside a conversation are free.
Does Flow by ServiceNow need a ServiceNow instance or a CMDB?
Flow by ServiceNow runs without a ServiceNow instance, a CMDB, or ITIL alignment. Existing ServiceNow customers can choose to connect Flow to an instance, and that connection syncs tickets, assets, knowledge, and Assists in both directions.
Does Flow by ServiceNow replace ServiceNow ITSM?
Flow by ServiceNow is a separate product from ServiceNow ITSM. ServiceNow says customers who need change management, problem management, or a CMDB-driven process stay on ITSM, and existing customers can run Flow and ITSM side by side.
Is Flow by ServiceNow available now?
Flow by ServiceNow is in controlled availability after its 1 October 2026 launch, with access by request at letsflow.ai and priority for North America. General availability in North America and EMEA is expected in Q4 2026, and a company representative told CIO.com that wider availability follows in Q1 2027.
Key takeaways.
- Flow by ServiceNow and Flow Designer are separate products: Flow Designer builds workflows inside a ServiceNow instance, and Flow has its own plain-language automation builder that needs no ServiceNow instance.
- Flow by ServiceNow is a standalone AI service desk for Slack, Microsoft Teams, and email, launched 1 October 2026 and in controlled availability.
- New customers pay $2 per conversation and $1 per automation run with a $10K annual minimum, and existing ServiceNow customers spend Assists.
- Flow is separate from ServiceNow ITSM, which stays the home for change management, problem management, and CMDB-driven processes.
Echelon builds AI delivery for ServiceNow. We help teams build and govern ServiceNow automation, from Flow Designer flows to full ITSM implementations. To see how Echelon accelerates your ServiceNow delivery, book a demo with Echelon.
