◆ Salesforce

Call Salesforce API from Apex

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 the account name and all open opportunities for the 'Acme Corp' account using the…+
Get the account name and all open opportunities for the 'Acme Corp' account using the Salesforce API. I need the account ID and the opportunity IDs, names, stages, and amounts. Put this in a list for me to use in the email.
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 start coding this API call, help me make sure it's robust. What are the common error…+
Before I start coding this API call, help me make sure it's robust. What are the common error conditions for querying account and opportunity data, and how should I handle them gracefully so the user doesn't see a broken page?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe API call to fetch open opportunities for 'Global Solutions' is timing out, but it works for…+
The API call to get opportunity data just started timing out for a specific large account.
The API call to fetch open opportunities for 'Global Solutions' is timing out, but it works for smaller accounts. I'm afraid to deploy a fix that might break other parts of the system or introduce a new performance bottleneck. Is this likely a data volume issue, a governor limit, or something else entirely? What's the safest next step to diagnose without impacting 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'm constantly running into governor limits or unexpected data volumes causing API calls to…+
I keep hitting governor limits or unexpected data volumes when making API calls.
I'm constantly running into governor limits or unexpected data volumes causing API calls to fail for larger clients, leading to last-minute rewrites and missed deadlines. What habit should I change to anticipate these issues earlier in the development cycle, especially when dealing with data retrieval for complex reports or integrations?
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.