◆ Salesforce

Trigger flow when specific field changes

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 taskI need to kick off a flow when the 'Stage' field on an opportunity changes. Configure the flow…+
I need to kick off a flow when the 'Stage' field on an opportunity changes. Configure the flow to trigger only when that specific field is modified.
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 I deploy this opportunity update flow, I need to ensure it only runs when necessary. Set…+
Before I deploy this opportunity update flow, I need to ensure it only runs when necessary. Set it up to trigger specifically when the 'Stage' field changes, not just any edit, to avoid unnecessary processing and maintain system performance.
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 opportunity follow-up flow is sending out duplicate emails every time any field is edited,…+
The opportunity follow-up flow is sending out duplicate emails every time any field is edited.
The opportunity follow-up flow is sending out duplicate emails every time any field is edited, not just when the 'Stage' changes, and the sales team is getting swamped with notifications. The head of sales just called me. I can't tell them I don't know why it's over-triggering. How do I diagnose why the flow is triggering on every edit, and what's the quickest way to restrict it to only trigger when the 'Stage' field specifically changes?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur flows often trigger on any record edit, leading to performance issues and user frustration…+
Flows are over-triggering, causing performance issues and user frustration.
Our flows often trigger on any record edit, leading to performance issues and user frustration from too many notifications. This wastes our team's time troubleshooting. What habit should I change to consistently ensure flows are configured to trigger only when specific, critical fields change, making our automations more efficient and reliable?
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.