◆ Salesforce

Get IDs of records created 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 taskAfter the 'New Account Creation' Flow successfully creates an Account record, get the ID of…+
After the 'New Account Creation' Flow successfully creates an Account record, get the ID of that newly created account and store it in a variable named 'newAccountId'.
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 acceptThe 'Opportunity Conversion' Flow needs to do more than just create a new Opportunity. Once the…+
The 'Opportunity Conversion' Flow needs to do more than just create a new Opportunity. Once the Opportunity is created, I need to immediately get its ID, then use that ID to create two related 'Activity' records for follow-up tasks, assigning them to the opportunity owner, all within the same Flow, before the user sees the confirmation screen.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMy 'Project Onboarding' Flow creates a new Project record and then several 'Task' records…+
The 'Project Onboarding' Flow is creating records, but I can't link them together correctly.
My 'Project Onboarding' Flow creates a new Project record and then several 'Task' records related to it. The problem is, sometimes the Tasks aren't correctly linked to the new Project, or they're linked to the wrong one. I'm afraid of data silos. I suspect I'm not reliably getting the ID of the *just-created* Project before trying to create the Tasks. What's the most reliable way to ensure I capture the correct ID of the newly created Project record so all subsequent Tasks are correctly associated, and how can I quickly verify this without deploying to production?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often find myself debugging Flows where records are created but not correctly associated with…+
I frequently struggle with ensuring newly created records are correctly linked in Flows.
I often find myself debugging Flows where records are created but not correctly associated with each other, leading to broken relationships. This costs me a lot of time and creates data quality issues. What's a better habit I can adopt in my Flow design process to consistently and reliably capture and utilize the IDs of newly created records, ensuring proper data linkage every time?
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.