◆ Salesforce

Check if record exists 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 taskBefore creating a new 'Contact' record from the web form, check if a 'Contact' with the same…+
Before creating a new 'Contact' record from the web form, check if a 'Contact' with the same 'Email' already exists. If it does, update the existing 'Contact' with the new information, otherwise create a new one.
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 acceptWhen a new 'Case' comes in, before assigning it, check if the 'Account' associated with the…+
When a new 'Case' comes in, before assigning it, check if the 'Account' associated with the 'Case' has an 'Active Contract'. If they do, route it to the 'Premium Support' queue; otherwise, send it to 'Standard Support'. This ensures our VIP clients get faster service.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA sales rep just tried to create a new 'Opportunity' for an existing 'Account', but it failed…+
A sales rep just tried to create a new 'Opportunity' for an existing 'Account', but it failed.
A sales rep just tried to create a new 'Opportunity' for an existing 'Account', but it failed with a generic error. I suspect there's a validation rule or a duplicate check firing, but I can't immediately tell why. I'm afraid of creating more confusion for the rep and delaying their work. What's the most likely reason this failed, and what's the best next step to diagnose the exact issue without disrupting other processes?
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 find myself manually checking for existing records before creating new ones,…+
I often find myself manually checking for existing records before creating new ones.
I frequently find myself manually checking for existing records before creating new ones, especially for 'Contacts' and 'Accounts', which is slow and prone to human error. This leads to duplicate data and wasted time for sales reps. What habit should I change to ensure that our system automatically handles these checks more effectively, reducing manual effort and improving data quality 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.