Summer ’26 Flow Updates: Six Things That Will Actually Change How You Build Automations
Every Salesforce release, the Flow section of the release notes is the one worth reading first. Summer ’26 did not disappoint — new date operators, batch size control for scheduled flows, collapsible fault paths, natural language updates for Screen Flows via Agentforce, and a genuinely better radio button experience. Here is the full breakdown of what landed, what it does, and when you would actually use it. Feature What it does Who benefits most 📅 Date Field Operators New operators: Is Today, Is Tomorrow, Is On, Anniversary. Applies to Date fields only — not DateTime. Admins building renewal reminders, SLA tracking, birthday campaigns, or any time-sensitive record logic. Eliminates the need for formula field workarounds. ⚙️ Scheduled Flow Batch Size Custom batch size control instead of the fixed default of 200. Smaller batches = lower governor limit risk. Larger batches = faster processing. Any org running Scheduled Flows against unpredictable record volumes. High-value for flows with DML operations or external callouts. 🗂️ Collapsible Fault Paths Fault paths in Flow Builder can now be collapsed. Canvas continues the visual cleanup started in Spring ’26 with collapsible Decisions and Loops. Admins managing complex flows with shared error-handling subflows. Large production flows become significantly more readable. 🤖 Natural Language Screen Flow Updates Agentforce natural language editing now supports Screen Flows. Describe a change in plain language, Agentforce makes the adjustment. Early access — review required. Admins who want to trial Agentforce-assisted flow building. Works well for additive changes with clear descriptions. Complex logic still needs manual work. 🔘 Radio Button Group New compact visual component replacing standard radio buttons in Screen Flows. Horizontal and vertical layout options, less vertical space per option. Any admin who has built Screen Flow intake forms and found standard radio buttons too space-heavy. Direct UI improvement for end users. 📧 Email Template Deployment Fix Send Email Actions using Email Templates now deploy correctly between environments. Fix is in “Show advanced options” in the action properties. Orgs with proper sandbox-to-production workflows who have been maintaining environment-specific flow versions as a workaround. One-time fix. 1. New date field operators Flow now supports four new date operators: Is Today, Is Tomorrow, Is On, and anniversary-based matching for date fields. For any flow that does time-sensitive record logic, this is a meaningful improvement over the workarounds that previously required formula fields or date math. The practical applications are immediate. A renewal reminder flow that should trigger 30 days before the contract end date can now use Is On with a relative date formula rather than a calculated checkbox field. A birthday-triggered campaign can fire using the anniversary operator without building a custom evaluation layer. Any flow checking whether a date falls within a specific window benefits directly. One important constraint: these operators apply to Date data types only, not DateTime. If your date field includes a time component, the new operators will not be available. This is worth checking against your object schema before building. Summer ’26 — New Flow Date Operators Quick Reference Is Today Matches records where the date field equals the current date. Ideal for daily-run flows that flag due-today tasks, contracts expiring today, or time-sensitive SLA conditions. Is Tomorrow Matches records where the date field equals tomorrow’s date. Use for advance notification flows — renewal reminders, follow-up triggers, appointment confirmations the day before. Is On Matches records where the date field equals a specified date or relative date formula. Most flexible of the new operators — covers “is on the first of next month” and similar calculated dates. Anniversary Matches records where the month and day of the date field match the current month and day, regardless of year. Use for birthday campaigns, contract anniversary workflows, and renewal sequences tied to the same calendar date each year. ⚠ Important: these operators apply to Date fields only — not DateTime. Check your field type before building. 2. Batch size control for Scheduled Flows Scheduled Flows now support a custom batch size setting. The default has always been 200 records per batch, which is a sensible baseline for most use cases but creates problems when qualifying record counts are unpredictable and the flow logic includes DML operations, callouts, or other governor limit-sensitive steps. Smaller batch sizes reduce the risk of hitting limits when record volume spikes. A flow that runs cleanly on 200 records can fail when it processes 1,400 and the batch triggers 200 SOQL queries rather than 200. Reducing the batch to 50 adds processing time but removes the failure risk. The tradeoff runs in both directions. Larger batches complete the full scheduled run faster when record volume is stable and governor limits are not a concern. The new control lets admins tune this explicitly rather than accepting a single default for every scenario. 3. Collapsible Fault Paths Fault paths can now be collapsed in Flow Builder, following the Spring ’26 changes that added collapsible Decisions and Loops. This is a quality-of-life improvement rather than a capability change — fault paths do not behave differently when collapsed — but for anyone managing complex flows with shared error-handling subflows, the canvas clarity improvement is real. Large production flows become difficult to read when fault paths branch from every element that can fail and the canvas becomes a sprawl of error-handling logic. Collapsing fault paths lets admins focus on the main execution path during review and debugging, and expand fault handling when needed. 4. Update Screen Flows with natural language via Agentforce Agentforce-powered natural language editing, which launched for Record-Triggered and Scheduled Flows in Spring ’26, now extends to Screen Flows in Summer ’26. Admins can describe the change they want in plain language — ‘add a required email field before the address step’ — and Agentforce makes the adjustment in Flow Builder. This feature is in early access and the honest framing is the right one: it works well for additive changes that are clearly described. Reorganising a complex screen, adjusting conditional visibility rules, or changes that require
AgentExchange Salesforce: AppExchange Renamed
Salesforce has renamed things before. A lot. Data Cloud has had five names. Agentforce 360 had four. But AgentExchange, Salesforce’s most consequential rename yet is different. The AppExchange, launched in 2006, the marketplace that nearly 90 percent of Salesforce customers used to extend the platform, just became AgentExchange. Launched with a $50M Builders Fund and 13,000 apps, agents, and MCP servers under one roof. The community has thoughts. AppExchange to AgentExchange — Twenty Years 06 2006 AppExchange launches — first enterprise app marketplace Launch 12 2012 1,000 apps milestone 18 2018 AppExchange integrates Slack apps after acquisition 24 2024 Agentforce launches — first AI agent listings appear 26 2026 AgentExchange — unified catalog, AI search, $50M fund Now What actually changed The rename is not purely cosmetic. Three previously separate catalogs, the AppExchange, the Slack Marketplace, and the Agentforce ecosystem, are now unified into a single AI-searchable marketplace. That means 10,000 Salesforce apps, 2,600 Slack apps, and over 1,000 agents and MCP servers from partners including Google, DocuSign, and Notion now live in one place. Discovery works differently. Instead of keyword browsing through categories, users describe what they need and AgentExchange surfaces the right solution. One-click activation replaces the previous multi-step install process. For admins who have spent time navigating package installation wizards, that reduction in friction is material. The $50M Builders Fund is the other concrete change. It provides investment, engineering support, and go-to-market backing for ISVs and partners building in the new ecosystem, not a fund you apply to generically, but structured support tied to building agents and MCP integrations for AgentExchange distribution. The case for why it is more than a rebrand The community frustration with Salesforce naming is understandable and largely justified. When a product gets four names in three years, each rename starts looking like a marketing exercise rather than a product decision. This one is different for a specific reason: the marketplace structure changed, not just the name. AppExchange was an app catalog optimised for keyword search and category browsing. AgentExchange is designed from the ground up for AI-guided discovery. Those are different products with different underlying assumptions about how users find and evaluate solutions. Moreover, the consolidation of Salesforce apps, Slack apps, and AI agents into a single catalog reflects a genuine product reality: the Salesforce platform in 2026 includes all three, and separating them into different marketplaces created friction for customers who needed solutions that span all three surfaces. Putting them in one place with AI-guided discovery is a coherent response to how the platform actually works now. Partner data from the announcement makes the economic case more concrete. DocuSign processed over 200 private offers in Q4 2025 with 60 percent faster time to signature after listing on the unified marketplace. Notion cut its average sales cycle from four months to three weeks. These are not typical launch testimonials — they are specific metrics tied to the marketplace distribution model. What the community is actually saying The Reddit r/Salesforce thread opened with ‘Why?’ and the SF Ben community spent a productive afternoon debating whether CTO Nicolas Vuilamy was right that the company would eventually just rename itself Agentforce. One Salesforce coach wrote: ‘It is all a clear sign that the future is not human for Salesforce.’ The tone ranged from resigned to genuinely unsettled. The underlying concern is reasonable. When every product gets an ‘Agentforce’ prefix and every marketplace becomes an ‘Exchange’, it starts to feel like the platform is being rebuilt around a bet on AI that has not yet fully proven itself in the field. That is a fair read. The counter is also fair: the bets Salesforce made on CRM in 2006 and on the cloud in 2010 looked aggressive at the time and turned out to be correct. The question is whether the AI agent bet is in the same category. What this means by role 13,000+ Solutions total Salesforce apps, Slack apps, agents, and MCP servers unified in AgentExchange at launch $50M Builders Fund Investment, engineering support, and go-to-market backing for ISVs building agents and MCP servers 300% YoY growth Growth in Slack AI agent listings since January 2026 — the fastest-growing category in the marketplace Role What actually changed for you What to do now Admin Unified catalog means one place to find solutions across Salesforce, Slack, and Agentforce. AI-guided discovery replaces keyword browsing. One-click activation replaces multi-step install wizards. Explore Browse AgentExchange for solutions you previously searched AppExchange for — new categories and unified search may surface options you did not know existed. Developer 1,000+ agents and MCP servers are now listed alongside traditional apps. These are structured integration tools AI coding agents can call directly — a new category of extension beyond installed packages. Evaluate Review available MCP servers relevant to your integration stack. The agent/MCP category will expand rapidly; early familiarity pays off. ISV / Partner The $50M Builders Fund and AI-guided distribution represent a genuine go-to-market shift. Marketplace discoverability now depends on AI-optimised listing quality, not just keyword-based search ranking. Act now Review AgentExchange listing criteria. Evaluate what an agent or MCP server submission would require for your product. The window to list early in an AI-native marketplace is open now. Decision Maker The rename signals Salesforce’s long-term direction: agents as the primary unit of value. The practical marketplace capabilities are similar to AppExchange for current purchasing decisions. The strategic signal is clear. Watch Track which vendor partners are building agents and MCP integrations. The ecosystem is reshaping around agent-based extensions — understanding the map now informs technology roadmap decisions later. Building on Salesforce and thinking about what AgentExchange means for your product or integration strategy? Reach out at truesolv.com — we work with the Salesforce ecosystem daily. Follow us on LinkedIn for more Salesforce news with less jargon.
Salesforce Headless 360 and MCP
For most of Salesforce’s history, building on the platform meant working inside it: browser open, Setup menu navigated, page layouts configured. Salesforce Headless 360, announced at TDX on April 15, draws a line under that era. Every piece of the platform (data, workflows, business logic, compliance controls) is now reachable as an API, an MCP tool, or a CLI command. No browser required. Here is what that actually means if you build integrations or work with AI coding tools. Salesforce Headless 360 — How the Platform Is Now Exposed Salesforce Platform Data · Flows · Logic · Permissions Headless 360 REST / Bulk / Streaming Standard Salesforce APIs 60+ MCP Tools AI-callable structured tools CLI / DevOps Center Programmatic CI/CD access Human Developers CLI · VS Code · CI/CD pipelines AI Coding Agents Claude Code · Cursor · Codex Integration Systems MCP servers · External APIs No browser required. Every capability reachable as API, MCP tool, or CLI command. What Salesforce Headless 360 Ships With The headline number is 60 new MCP tools exposing Salesforce capabilities as structured interfaces that AI agents can call directly: objects, flows, deployments, permissions, reports. Alongside those, 30 preconfigured coding skills cover the most common Salesforce development tasks, from writing Apex triggers to configuring permission sets. DevOps Center MCP and Natural Language DevOps The DevOps Center MCP is the most immediately practical piece for integration teams: it brings programmatic access into any CI/CD pipeline. Natural Language DevOps sits on top of that: describe what you want to deploy in plain language and agents execute it. Salesforce cites a 40 percent cycle time reduction for development workflows as an early benchmark from teams using the integrated toolchain. The framing from Salesforce is that the build loop requiring context-switching across four different tools now happens inside one connected experience. That is the right framing, but the practical reality depends heavily on where your org’s metadata and documentation quality sits right now. What MCP means for Salesforce integrations The Model Context Protocol is becoming the default interoperability layer for AI agents across the industry. By exposing Salesforce through MCP, Salesforce is positioning itself as a participant in multi-agent orchestration, not just a destination for data, but a system that AI agents from Claude Code, Cursor, Codex, and Windsurf can work within directly. The practical shift for integration teams is significant. Instead of writing API wrappers manually (defining the request shape, handling authentication, mapping the response), you describe the integration behaviour and an agent executes and tests it using the MCP tools that already understand Salesforce’s object model. A Practical Integration Example For example: an integration that syncs Salesforce Opportunity data to an external billing system previously required a developer to write and maintain the API connection, handle field mapping, and manage error states. With MCP-exposed Salesforce tools and an AI coding agent, the same integration can be described in plain language, generated, and validated against the actual org schema, including custom objects and fields, without manual API documentation reading. The constraint is the quality of the description. Vague integration requirements produce vague integrations. MCP tools remove the API plumbing problem; they do not remove the requirement to know what you are building. Agent Fabric and multi-agent governance Headless 360 opens the Salesforce platform to AI agents. Agent Fabric answers the follow-on question: when you have multiple agents from multiple vendors operating across Salesforce and other systems, who governs them? Agent Fabric is the control plane launched at TDX 2026. It provides deterministic orchestration and centralised governance across agents, tools, and LLMs, scanning for agents across Salesforce Agentforce, Amazon Bedrock, Microsoft Foundry, and MCP servers, then providing a unified view of what agents exist, what they have access to, and what they are doing. Why Deterministic Governance Matters The governance problem it solves is specific: AI agents are probabilistic. They reason toward outcomes, which means their behaviour cannot be fully predicted from the instruction set alone. Agent Fabric adds the deterministic layer: Agent Broker defines fixed handoff rules between agents, Agent Script enforces compliance checkpoints within workflows, and Trusted Agent Identity ensures agents execute with specific user permissions rather than a shared service account. For architects designing systems where agents span Salesforce and external platforms, Agent Fabric is the piece that makes enterprise-grade deployment possible rather than merely experimental. Workflow Traditional Salesforce dev Headless 360 + AI coding agents Write an Apex trigger Open Developer Console or VS Code → write Apex → deploy to sandbox → test manually → deploy to production Describe the trigger behaviour in natural language → agent writes Apex using your org’s actual object model → review → deploy via DevOps Center MCP Build a Salesforce integration Read API docs → write request/response handlers → map fields manually → handle auth and error states → test in sandbox Describe integration behaviour → agent generates using MCP tools that understand your schema → automated testing → review and approve Understand an existing automation Open Flow Builder or Apex class → read through the logic → trace dependencies manually → ask a colleague Ask Vibes (Ask mode): “Explain this trigger and whether it conflicts with the Process Builder on this object” — org-aware answer with dependency context Debug a production issue Reproduce locally → inspect error log → trace through code → write fix → test → deploy Debug mode: agent analyses error log, identifies root cause in org context, proposes targeted fix → developer reviews and applies Deploy a change across environments Package the change → run change set or Salesforce CLI deploy → validate in staging → release Natural Language DevOps: describe the deployment in plain language → agent executes via DevOps Center MCP with CI/CD pipeline integration Context-switching across tools VS Code → Org → Developer Console → Sandbox → Jira → Slack → back to Org. Multiple context switches per task. One connected experience inside the development environment. Salesforce cites 40% reduction in development cycle time. What you need before Headless
TDX 2026 Salesforce Recap
Salesforce co-founder Parker Harris asked the question right before TDX 2026: “Why should you ever log into Salesforce again?” What got announced on April 15 in San Francisco was a structural redesign of how the entire Salesforce platform works. Here is the short version of everything that actually matters. 🌐 Headless 360Platform as API Every Salesforce capability is now an API, MCP tool, or CLI command. AI coding agents can build and act in your org without a browser. GA at TDX 60+ new MCP tools · 40% dev cycle time reduction 🎛️ Agentforce Vibes 2.0Org-aware AI dev IDE Vibe coding with full org metadata awareness. Four modes: Agentic, Plan, Ask, Debug. Runs on Claude Sonnet, GPT-5, and open source models. Preview May ’26 Multi-model · Paid tier required 🔄 AgentExchangeAppExchange renamed AppExchange, Slack Marketplace, and Agentforce ecosystem unified into one AI-searchable catalog. One-click activation. $50M Builders Fund. GA at TDX 13,000+ solutions · 1,000+ agents & MCP servers 📋 Agent ScriptOpen-sourced Deterministic scripting language for AI agents — fixed rules + LLM reasoning in between. Full spec, parser, and compiler now on GitHub. Open source Compliance-readable · Agent Fabric integration Headless 360: the browser is now optional For most of Salesforce’s history, building on the platform meant working inside it — browser open, Setup menu navigated, page layouts configured. Headless 360 draws a line under that era. Every capability on the Salesforce platform is now reachable as an API, an MCP tool, or a CLI command. Sixty new MCP tools and thirty preconfigured coding skills shipped at launch. The practical implication is that AI coding agents can now build and act inside your Salesforce org without a browser open anywhere. Salesforce cited a 40% cycle time reduction for development workflows as an early benchmark. The DevOps Center MCP brings programmatic access into any CI/CD pipeline, and Natural Language DevOps lets developers describe what they want to deploy rather than configuring it step by step. Agentforce Vibes 2.0: org-aware AI development Most AI coding tools write code that looks correct but does not know what objects, fields, profiles, flows, or integrations exist in your specific org. Agentforce Vibes 2.0 solves that. It uses the Salesforce Unified Catalog to provide context-aware suggestions from the first prompt. Four work modes ship with Vibes 2.0. Agentic mode for autonomous task completion. Plan mode for back-and-forth review before any code is written. Ask mode for questions about how the org or its code works, without triggering changes. Debug mode for inspecting what is happening in production and proposing a fix before applying it. Multi-model support is included: Claude Sonnet, GPT-5, and open source models. For organisations with model commitments or data residency requirements, that is material. Vibes 2.0 enters preview in May 2026. The free tier is being removed; a paid subscription is required. AgentExchange: one marketplace for everything AppExchange launched in 2006 and became the marketplace that nearly 90 percent of Salesforce customers used to extend the platform. It just became AgentExchange. The rename reflects a structural consolidation: AppExchange, the Slack Marketplace, and the Agentforce ecosystem are now unified into a single AI-searchable catalog. Ten thousand Salesforce apps, 2,600 Slack apps, and over 1,000 agents and MCP servers from partners including Google, DocuSign, and Notion now live in one place. One-click activation replaces the previous multi-step install process. A $50M Builders Fund provides investment, engineering support, and go-to-market backing for ISVs and partners building in the new ecosystem. Partner results from the announcement: DocuSign cut time to signature by 60 percent after listing on the new marketplace. Notion reduced its average sales cycle from four months to three weeks. Agent Script goes open source Agent Script is the scripting language Salesforce built to solve a specific problem: AI agents are probabilistic. They reason their way through scenarios and can arrive at unexpected outcomes because that is how LLM reasoning works. For enterprise deployments, that unpredictability is often a blocker. Agent Script adds a deterministic layer on top: you define the fixed logic and the LLM handles the reasoning in between the defined steps. At TDX 2026, Salesforce open-sourced the full specification, including the parser and compiler, on GitHub. The open-source move is a platform bet. Salesforce is inviting the broader developer ecosystem to build agent authoring tools on top of a shared language specification rather than a proprietary SDK. Furthermore, it makes Agent Script readable and auditable by compliance teams who do not write code. “Why should you ever log into Salesforce again?” Parker Harris, Salesforce Co-Founder Said before TDX 2026 — not a provocation, but the product roadmap. Every Salesforce capability is now reachable as an API, MCP tool, or CLI command. What this means for your org right now The honest answer is: less than the announcement energy suggests, and more than you can safely ignore. For orgs that are not yet using Agentforce at all, TDX 2026 reduced the distance between a prototype and a deployed agent. The infrastructure, APIs, MCP tools, Agent Script, a governed marketplace, is now in place. The question is no longer whether you can build on it; it is whether your org’s metadata, data quality, and team readiness support doing so reliably. For orgs already running Agentforce in production, Headless 360 and Agent Script are the most immediately relevant announcements. Headless 360 changes how integrations and CI/CD pipelines interact with the platform. Agent Script changes how you define and govern agent behavior at scale. Role Most relevant TDX announcement What to do now Salesforce Admin External Client Apps enforcement tightening in Summer ’26 alongside the sandbox upgrade. AgentExchange consolidation changes how you install managed packages. Act now Audit Connected Apps before May 9. Review AgentExchange for any solutions your org has been looking at. Developer Headless 360 ships 60+ MCP tools and enables AI coding agents to work directly inside Salesforce orgs. Agentforce Vibes 2.0 previews in May with org metadata awareness and four work modes. Plan for Assess your metadata hygiene — Vibes
Salesforce Tracks Field History. Just Not Enough of It
Salesforce tracks field history out of the box. Most admins know this. What they also know is that the native tracking has a ceiling of 20 fields per object, a retention window of 18 months, and a reporting layer that makes it genuinely difficult to answer the question: what changed, when, and who did it? For most orgs running real sales, compliance, or operations workflows, those limits are not theoretical. They are the reason someone eventually asks for something the system cannot produce. What native Field History Tracking actually gives you Salesforce’s built-in Field History Tracking works by logging changes to specified fields on standard and custom objects. When a field value changes, Salesforce records the old value, the new value, the timestamp, and the user who made the change. That information appears in a related list on the record. This is genuinely useful as far as it goes. For a small team with straightforward audit needs and a limited number of objects to monitor, it covers the basics without any configuration beyond selecting the fields to track. The limits become visible when the needs become real. Twenty fields per object is not a large number for an org where a Sales team, an Ops team, and a CS team are all working on the same objects with different fields they care about. Eighteen months is a short window for any compliance use case where a contract or customer relationship spans multiple years. And the related list view, while functional for looking up a single record, is not a reporting surface. ⚠ What happens when a deal value changes and nobody knows why The situation A rep closes a deal at $48,000. Commission is calculated. Three weeks later, the Opportunity Amount in Salesforce reads $38,000. The rep says the value was changed without authorisation. The manager says it was never $48,000. The deal was one of hundreds closed that quarter. Without True Field History The Amount field was not one of the 20 tracked fields — or the change happened during a bulk import that bypasses native logging — or it happened 19 months ago, outside the retention window. No verifiable record exists. The dispute is resolved by whoever has more leverage in the room. With True Field History The full history of the Amount field is available as a Salesforce report: original value, every change since creation, the user who made each change, and the timestamp. The dispute takes five minutes to resolve, and the answer is based on data, not memory. What True Field History does differently True Field History is a native Salesforce app built to remove the ceilings that the built-in tracking imposes. It runs inside your existing Salesforce org, uses the same objects and security model your team already works with, and does not require external infrastructure or a separate data store. The difference is in what gets tracked, how long it is retained, and what you can do with the data once it exists. Capability Native Field History Tracking True Field History Fields tracked per object 20 fields maximum Hard Salesforce platform limit — applies to all standard and custom objects Unlimited Track as many fields as your compliance or operations requirements need Data retention period 18 months Changes older than 18 months are purged automatically by Salesforce Configurable Retain history for as long as your business or regulatory requirements specify Reportability Related list only View history on one record at a time — cannot be included in standard Salesforce reports or dashboards Full Salesforce reporting History data is queryable via Reports and Dashboards — analyse across records, users, and time periods API and system user changes Partial API changes to tracked fields are logged, but still subject to the 20-field cap and retention window Full coverage All changes captured — human edits, integration users, API calls, and system processes Bulk and import changes Not logged Data Loader and bulk API changes are excluded from native field history by default Captured Import and bulk operation changes are logged with user, timestamp, and source Cross-record analysis Not available No way to report on which fields changed most, which users made the most edits, or change patterns across the org Available Build reports on change frequency, user activity, object-level trends, and pre/post-change values at scale Compliance audit readiness Limited Adequate for basic lookups within the 18-month window if the field was tracked — insufficient for formal audits on older data Purpose-built Designed to produce the complete, date-stamped change history that auditors and compliance teams require Installation Native — no install needed Native Salesforce app Installed in your org — no external infrastructure or separate data store No field cap True Field History tracks as many fields as your compliance, operations, or business requirements need — not as many as Salesforce’s 20-field limit allows. For objects with complex workflows where many fields carry business-critical information, this removes the prioritisation problem: you no longer have to decide which 20 fields matter most. Retention that matches your business timeline The 18-month native retention window is shorter than many contract cycles, audit requirements, or customer relationship timelines. True Field History retains the history you need for as long as your business requires it, without the automatic purge that native tracking applies. History that is actually reportable The related list view in native Salesforce is not a reporting surface. It shows you the history of one record at a time, which is fine for lookups but useless for analysis. True Field History stores change data in a structure that Salesforce Reports and Dashboards can query. That means you can answer questions like: which fields changed most frequently last quarter, which users made the most modifications to closed Opportunities, or which accounts had their contract value changed in the 30 days before renewal. System and API changes captured Changes made by integration users, system administrators, or API processes are logged alongside changes made by human users. For orgs with active integrations,
Stripe and Salesforce integration for SaaS companies
Your Stripe dashboard shows who is paying. Your Segment or PostHog shows who is actually using the product. Your Salesforce shows who the sales team is talking to. Three tools, three completely separate truths, and no connection between them. The most dangerous churn is the kind where a customer goes quiet in the product weeks before the renewal and nobody on the sales team knows, because they are looking at a different screen. At 30 to 50 people, this gap stops being an inconvenience and starts costing real revenue. How the Three Systems Connect in Salesforce Segment or PostHog PRODUCT EVENTS Stripe Billing & Subscriptions BILLING DATA Salesforce Account · Opportunity Contract · Lead · Contact SALESFORCE FLOW PQL events usage scores MRR · plan · status Renewal Opportunity auto-created at 90-day window PQL Task for Rep triggered by product threshold CS Churn Alert usage drop triggers CS queue Stripe and Segment/PostHog feed Salesforce. Flow automation handles the rest. How this gap forms at the 30–50 person stage At 10 people, three separate systems are manageable. The founder knows every customer. The CS lead knows the product numbers. The AE knows the renewal dates. Context lives in heads rather than systems, and that works until it does not. At 30 to 50 people, the team is too large for context to live in heads, and too small to have dedicated RevOps infrastructure. Stripe renewals are tracked in a shared spreadsheet that someone updates when they remember. Product usage reports are emailed by the data team on Fridays, if at all. Salesforce has the account records, but none of the product or billing reality is visible on them. The result is a sales team operating on incomplete information, a CS team reacting to churn rather than preventing it, and a leadership team whose pipeline numbers do not reflect what is actually happening in the customer base. Three problems that appear when these systems are not connected The renewal blind spot A subscription renewal is not a surprise event. The date is known. The contract value is known. And yet, in most SaaS companies at this stage, renewals are managed through a combination of calendar reminders, spreadsheet exports from Stripe, and a Salesforce pipeline that someone populated three months ago and has not touched since. The specific failure mode is not the missed renewal itself it is the missed signal. A customer whose usage dropped 60% in the 30 days before renewal is telling you something. Without Stripe and product data flowing into Salesforce, that signal is invisible. The rep goes into the renewal call having seen nothing change in CRM, not knowing the customer has already mentally moved on. Research from SaaS industry benchmarks consistently shows that companies managing renewals manually lose 10 to 15 percent more ARR to avoidable churn than those with connected systems. At a $3 million ARR base, that is between $300,000 and $450,000 a year in revenue that a spreadsheet is costing you. 10–15% more ARR lost The cost of managing renewals manually SaaS companies that track renewals in spreadsheets — without automated CRM visibility into billing and product usage — lose 10 to 15 percent more ARR to avoidable churn than those with connected systems. At a $3M ARR base, that is between $300K and $450K per year that a spreadsheet is costing you. SaaS industry renewal benchmarks The PQL opportunity going uncontacted The most valuable leads in a SaaS company are not the people who filled out a demo form. These are Product-Qualified Leads, and they are worth three to five times the conversion rate of a cold inbound lead. The problem is that the signal for a PQL lives in Segment or PostHog. It does not live in Salesforce. So when a user activates your most advanced features and invites four teammates in the same week, nothing happens in CRM. Meanwhile, the rep’s call list is full of people who clicked an ad or downloaded a whitepaper. The highest-intent users in your product are invisible. The quote and proposal bottleneck At this stage, sales reps are usually creating proposals in one of three ways: a Google Docs template they copy and paste from, a PDF that lives on someone’s desktop, or an email they wrote from scratch. None of these live in Salesforce. None of them can be tracked, approved by a manager, or analyzed for win rates. Furthermore, when a deal closes, nobody can trace back from the Opportunity to the quote that was sent. Pricing decisions, discount patterns, and approval workflows are invisible to leadership. The audit trail does not exist because the quotes were never in the system. What a sales rep’s week looks like without the integration vs. with it What the rep sees Without integration With integration Current MRR / plan ACV from when the deal was first entered. May not reflect a seat reduction or downgrade that happened in Stripe. Live MRR pulled from Stripe, updated on the Account record in real time. Seat count and plan visible at a glance. Product usage trend Not visible. Rep would need to ask the CS lead, who would need to pull a report from PostHog or Segment manually. 30-day engagement score and key feature activation events visible directly on the Account record. Renewal date In the spreadsheet maintained by one person. Or a calendar reminder. Possibly both, possibly disagreeing. Renewal Opportunity auto-created 90 days out, visible in pipeline alongside new business, with value from contract. Churn risk signal None — unless a customer raises a support ticket or emails to cancel. Risk is identified at or after the churn event. Usage drop flag auto-generated when engagement falls below baseline for 14+ days. CS task created before the call. Payment health Unknown. A declined card or failed payment from last month would not appear in CRM. Payment status from Stripe on the Account record. Failed payments surfaced as a risk flag before the renewal call. Expansion opportunity Rep guesses
How to Use GEO in Salesforce Experience Cloud
SEO is not dead, but it has a new layer on top of it. Spring ’26 added Generative Engine Optimization to Salesforce Experience Cloud — a single toggle in Experience Builder that tells AI engines like ChatGPT, Perplexity, and Gemini how to read your portal content directly from the source. If your customers are starting their searches in AI chat instead of Google, this matters more than you might think. Here is what the feature does, how to turn it on, and which types of Salesforce sites benefit most. What Generative Engine Optimization actually does When a user asks ChatGPT or Perplexity a question about your product or service, the AI engine looks for publicly available content to ground its answer. If your Experience Cloud site is not set up to accommodate that process, the engine either ignores it or generates an answer from indirect sources — which may not reflect your current content accurately. GEO changes that by allowing AI bots to request a structured content snapshot of your public site pages. The snapshot gives the AI a clean, source-verified version of your content to work with, rather than a cached or scraped approximation. The result is that your portal becomes citable: when someone asks an AI assistant a question your help center or community site answers, there is a higher chance the answer comes from your actual content. This is the core difference from traditional SEO. Traditional SEO tells Google’s web crawler how to index your page for search ranking. GEO tells AI language model crawlers how to read and reference your page when generating answers. Dimension Traditional SEO GEO Target audience Google, Bing, and other traditional search engine crawlers AI-powered answer engines: ChatGPT, Perplexity, Gemini, Google AI Overviews Goal Rank higher in search results pages Be cited accurately in AI-generated answers Core mechanism Crawlable HTML, meta tags, backlinks, structured data, page speed Structured content snapshots that AI bots can request and process What it optimises for Click-through from a results list Accuracy and attribution when the user never sees a results list Where users see the result A link in a list of search results they click through An answer that cites your content directly in the AI interface Requires publishing Crawled on Google’s schedule, not yours Snapshot reflects your content as of the last site publish How to enable in Salesforce SEO settings: page title, meta description, canonical, sitemap Experience Builder → Settings → SEO → enable GEO toggle → republish Replaces the other? No — parallel tracks for parallel channels. Both are worth managing. Where to find the toggle and how to enable it The GEO setting lives in Experience Builder under the SEO settings panel. The path is: Experience Builder → Settings → SEO → Provide content snapshots of public site pages when requested by AI bots Enable the toggle, then republish the site. The setting takes effect on the next publish. It applies to both Aura and LWR sites and is available in Enterprise, Performance, Unlimited, and Developer editions. There is no additional configuration required at the page level. The toggle works across all public-facing pages on the site. Pages behind authentication are not included — GEO only applies to content that is publicly accessible without a login. How to Enable GEO in Experience Builder Spring ’26 — 3 steps 1 Open your Experience Cloud site in Experience Builder Navigate to the site you want to update. You need Admin access or a profile with Experience Cloud site management permissions. Setup → All Sites → Builder 2 Go to Settings → SEO and enable the GEO toggle In the left panel, open Settings. Select SEO. Find the option labelled “Provide content snapshots of public site pages when requested by AI bots” and enable it. Settings → SEO → AI bots toggle → ON 3 Publish the site The GEO setting takes effect on the next publish. Click Publish in Experience Builder to apply the change. The setting then applies to all public-facing pages on both Aura and LWR sites. Publish → Confirm Available in Enterprise, Performance, Unlimited, and Developer editions. Applies to public pages only — authenticated content is not included. What a content snapshot actually is A content snapshot is a static HTML version of your page that AI crawlers can request and process. It is optimised for machine reading rather than browser rendering — it strips out the dynamic elements, JavaScript-rendered content, and navigation chrome, and returns the core textual content of the page in a clean format. For AI engines, this is more reliable than attempting to crawl a JavaScript-heavy page where the main content only appears after client-side rendering. Furthermore, it means the snapshot reflects what is actually published in your Salesforce CMS, not a cached version from weeks ago. The practical implication is accuracy. If your help center article says your product supports a specific integration, the snapshot contains that exact statement. The AI engine citing your content has a verified source, rather than a reconstructed one. Which Salesforce portals benefit most from enabling GEO Which Salesforce Portals Benefit Most from Enabling GEO Public pages only 📖 Self-service help centers and knowledge bases Articles, FAQs, and troubleshooting guides are exactly the content AI engines look for when answering product questions. GEO makes your help content the cited source instead of a paraphrased approximation. Highest impact 🤝 B2B partner portals with public documentation Product docs, integration guides, and pricing pages are actively searched by B2B buyers using AI research tools. A GEO-enabled portal appears in that research process; one without it does not. High impact 💬 Community sites with publicly visible content Community answers to product questions are high-value for AI engines because they reflect real usage. If your community is publicly viewable without login, GEO makes that content accessible in the right format. Good candidate 🏢 Customer-facing product or service information sites Any Experience Cloud site where prospects or customers look up your features, plans, or support
Connected Apps Are Being Retired in Salesforce
Starting with Spring ’26, Salesforce disabled the creation of new Connected Apps by default across all orgs. Your existing ones still work for now. But the direction is clear: External Client Apps are the future, and the clock is running. This guide covers what changed, why Salesforce made this move, what External Client Apps actually give you, which apps are and are not affected, and a step-by-step migration walkthrough through App Manager. The second half is a structured checklist for the audit before you migrate and the testing after. The TLS certificate changes happening in the same release are covered at the end, because both come from the same security-first motivation. Spring ’26 Migration Timeline & TLS Certificate Phase-Down Connected Apps → External Client Apps 1 Winter ’26 New Connected App creation disabled by default in new orgs Opt-in 2 Spring ’26 New creation disabled across all orgs — Support request required Enforced 3 Summer ’26 Expected enforcement deadline — plan migration before this Deadline 4 Summer ’26 Triple DES for SAML SSO stops working completely Hard Stop TLS Certificate Lifespan Phase-Down (CA-signed certificates only) A Until Mar 14, 2026 Max lifespan 398 days (previous standard) B Mar 15, 2026 Max lifespan drops to 200 days Now C Mar 15, 2027 Max lifespan drops to 100 days Plan for D Mar 15, 2029 Max lifespan drops to 47 days — automation required Automate Why Salesforce is making this change Connected Apps have been part of Salesforce for over a decade. If you have ever set up OAuth for a third-party integration, configured Data Loader, or connected a custom web application to the Salesforce API, you have used one. They are everywhere, and most of them work fine. The problem is not the apps that are configured properly. The problem is the ones that are not, and the architecture that makes unsafe configurations easy to create. By default, Connected Apps allow any API-enabled user in an org to self-authorise a connection to an external application, without admin approval. That is how phishing and vishing attacks that targeted Salesforce orgs worked: trick a user into authorising a malicious Connected App, and the attacker has API access to the org’s data. Salesforce responded by tightening this behaviour, but the structural issue remained. External Client Apps take a different starting position. They adopt a closed security posture by default. Access is not granted unless an administrator explicitly permits it. Furthermore, the architecture separates developer configuration from admin policy, which means a developer building an integration cannot inadvertently override security settings that the admin put in place. What changed in Spring ’26, specifically The rollout has been gradual. In Winter ’26, Salesforce disabled Connected App creation by default in new orgs, with an option for admins to re-enable it manually. Spring ’26 tightened that further: new Connected App creation is now disabled across all orgs, including existing ones. Getting the ability back requires a Salesforce Support request, and Salesforce has been clear that this option will eventually disappear entirely. Two categories of Connected Apps are not affected by this change. Connected Apps created as part of a managed package continue to work and can still be created in that context. Connected Apps used for Slack in the legacy Agentforce Builder are also excluded. Everything else follows the new default. Any new integration from Spring ’26 onward must be built as an External Client App. ⚠ What happens if you try to create a new Connected App without a Support request The New Connected App button no longer appears in App Manager — the option is gone from the UI entirely. Attempting to create one via the Metadata API returns an error. There is no workaround inside the platform. Any new integration built after Spring ’26 that requires its own OAuth client must use an External Client App instead. If a specific business case genuinely requires a new Connected App, you must open a Salesforce Support case and explicitly request the capability. Salesforce may or may not grant it, and this option will be removed in a future release. What External Client Apps offer that Connected Apps do not External Client Apps are not just Connected Apps with a new name. The differences are architectural, and several of them matter a lot depending on how your org is set up. Separation of developer settings and admin policies In a Connected App, the developer configuration and admin security policies live in the same record. A developer with edit access to the Connected App can change the OAuth scopes, the IP restrictions, and the session policies. In an External Client App, those roles are separated. Developers manage the technical settings; admins manage the access policies. Neither can override the other without the appropriate permission. For ISVs and AppExchange partners, this matters enormously. It means the admin installing your package can control how it behaves in their org without touching the underlying app configuration. Second-generation packaging support External Client Apps are designed specifically for second-generation packaging, or 2GP. Connected Apps technically work with 2GP, but the process required manual steps that were fragile and time-consuming. ECAs package cleanly, distribute correctly, and integrate naturally with source control and CI/CD pipelines via the Metadata API. For admins managing integrations rather than building packages, the practical difference is that ECAs behave more predictably in sandboxes and scratch orgs. Scratch Org support for External Client Apps was added in Spring ’26, which makes the developer testing cycle considerably cleaner. Closed security posture by default A new External Client App is not accessible to any user until an administrator explicitly grants access. There is no self-authorisation pathway by default. This is the core security difference from Connected Apps, and it is the reason Salesforce is moving in this direction. What ECAs do not yet support Two important gaps remain. External Client Apps do not support the Username-Password OAuth flow. If any of your existing Connected Apps use this flow, you cannot migrate them
Salesforce Setup Roadmap for SaaS Companies
Setting up Salesforce for a SaaS company is not the same as setting it up for a real estate agency or a professional services firm. Subscriptions, trials, renewals, MRR, none of that exists in a default Salesforce org. Getting it right means building a system that reflects how SaaS revenue actually works: from the first lead through to the second and third renewal. This is the setup roadmap used with SaaS companies at every growth stage. SaaS Salesforce Setup — Three-Phase Roadmap Phase 1 Pipeline Control 2 – 15 people SaaS-configured objects (MRR, ACV, trial stages) Website lead capture via Web-to-Lead Email and calendar auto-sync Basic quota tracking Clean data migration Foundation Phase 2 Process & Prevention 15 – 30 people Contract Management object New Business vs Renewal quota split Round Robin lead assignment Calendly integration Outbound activity logging Scale-Ready Phase 3 Revenue Intelligence 30 – 50 people Product data via Segment / PostHog Stripe subscription sync Automated Renewal Opportunities Quotes object and PDF proposals RevOps forecasting Fully Connected Build in sequence — each phase is the foundation for the next The roadmap breaks into three phases, each tied to the problems that appear at a specific team size. Phase 1 is about getting your data into one place and your pipeline under control. Phase 2 is about building process before things break. Phase 3 is about connecting your product and revenue data so the whole system works without manual intervention. Most SaaS companies skip Phase 1 entirely, configure a few things in Phase 2, and then wonder why Phase 3 never delivers the visibility they expected. ⚠ What breaks when you skip Phase 1 and go straight to Phase 3 No clean data foundation Stripe sync and product events write to duplicate or incomplete records. Automation fires on bad data. No stage or quota logic RevOps forecasting has nothing reliable to forecast. Pipeline reviews become guesswork in a different tool. No email or activity sync Automated tasks get created on leads with no interaction history. Reps ignore them because there is no context. No Contract Management object Renewal Opportunity automation has no subscription terms to read. The automation cannot trigger correctly. No team training or adoption The Phase 3 system sits unused while the team works in spreadsheets. The investment does not produce results. Phase 1 (2–15 people): Get the pipeline under control At this stage, most SaaS teams have contacts in a spreadsheet, deals tracked in someone’s head, and follow-up happening through email threads. Salesforce at Phase 1 has one job: get everything into one system and make it usable for a small team with no dedicated ops person. Configure core objects for SaaS context A default Salesforce org is built for transactional sales. The standard Opportunity fields assume a one-time deal. For SaaS, you need subscription-aware fields from the start. That means adding fields for Monthly Recurring Revenue, Annual Contract Value, trial start and end dates, subscription tier, and billing interval. The Lead object also needs updating. Source fields should reflect where SaaS leads actually come from: product sign-up, inbound form, G2 review, or referral. Furthermore, the Opportunity stage names matter more than most teams realise. Default stages like ‘Prospecting’ and ‘Perception Analysis’ mean nothing in a SaaS context. Replace them with stages that reflect your actual sales motion: Trial Active, Demo Scheduled, Proposal Sent, Closed Won, Closed Lost. Set up lead capture from your website Every SaaS website has a form or a trial sign-up button. In most early-stage companies, those leads land in an email inbox or a spreadsheet. Connecting your website forms directly to Salesforce via the Web-to-Lead feature takes an afternoon and immediately removes the manual logging step. For trial sign-ups specifically, the connection between your product and your CRM is worth building early. Even a simple webhook that creates a Lead when a user signs up gives your team visibility into who is in the product — before you build anything more sophisticated. Connect email and calendar Manual activity logging is the reason most CRM data goes stale within three months of implementation. When reps have to log every call and email by hand, they stop doing it. Salesforce Inbox or the standard Gmail and Outlook integrations sync email threads and calendar events automatically. As a result, every Lead and Contact record shows a complete interaction history without anyone updating it manually. That is the baseline that makes everything else in the CRM trustworthy. Set up sales quotas early Most founders skip quota configuration at Phase 1 because the team is too small. That is a mistake. Setting up quota tracking in Salesforce from the beginning creates a performance culture before the team grows. Specifically, it gives you a reference point when you are making your first sales hire: what does good look like, and what is the current baseline? Quota configuration at this stage is simple. Assign monthly or quarterly revenue targets per user, and build a single Salesforce report that shows actuals versus target. That is all you need at 2–15 people. Data migration: clean before you move Almost every SaaS company arrives at Salesforce with a mix of HubSpot exports, Notion tables, and Airtable bases. Before migrating any of that data, spend time cleaning it. Remove duplicates, standardise company names, and decide which fields you actually need to carry over. Moving messy data into Salesforce does not fix the mess. It just moves it into a more expensive system. A clean migration of 500 accurate records is considerably more useful than importing 3,000 records with no confidence in the data. Phase 1 — Pipeline Control Checklist 2–15 people Core object fields configured — MRR, ACV, trial dates, subscription tier on Opportunity; SaaS lead sources on Lead Opportunity stage names updated — replaced with SaaS stages: Trial Active, Demo Scheduled, Proposal Sent, Closed Won, Closed Lost Web-to-Lead connected — website form and trial sign-up button create Lead records automatically Email and calendar sync live — Gmail or Outlook integrated;
How to Find Your SaaS PQL in Salesforce
Product-led growth gets talked about as a marketing strategy. It is actually a data strategy. The moment a user signs up for your free trial, they start telling you exactly how likely they are to pay, through every click, every feature they open, and every session they skip. Most SaaS sales teams have no idea any of that is happening. None of it is in their CRM. What is a Product-Qualified Lead? A Product-Qualified Lead, or PQL, is a user who has reached a meaningful milestone inside your product. They activated a key feature, hit a usage threshold, invited a teammate, or upgraded their storage. Whatever the milestone is, they are doing the thing your product is designed to do. That makes them different from every other lead type in your funnel. A Marketing-Qualified Lead clicked an ad or downloaded an ebook. A Sales-Qualified Lead filled out a demo form. Neither has actually used your product. A PQL has, and in most PLG companies, that difference shows up as a 3% conversion rate versus a 25% one. Furthermore, PQLs are consistently underused. Not because companies do not want to act on them, but because the signal lives somewhere the sales team cannot reach. Why the PQL signal gets wasted without CRM integration Product analytics tools capture this data well. Segment, Mixpanel, PostHog, and Amplitude track every session, every feature interaction, and every drop-off point with precision. The dashboards are detailed. The data is there. However, your sales team is not in those dashboards. They are in the CRM. And in most PLG SaaS companies, those two systems do not talk to each other. The result is a structural disconnect. Your product knows which users activated three core features in a seven-day trial. Your reps are calling people who downloaded a whiteboard template six weeks ago. Meanwhile, the user who is two steps from converting sits uncontacted in your product database, not in your pipeline. This is not a prioritisation problem. It is a data infrastructure problem. Specifically, it is fixable. PLG Trial-to-Paid Funnel in Salesforce Trial Signup by source & channel Activation key feature milestone reached PQL Trigger usage threshold, invite, or score met Sales Action rep task auto-created in Salesforce Closed-Won Here is what four common PQL triggers look like in practice. 1. Trial activation trigger A user activates three core features within seven days of signing up. Salesforce creates a task for a rep to reach out with a targeted expansion message. The rep sees the activation data directly on the Lead record. 2. Churn risk alert A user’s engagement drops below their baseline for 14 consecutive days. Salesforce creates a CS alert before the churn event. The CS team can intervene with full context on what the user did and did not do. 3. Account expansion signal Five or more users at the same account invite colleagues during the trial period. Salesforce scores the Account higher and moves it into an expansion workflow automatically. 4. Free-to-paid attribution A free-to-paid conversion is tracked as a closed Opportunity, connected to the original trial Lead record. Marketing attribution becomes real, not estimated. Situation Without PQL data With PQL data in Salesforce Who reps contact first Demo form leads, regardless of product activity Users who activated key features, ranked by engagement score What reps see on a Lead record Name, email, company, source Features activated, sessions logged, days since last login, PQL status Churn detection Customer cancels, CS finds out after the fact Usage drop triggers CS alert at day 14, before churn event Free-to-paid attribution Estimated or modelled based on last-touch channel Closed Opportunity linked directly to original trial Lead record Account expansion signals No visibility until a user reaches out or upgrades manually Automatic score increase when 5+ teammates invited during trial PLG funnel visibility Sign-up volume and revenue, nothing in between Full funnel: signup, activation rate, PQL rate, closed-won from trial How to build this in Salesforce The most practical starting point is a set of Custom Fields on the Lead or Contact record that reflect product activity. You do not need a full Customer Data Platform to get started. You need a clean data feed and clear trigger logic. 3 PQL triggers worth setting up first 1 Feature activation trigger User activates 3 or more core features within 7 days of signing up. This is the clearest signal that the product is working for them, and the highest-intent moment to start a conversation. Trigger: 3 features in 7 daysAction: Rep task created in Salesforce 2 Churn risk trigger User engagement drops below their personal baseline for 14 consecutive days. Acting at day 14 gives CS enough lead time to re-engage before the user mentally cancels. Trigger: 14-day usage dropAction: CS queue alert in Salesforce 3 Account expansion trigger Five or more users from the same account invite colleagues during the trial period. Team adoption during trial is one of the strongest predictors of a paid conversion at the account level. Trigger: 5+ teammate invitesAction: Account score increase + expansion workflow Step 1: Define your PQL criteria Before any configuration, decide what product-qualified means for your specific product. Pick two or three behaviours that correlate with paid conversion in your existing data. Common examples include activating a specific feature, reaching a usage volume threshold, or completing an onboarding checklist. If you do not have conversion data yet, start with Salesforce Trailhead’s PLG resources or the Salesforce Admins blog for benchmark guidance on typical SaaS activation signals. Step 2: Connect your product data to Salesforce The most common paths are a native integration from your analytics tool, a Salesforce-connected webhook from your product backend, or a middleware tool like Segment Connections or Census. Each approach writes product events into Salesforce fields or Custom Objects. Step 3: Build the trigger logic in Salesforce Flow Use Salesforce Flow to create the automation. When a product field meets your PQL criteria, Flow triggers an action. That action
