Monday morning. A Sales Manager reviews last week's deals and finds that of eighteen Opportunities moved to the "Proposal Sent" stage; only twelve had the Conga proposal emailed. Six are open — customer waiting, rep already on the next deal, nobody noticed. By Wednesday, two of those customers go silent. By Friday, one signs with a competitor.
This isn't a sales discipline problem. It's an automation gap. Updating an Opportunity and sending the right document shouldn't be two manual steps that depend on a rep remembering both. Record-Triggered Flows on Salesforce, paired with Conga's document generation engine, run the chain automatically: stage changes, Conga template fires, branded email lands in the customer's inbox, audit trail captured on the Opportunity. No rep involvement past the click that moves the stage.
The fix is a Record-Triggered Flow architecture that listens to Opportunity stage changes, calls the right Conga template per stage, sends the personalized document automatically, and writes the send event back to the Opportunity for visibility.
Here's how to automate Salesforce Opportunity updates and Conga emails with Record-Triggered Flows.
Five forces fragment Opportunity-to-document automation:
Each gap creates one lost deal a month. Combined, they explain why proposal conversion looks worse than it should.
Salesforce phased out Workflow Rules and Process Builder. Record-Triggered Flows are the modern automation surface for stage changes on Opportunity, Account, Case, and custom objects.
The Flow fires when an Opportunity's StageName changes — explicitly on entering or exiting a stage. Granularity that Workflow Rules never supported.
A single Flow can update the Opportunity record, call Conga's REST API to generate the document, send the email, write a log to a custom Audit object, and post to Chatter — all in one transaction.
Stage-change automation that fires for Proposal Sent, Contract Sent, and Won notifications shares most of the same logic. Sub-flows let one Flow handle multiple stage transitions without duplication.
Three architectural rules keep the Conga template library clean and ensure the right document fires every time.
Don't hardcode template IDs in the Flow. Store the mapping in a custom Metadata Type so admins can update templates without changing the Flow.
A Proposal Sent template for North America differs from the one for EMEA — different legal language, currency, terms. The Flow reads the Account's Territory and product line and picks the matching template.
When legal updates the warranty language, the new template version takes effect from a defined date. Older Opportunities use the version that was active when their Opportunity opened.
Five Record-Triggered Flow patterns that cover most Opportunity-to-Conga automation.
When stage enters "Proposal Sent," generate the branded quote PDF from the Primary Quote and email to the primary Contact. Update Opportunity with Send timestamp.
When stage enters "Contract Sent," generate the contract from the Primary Quote and route via Adobe Sign or Docusign for signature.
When stage enters "Closed Won," send a branded welcome to the customer and an internal notification to Finance, Operations, and the Account Manager — all in one Flow.
When stage enters "Closed Lost," send a short customer survey via Conga and update the rep pipeline coverage dashboard. Loss reasons captured for forecasting.
When an Opportunity sits at any stage past the configured threshold, post a Chatter alert to the Sales Manager and email the rep with the stuck record link.
Five validation rules keep the Flow + Conga chain honest under load.
Block stage progression unless the required Opportunity fields are populated. Conga templates can't merge into a NULL field.
Capture the Conga template version active at Opportunity Open. Subsequent template updates don't retroactively change in-flight Opportunities.
Block stage entry to "Proposal Sent" without a linked Primary Quote. The Flow needs a record to read from.
Block stage entry without a valid email on the primary Contact. Conga can't send to a NULL or malformed address.
Wire the Audit object write to the same transaction as the Conga API call. No emails were sent without audit.
"A Flow without an audit log is a Flow you'll regret the day a customer asks what you sent."
Record-Triggered Flows replaced Workflow Rules and Process Builder as the modern automation surface. Flows support multiple actions per trigger, sub-flows, complex branching, fault paths, and external API calls — all things Workflow Rules couldn't do. Salesforce no longer recommends creating new Workflow Rules; Record-Triggered Flows are the supported path.
Yes. Conga exposes a REST API that Salesforce Flows invoke through HTTP Callout actions or a dedicated invocable Apex class. The Flow sends the Opportunity ID and template reference; Conga generates the document and returns the file URL, which the Flow attaches to the Opportunity.
Every external callout in a Record-Triggered Flow should sit inside a fault path. When Conga returns an error — missing template, merge failure, authentication issue — the fault path captures the error, writes it to a custom log object, notifies the admin, and prevents the stage update from silently failing.
Wire the Flow to write a record to a custom Audit object every time a Conga document is sent. Include Opportunity ID, template version, recipient email, timestamp, and the file URL Conga returned. The audit becomes the answer when a customer disputes whether a document was sent.
Manufacturers fix the Monday morning lost-proposal problem by re-architecting the Opportunity-to-document layer - Record-Triggered Flow automation on stage changes, Conga template selection by Territory and product line, fault-path error handling, and audit logging. This isn't a sales discipline issue; it requires Salesforce engineering across the Flow architecture, Conga API integration, and the audit object that captures every send.
Minuscule Technologies is a Trusted Salesforce Engineering Partner with 160+ Salesforce experts and 75+ projects delivered globally — including Nasdaq-listed manufacturers across heavy equipment, HVAC, automotive, and industrial sectors. We engineer Record-Triggered Flow and Conga automation that turns every stage change into a customer touch with full audit trail.
Connect with our enterprise architecture team and we'll review your Flow architecture, Conga template strategy, and audit logging design.
You've seen what's possible. Now, let's make it happen for your business. Whether you need an end-to-end Salesforce solution, a complex integration, or ongoing managed services, our team is ready to deliver.
Schedule a Free Strategic Call
