rss.livelink.posts-in-node

Test questions

IgorL — Wed, 30 Sep 2026 17:57:12 GMT

Please help

Re: Creating an O-Auth connection to integrate ServiceNow to Flow

IgorL — Wed, 30 Sep 2026 15:33:57 GMT

dadasd

Flow test question

IgorL — Wed, 30 Sep 2026 13:42:34 GMT

Testing

Flow Forum Board Test

gabrielmusa — Tue, 29 Sep 2026 21:43:23 GMT

Flow Forum Board Test

Re: This is a Test Event for CSM

CaroS — Tue, 29 Sep 2026 18:04:38 GMT

Good insight

Testing BP

IgorL — Tue, 29 Sep 2026 16:38:42 GMT

Testing

Re: Introducing Flow by ServiceNow

ServiceNow1 — Tue, 29 Sep 2026 12:17:53 GMT

first

Introducing Flow by ServiceNow

gabrielmusa — Mon, 28 Sep 2026 18:13:54 GMT

I'm excited to introduce Flow, a refreshed take on a conversational, AI-native service desk. You can read my product manifesto here.

Every help desk team we talk to tells some version of the same story. Employees expect instant answers right where they already work; and lately that's a chat tool like Teams or Slack, or the AI agent of their choice. The teams supporting them are buried. Heads down, queue full, no time to get out ahead of the next wave of the exact same requests.

It's the same story at both ends of the market. It's true for the 200-person company running IT out of Slack DMs, email and a spreadsheet. It’s also true for the 10,000-person enterprise where one satellite department needs basic support, can't wait three months for an implementation on the main platform, and wants full control of its own system. We built Flow for both.

What Flow is

Flow is a conversational AI service desk that gives any team a working help desk in a day.

Employees get help through natural conversation in Slack, Teams or email. No forms. No portal to bookmark. No tickets to file. Flow resolves requests in the flow of work, using the knowledge you already have, wherever it lives, with nothing to migrate.

And when the same request keeps coming back, the system surfaces those insights, and your team builds an automation in plain English to stop it from ever reaching the queue again. Describe the fix the way you'd explain it to a new hire; Flow drafts the steps, wires up the connector actions, and flags what's missing instead of guessing. Then test the whole thing in simulation before it touches a real system. No code. No sprint. No platform team standing between your people and their own ideas. Admins set the guardrails up front: what each team can touch or read, what needs a human sign-off, and every run is logged.

Connect your identity provider, your chat tool, and your existing knowledge and asset sources and tools you want to automate, and you're live in four steps. Flow already speaks to 100+ apps out of the box, and each connection stays safely scoped to the team that needs it. No CMDB. No middleware. No need for ITIL alignment.

For the requests that do need a person, Flow hands off with full context. Your team replies directly inline, in the same thread the employee started in, right from the Flow app. Email in the morning, a Slack follow-up that afternoon: one conversation, not two tickets to reconcile. And Flow watches for patterns along the way, surfacing the next thing worth documenting or automating, so your team gets more proactive over time instead of more buried.

And yes: it's built completely off the ServiceNow platform. As someone who's spent the last twelve years here building ITSM and ITOM products on the platform, I'm the first to appreciate how sacrilegious a statement that is. We did it anyway. Not to walk away from what ServiceNow is: the depth, the governance, the twenty years of knowing how real enterprises actually run, but because the lower maturity and simplicity needed by these satellite service desks is more lightweight, and not everyone needs a Lamborghini if all they are doing is driving to the grocery store.

Where we chose to start

We wanted to start somewhere real, where teams already work this way today. The service desk was the obvious place. It's where the repetitive, answerable, automatable work lives. It's where a conversational AI can prove its efficiency on day one.

I've now watched it work in real teams with a dozen early access customers, and here's what excites me, especially after twelve years of doing this the old way:

Conversations, not tickets: People resolve work by talking, not by filing. The tax is gone, and adoption and speed follow.
Multiplayer support, in the channel: Flow shows up in the threads where the work already is, and answers everyone in them; even when three people are talking over each other, the way real teams do.
Safe automation in plain English: Your team describes the fix; Flow builds it. You decide who can automate what, and you keep a human on anything that matters. Power, without a queue for the power.
Agents for everyone: Not one bot for employees, but AI that helps the person asking and the person resolving, with full MCP support to reach into the rest of your stack, and to let the rest of your stack reach into Flow.

That last point is key: once the interface is a conversation and the actor can be an agent, the thing on the other end of the request no longer must be a human either.

