◆ Salesforce

Check isInsert or isUpdate in Flow

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 taskWhen a sales opportunity is saved, I need to know if it's a brand new opportunity or an update…+
When a sales opportunity is saved, I need to know if it's a brand new opportunity or an update to an existing one. Add a check to the flow that tells me if it's an insert or an update.
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 this opportunity automation goes live, I need to make sure it handles both new…+
Before this opportunity automation goes live, I need to make sure it handles both new opportunities and updates correctly. Build in a check to differentiate between an insert and an update, so we can apply the right logic for each scenario without errors.
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 new sales commission flow just doubled commissions for all updated opportunities, and the…+
Our new sales commission flow just doubled commissions for all updated opportunities.
Our new sales commission flow just doubled commissions for all updated opportunities, and the VP of Sales is demanding answers by end of day. I thought I had logic for new vs. updated records, but it's clearly not working. I can't tell the VP I'm guessing. How do I quickly verify if the flow is correctly identifying an insert versus an update, and what's the immediate fix to prevent further incorrect commission payouts?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe frequently run into issues where automations apply the wrong logic because they don't…+
Incorrectly applying logic for new vs. updated records is a recurring problem.
We frequently run into issues where automations apply the wrong logic because they don't correctly differentiate between a new record and an update. This wastes time and creates data integrity problems. What habit should I change to consistently ensure flows accurately check for isInsert or isUpdate, preventing these recurring errors?
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.