◆ Salesforce

Use Apex-defined data type 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 taskIn the 'Order Fulfillment' flow, create an Apex-defined data type named 'FulfillmentRequest' to…+
In the 'Order Fulfillment' flow, create an Apex-defined data type named 'FulfillmentRequest' to represent the order items, quantities, and delivery address, so the flow can process complex orders efficiently.
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 the 'Invoice Generation' flow goes live, ensure the Apex-defined data type for…+
Before the 'Invoice Generation' flow goes live, ensure the Apex-defined data type for 'InvoiceLineItem' includes fields for 'Product SKU', 'Unit Price', and 'Discount Applied', so the flow generates accurate and detailed invoices for the finance team.
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 new 'Supply Chain Integration' flow needs to send a list of 'Product Shipment Details' –…+
I need to pass a list of complex data to an external system from a flow, but standard variables aren't enough.
The new 'Supply Chain Integration' flow needs to send a list of 'Product Shipment Details' – including product ID, quantity, and warehouse location – to an external system. Using individual variables for each item is getting unmanageable, and I can't seem to structure the data correctly for the external API. I'm worried it will lead to malformed requests and data errors. What's the best next move to define and pass this complex list of data from the flow to the external system reliably?
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 encounter situations where flows need to process or send complex, structured data,…+
I often struggle to handle complex data structures within flows, especially when integrating with external systems.
I frequently encounter situations where flows need to process or send complex, structured data, like a list of items with multiple attributes, to external systems or other Apex actions. I often resort to workarounds that make the flow hard to read and maintain. What habit should I change to consistently and effectively manage complex data types within my flows, making them more robust and easier to debug?
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.