<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:blog="http://dnn-connect.org/blog/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>Blog - #LightningFlowtips</title>
    <link>https://xrmlabs.com/About-Us/XRMs-Blog/term/3100/locale/en-US/Blog-LightningFlowtips</link>
    <description />
    <managingEditor>sales@xrmlabs.com</managingEditor>
    <pubDate>Thu, 16 Apr 2026 03:04:55 GMT</pubDate>
    <lastBuildDate>Thu, 16 Apr 2026 03:04:55 GMT</lastBuildDate>
    <category>#LightningFlowtips</category>
    <generator>DotNetNuke Blog RSS Generator Version 6.5.2.0</generator>
    <ttl>30</ttl>
    <atom:link href="https://xrmlabs.com/DesktopModules/Blog/API/RSS/Get?moduleid=440&amp;tabid=94&amp;term=3100" rel="self" type="application/rss+xml" />
    <item>
      <title>The Hidden Power of Subflows in Record-Triggered Automation</title>
      <link>https://xrmlabs.com/About-Us/XRMs-Blog/Post/8665/The-Hidden-Power-of-Subflows-in-Record-Triggered-Automation</link>
      <description>&lt;p&gt;In this blog, we explore the hidden power of subflows in record-triggered automation.&amp;nbsp;&lt;br /&gt;
Salesforce Flow has become the gold standard for no-code and low-code automation. But as record-triggered automation becomes more powerful, complexity naturally follows. That&amp;rsquo;s where subflows come in &amp;mdash; a hidden gem that can simplify, modularize, and scale your automation efforts.&amp;nbsp;&lt;/p&gt;
</description>
      <category>#LightningFlowtips</category>
      <category>#SalesforceAutomation</category>
      <category>#SalesforceBestPractices</category>
      <category>#SalesforceFlows</category>
      <category>#SalesforceTips</category>
      <guid isPermaLink="true">https://xrmlabs.com/About-Us/XRMs-Blog/Post/8665/The-Hidden-Power-of-Subflows-in-Record-Triggered-Automation</guid>
      <pubDate>Fri, 03 Oct 2025 19:58:00 GMT</pubDate>
      <blog:publishedon>2025-10-03 19:58:00Z</blog:publishedon>
    </item>
  </channel>
</rss>