◆ Salesforce

Expose package code via 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 taskCreate a flow action that calls the 'calculateDiscount' Apex method from the 'PricingEngine'…+
Create a flow action that calls the 'calculateDiscount' Apex method from the 'PricingEngine' package, passing the Opportunity ID and Product Family, so we can display the custom discount on the opportunity page. Have it ready for testing by Friday.
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 acceptWe need to integrate our new external credit check service into the 'New Account Creation'…+
We need to integrate our new external credit check service into the 'New Account Creation' flow. Can you build a flow that calls the Apex method 'CreditCheckService.runCheck' with the account details, processes the response, and then updates the 'Credit Status' field on the account, all while handling potential API errors gracefully?
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 flow that calls our custom 'OrderFulfillment' Apex method is intermittently failing, but…+
The flow that calls our custom 'OrderFulfillment' Apex method is intermittently failing, but only for certain product types.
The flow that calls our custom 'OrderFulfillment' Apex method is intermittently failing, but only for certain product types. It's not a consistent error, and the Apex code itself seems fine when run in isolation. I suspect it's how the flow is passing parameters or handling the response under specific conditions, but I can't replicate it reliably. Our fulfillment team is blocked. What's the quickest way to debug this interaction between the flow and the Apex, especially given the intermittent nature?
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 face issues where flows calling Apex methods fail due to incorrect parameter…+
I frequently face issues where flows calling Apex methods fail due to incorrect parameter mapping or unhandled exceptions.
I frequently face issues where flows calling Apex methods fail due to incorrect parameter mapping or unhandled exceptions, leading to production incidents and rework. It feels like a recurring blind spot. What habit should I change in how I design, build, or test flows that interact with custom Apex code to prevent these integration failures before they impact users?
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.