◆ Salesforce

Pass parameters to Visual Workflow

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskWhen a new 'High Priority' case is created, pass the case ID and the contact's email address to…+
When a new 'High Priority' case is created, pass the case ID and the contact's email address to the 'Urgent Notification' flow, so the on-call team gets immediate alerts and can respond quickly.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore the 'Client Onboarding Checklist' flow goes live, ensure it can receive the 'Client…+
Before the 'Client Onboarding Checklist' flow goes live, ensure it can receive the 'Client Tier' and 'Assigned Account Manager' from the opportunity record, so the flow customizes the onboarding steps based on client importance and who's responsible.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe sales director wants a new 'Discount Approval' flow to trigger when a discount over 15% is…+
The sales director wants a new approval process, but I can't get the right information into the flow.
The sales director wants a new 'Discount Approval' flow to trigger when a discount over 15% is requested on an opportunity. I need to pass the proposed discount percentage and the opportunity's total value to the flow, but it's not recognizing the fields correctly. I'm worried it will either approve too much or get stuck in a loop. What's the most reliable way to get these specific values into the flow for accurate decision-making?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently build flows that need to make decisions based on multiple fields from the…+
I often struggle to get the right data from records into my flows for complex logic.
I frequently build flows that need to make decisions based on multiple fields from the triggering record, like an opportunity's stage, amount, and product family. I often spend too much time troubleshooting why the flow isn't receiving the correct parameters. What habit should I change to consistently and efficiently pass all necessary data from the record into my flows for complex business logic?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Salesforce's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.