#Flow156 人がディスカッション中

Maybe Zapier creates and then updates the Opportunity? It might come in from Zapier at $0, then get immediately updated? Maybe try the following in a sandbox or dev org. Three possible ideas: 

1. Can you change to update the flow to trigger when a record is created or updated? Or would that not work for your circumstance? 

2. If you do change it to created or updated, you could select to have it run only when a record is updated to meet the condition requirements, and then make sure the requirements are even more specific. 

3. OR, instead of doing those two things, try to remove an entry criteria at a time to see if one of the criteria seems to be causing this to happen. 

Yes — as of the Spring '25 release, the standard Flow core action "Send Email" (not the older Email Alert action) supports attachments directly. It added an Attachment ID input parameter that accepts a ContentVersion Id (Salesforce Files), a classic Attachment Id, or a Document Id — so your files can live as Salesforce Files, classic Notes & Attachments, or a Document, and you just pass the record Id into that parameter. 

You can also set the Email Template Id on that same Send Email action, so the flow renders the template as the body and attaches the file(s) in the same step. 

One limit worth knowing: total email size, including attachments, is capped at 35 MB. 

Official doc: help.salesforce.com, article id platform.flow_ref_elements_actions_sendemail.htm ("Send Email Action"). 

Assumption: I'm assuming you're on Spring '25 or later, since attachment support on the core Send Email action is a fairly recent addition — before that release, the standard action couldn't attach files at all, and people had to fall back to an invocable Apex action using Messaging.SingleEmailMessage with setEntityAttachments()/setFileAttachments() instead. If you're on an older release, let me know and I can point you to that Apex-based workaround. 

Hi , 

 To redirect users in a screen flow to a specific page in Salesforce after they click 

Finish, use this format.  

/lightning/flow/flowName?retURL=url

https://help.salesforce.com/s/articleView?id=platform.flow_distribute_internal_url_returl.htm&type=5

I did this with my org and it worked perfectly until one of the record owners quit and their user became inactive. When we attempted to unqualify the leads so they could be added to the cadence, there was an error and leads could not be unqualified. Does anyone have a solution to this?  

Note- We do not use a lead queue, our lead assignment is either manual or automated via zapier.  

Thanks 

@Craig Munster

Ah, that's the missing piece — and you're right, I was wrong to steer you off your formula field. On an Opportunity Product button the native OpportunityId genuinely isn't exposed in the merge-field picker (annoying known quirk). Your Opportunity_Id__c CASESAFEID field is exactly the right workaround, so keep it — custom fields DO show up under Insert Field. Just reference that one instead of OpportunityId: 

/flow/Opportunity_Product_Screen_Flow_Clone_Opportunity_Product?recordId={!

}&retURL=/lightning/r/Opportunity/{!OpportunityLineItem.Opportunity_Id__c}/related/OpportunityLineItems/view 

That sends them back to the Products related list on the parent Opp. Sorry for the runaround getting there! 

If this helps, please mark it as the Best Answer so it helps the next person — thanks 🙂

@durgam santhosh

Yes - the native no-Apex route is an Email Alert (the core 'Send Email' Flow action won't render a template's merge fields). Create an Email Alert on Opportunity (Setup > Email Alerts) that uses your Opportunity Lightning template, then call it from your record-triggered Flow as an Action - the alert sets the triggering Opportunity as the Related To, so all your Opportunity merge fields resolve. 

For recipients you can pick Opportunity Owner directly; to send to that custom email field it has to be an Email-type field, then it shows up under Recipient Type 'Email Field'. 

If this helps, please mark it as the Best Answer so it helps the next person - thanks!