AI Indexes
GTM AI Index
Index › Products › Salesforce Flow · October 2026 Edition
Salesforce · 2 categories · Named, not ranked

Salesforce Flow

10Judge labels
0First choices
3Negative labels
9 / 14Models named it
2Categories
October 2026 Edition. Every number here is derived from the raw labels under vendor table v2026-10-05.2, every buyer segment counted.
Standing
3 labels, too few to rank
A product needs 10 labels in a category before a share or quadrant is stated. Salesforce Flow was named 3 times in Lead routing and 1 other category, where LeadAngel led with 26%. The labels and the evidence are below, counted exactly.
By buyer segmentRead the same way at every buyer size.
In lead routing · each standing computed within its segment · bars are 0 to 100 · the accent bar is the product's own best reading

Standing by category

Every category where a model named Salesforce Flow for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.
CategoryFunctionShareRankNegative rateLabelsQuadrantSince September 2026
Lead routing and managementSales0%91 of 11150%2under 10 labels · led by LeadAngel at 26%newNew since September 2026: not ranked then, 0% now.
Workflow automation and iPaaSGTM data and infrastructure0%48 of 670%1under 10 labels · led by Workato at 28%=heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked.

Movement

Since September 2026, Salesforce Flow held within the floor in all two categories: no change cleared 11 points.

Best category · Lead routing · by segment

Small businessnewNew since September 2026: not ranked then, 0% now.
0%from 0% in September 2026
Inside the floor by 11 pointsRank 44 of 103, unchanged
Mid-marketnewNew since September 2026: not ranked then, 0% now.
0%from 0% in September 2026
Inside the floor by 11 pointsRank 82 of 103, unchanged
Enterprise=heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked.
0%from 0% in September 2026
Inside the floor by 11 pointsRank 76 → 51 of 80

All categories · Mid-market

CategorySeptember 2026NowChangeReadingRank
Lead routing0%0%newNew since September 2026: not ranked then, 0% now.New this editionRank 91 of 111, unchanged
Automation & iPaaS0%0%=heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked.Within noiseRank 50 → 48 of 67

Shares here are read over the models both editions asked, so they can differ by a point or two from the standing above, which counts every model in this edition.

The floor is 11 points of share, measured: how far the models move a leader on their own when the same questions are asked twice with nothing changed. A larger change is movement; a smaller one is noise, and both are shown. Movement is read over the twelve models both editions asked; GPT-6 Luna, Muse Glimmer 30B joined this edition and are in the standing but not yet in the comparison. How the floor is measured · The editions

By model

How each model treated Salesforce Flow across every prompt where it was named for a mid-market B2B company. Fourteen models, six prompts per category.
ShowHide
ModelFirst choiceAlternativeMentionNegativeLabels
Claude Haiku 4.500101
GPT-5.4 mini00000
Gemini 3.5 Flash00000
Perplexity Sonar00000
Grok 4.2000000
Mistral Small00101
DeepSeek V4 Flash00000
Llama 4 Maverick00000
Qwen 3.7 Flash00011
Kimi K200000
GLM 4.7 FlashX00000
MiniMax M2.500000
GPT-6 Luna00000
Muse Glimmer 30B00000

By framing

Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.
FramingLabels by classFirst choices
Direct2 labelsNone
Paraphrase0 labelsNone
Comparative1 labelNone
Budget-constrained3 labelsNone
Scale-constrained1 labelNone
Negative3 labels1not counted in share
First choiceAlternativeMentionNegative10 labels in all, every segment counted; 0 of the 1 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.

What the models said for it

Verbatim evidence the judge attached to positive labels.

No positive label carried a quote.

And against it

Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.

“native tools often hit a ceiling and require "spaghetti" coding to maintain” Qwen 3.7 Flash · Lead routing · direct prompt · soft negative

Named alongside

The products named in the same answers as Salesforce Flow, over the 10 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and Salesforce Flow was named but was not.
ShowHide
ProductSame answerTook the first choice insteadHead to head
LeanData4 of 101Not among the top eight
Chili Piper4 of 100Not among the top eight
Zoho CRM3 of 102Not among the top eight
HubSpot Workflows3 of 101Not among the top eight
HubSpot Sales Hub3 of 100Not among the top eight
UiPath3 of 100Not among the top eight
Appian2 of 100Not among the top eight
Automation Anywhere2 of 100Not among the top eight
Blue Prism2 of 100Not among the top eight
Make2 of 100Not among the top eight
A head-to-head page exists where both products are among a category's top eight. The other rows are the same fact without a page behind them, so they link to the product instead.

What carried it into the answer

The sites and pages cited by the answers that named Salesforce Flow. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 8 of the 10 answers that named Salesforce Flow and are not a share of its labels.

Domains cited

articsledge.com3
guideflow.com3
prospeo.io3
avoma.com2
capterra.com2
default.com2
docket.io2
g2.com2
getbreakout.ai2
gitnux.org2

Twenty-three of the twenty-three domain citations in answers naming Salesforce Flow came from somebody else's page.

Pages cited

Pages are listed as the models cited them.

Names read as Salesforce Flow

What the judge wrote, as written, with how often. The vendor table decides that these count as Salesforce Flow; a claim can dispute any of them.
HubSpot Workflows / Salesforce Flows 1

Follow Salesforce Flow

An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.

Already following? Everything you follow, with a stop for each.

The company

Salesforce is the company behind Salesforce Flow.
ShowHide

On record

Wikidata
Headquarters
San Francisco, United States
Founded
1999
Employees
about 35,000 (2019)
Ownership
Public, CRM on New York Stock Exchange

Fetched September 14, 2026. These describe the company, not the product's standing, and a claimed page can dispute any of them. · Wikidata · LinkedIn · Crunchbase

In its own words

Stated by the vendor, not checked
Positioning
Generate Salesforce Flows using the MCP tool execute_metadata_action.
Customers named
r.Potential
Not stated on the pages read
Price, starting price, free plan or trial, integrations, certifications, hosting

What Salesforce Flow's own pages state, read October 5, 2026: appexchange.salesforce.com/appxStore, engineering.salesforce.com/flow-scheduling-for-the-einstein-ml-platform-b11ec4f74f97, appexchange.salesforce.com/appxListingDetail, salesforce.com/platform/integration-automation, salesforce.com/service/digital-process-automation. A claimed page can correct any of them.

Is this your product?

Claim this page

Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Salesforce Flow's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Salesforce Flow, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.

What a new claim receivesHide what a new claim receives

A new claim receives the current edition's vendor brief for Salesforce Flow by email, built from the raw record of the edition. It shows:

  • where Salesforce Flow is named, by buyer and by framing, and which cells hold its first choices;
  • the claims the models make when they name it, ranked, with the strongest and the weakest quoted;
  • its vocabulary against the segment leader's, and the pages the models cited;
  • who was chosen in the answers that did not name Salesforce Flow, and every reason the record gives;
  • a battlecard for each top rival: the head-to-head split, why they win, and the reservation quoted against them;
  • one page of published figures cleared to show a buyer.
The subscriber app

A verification link goes to your work email; an address at salesforce.com is approved on the spot, any other is reviewed by hand. Your email is never published. Claiming gives no say over labels, shares, verdicts or which quotes appear.