◆ Salesforce

Trigger flow on specific field change

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
See the prompt↓All Salesforce tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskTrigger the 'UpdateAccountTier' flow whenever the 'Annual_Revenue__c' field on an Account…+
Trigger the 'UpdateAccountTier' flow whenever the 'Annual_Revenue__c' field on an Account record changes. This needs to be live by Friday morning.
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 acceptI'm setting up a flow to update account tiers based on revenue changes. Before I activate it,…+
I'm setting up a flow to update account tiers based on revenue changes. Before I activate it, can you ensure the trigger for 'UpdateAccountTier' flow only fires when 'Annual_Revenue__c' actually changes to a new value, not just when the record is saved without a change? Also, add a condition to prevent it from firing for 'Prospect' accounts, so we don't waste resources on unqualified leads.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur 'LeadAssignment' flow is firing multiple times whenever a sales rep updates a lead's…+
Our 'LeadAssignment' flow is firing multiple times whenever a sales rep updates a lead's status, causing duplicate assignments.
Our 'LeadAssignment' flow is firing multiple times whenever a sales rep updates a lead's status, causing duplicate assignments. Sales reps are frustrated, and leads are getting confused. I set the flow to trigger on 'Lead Status' change, but something is causing it to re-evaluate. I'm afraid I've created an infinite loop or an unintended re-trigger. What's the most common cause for a flow to trigger repeatedly on a single field change, and what's the best way to quickly identify and correct the trigger conditions without breaking other automations?
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 encounter issues where flows trigger unexpectedly or multiple times, leading to…+
I frequently encounter issues where flows trigger unexpectedly or multiple times, leading to data inconsistencies or performance problems.
I frequently encounter issues where flows trigger unexpectedly or multiple times, leading to data inconsistencies or performance problems. It's a constant source of post-deployment headaches. The recurring pattern is that my trigger conditions aren't always robust enough to handle all user behaviors or system updates. What habit can I change in how I define and test flow trigger conditions to ensure they fire precisely when intended and only once, so I build more reliable automations from the start?
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.