◆ Salesforce

Get records using Flow with ID collection

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 taskGet all the contact records associated with the 'Acme Corp' account. I need their IDs in a list…+
Get all the contact records associated with the 'Acme Corp' account. I need their IDs in a list so I can update their 'Marketing Opt-Out' field to true before Friday's email blast.
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 run this, ensure the flow collects the IDs efficiently. If the account has thousands…+
Before I run this, ensure the flow collects the IDs efficiently. If the account has thousands of contacts, I don't want it to time out or hit governor limits. Make sure it's robust enough for any account size.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI was trying to get all contact IDs for 'Global Enterprises' to update their 'Last Contact…+
I just tried to collect IDs for a large account and the flow failed with a 'too many SOQL queries' error.
I was trying to get all contact IDs for 'Global Enterprises' to update their 'Last Contact Date', but the flow just blew up. It's a massive account, and I'm worried about hitting limits again. What's the best way to collect these IDs without crashing, and what's the fastest way to fix this before my 3 PM deadline?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep running into SOQL query limits when building flows to collect record IDs for bulk…+
My flows for collecting record IDs frequently fail on larger accounts, costing me time and rework.
I keep running into SOQL query limits when building flows to collect record IDs for bulk updates, especially with our biggest clients. This forces me to rebuild or split the logic, wasting hours. What habit should I change in how I approach ID collection to make my flows reliable for any data volume?
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.