Who it's for

Making the world of work, work for everyone is not a story reserved for the largest enterprises anymore. I want to democratize ServiceNow’s expertise built on thousands of customers.

If you're new to ServiceNow, Flow is a standalone product. No CMDB. No ITIL. No knowledge migration. No multi-month partner rollout. If you've been running a help desk out of Slack DMs, email and a spreadsheet, this is the part that matters: Flow gives you structure and automation without the overhead that made enterprise ITSM feel like it was never built for you. Try it free for 30 days. Stand it up for your team in a day, and start resolving real requests before lunch.

If you're already on ServiceNow, Flow isn't here to replace the platform or change how your employees meet the core business. Keep EmployeeWorks as your front door across chat, and Build Agent for conversational development. Bring Flow in if you want to launch a service desk for a satellite team, and let business teams automate in natural language without waiting on scarce skills or admin time. Satellite teams sync bidirectionally with your existing ServiceNow instance and draw on your knowledge and CMDB context for sharper answers. Automations you build in Flow surface in EmployeeWorks over MCP. And Flow runs on the NowAssist credits you've already bought - no new SKU, no new procurement cycle. It activates what you already own.

This is for the Fortune 500. And the Fortune 500,000.

We're starting with the service desk, and we have no intention of stopping there.

Come check us out at letsflow.ai

-Darius, Head of Product, Flow by ServiceNow

Getting Started

gabrielmusa — Mon, 28 Sep 2026 18:12:41 GMT

Hi Flow community,

This blog post contains resources to help you quickly get up to speed with Flow. We'll keep it updated as new items are introduced. Attached, below, you can find the Getting Started Guide.

Flow documentation

gabrielmusa — Mon, 28 Sep 2026 18:12:03 GMT

Hi Flow Community

Attached below, you'll find a link to the Flow documentation. We'll update it here as the product expands and the documentation changes.

Creating an O-Auth connection to integrate ServiceNow to Flow

gabrielmusa — Mon, 28 Sep 2026 18:06:13 GMT

To safely connect your ServiceNow instance (if available), you will need to Create an OAuth key for authentication. If you haven't created one yet, this is the quickest way to do so. Please note - it might also be worth checking if there is another OAuth key used in prod that can be used since it overwrites.

First confirm that you have a system property (glide.oauth.inbound.client.credential.grant_type.enabled) that enables client credential grant type. I assume this should be there already, but let me know either way if that’s not the case. If it is indeed missing just create a new one.

Create an integration user to use for the client credential token. We recommend something like flow.ai.integration. You will need to grant this user itil and snc_platform_rest_api_access roles to that user so it can read CMDB, Knowledge, and write incident/requests bidirectionally for ticket synch.

Navigate to System OAuth > Inbound Integrations. Create a New Integration.

Create the token. You can just fill in provider name as a free form text field. Select the OAuth user you created in the previous step. Name auth scope is set to useraccount. See below screenshot.

With this OAuth credential setup, you can then enter it into your Flow integration connector for ServiceNow to begin loading assets, knowledge, and synching tickets bidirectionally!

test post with image

admin — Sat, 26 Sep 2026 09:15:10 GMT

test post with image

Re: TEST 0309261004

01martech0t — Mon, 21 Sep 2026 15:18:26 GMT

Nice

Re: [ABUSE] By: Igor3 / Board: autonomous-it-forum (4)

ServiceNow1 — Fri, 04 Sep 2026 16:45:47 GMT

Re: TEST 0309261004

Igor3 — Thu, 03 Sep 2026 13:08:57 GMT

2nd reply

Re: TEST 0309261004

Igor3 — Thu, 03 Sep 2026 13:19:35 GMT

1st reply
[edited]

TEST 0309261004

Igor3 — Thu, 03 Sep 2026 13:06:01 GMT

Test message

Re: test111

Igor3 — Thu, 03 Sep 2026 13:02:10 GMT

test

[ABUSE] By: Igor3 / Board: autonomous-it-forum (4)

Igor3 — Thu, 03 Sep 2026 12:33:27 GMT

Report Type: Something Else | Content Category: Other | Description: test | Reported by: Igor3 (https://www.webstg.servicenow.com/community/user/viewprofilepage/user-id/1933)

Link to post: (Re: test111)
by Igor3

https://www.webstg.servicenow.com/community/autonomous-it-forum/test111/m-p/63982#M4

test

This message has 0 replies

Re: test111

Igor3 — Thu, 03 Sep 2026 12:30:53 GMT

test