◆ Salesforce

Manage multiple workflow/flow/process builders

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 taskDeactivate the 'Auto-Assign Support Case' workflow rule that was created last…+
Deactivate the 'Auto-Assign Support Case' workflow rule that was created last year.
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 activate the new 'Lead Qualification' flow, analyze its interactions with the existing…+
Before I activate the new 'Lead Qualification' flow, analyze its interactions with the existing 'New Lead Assignment' process builder. Identify any potential conflicts, infinite loops, or unintended overwrites, and suggest the most efficient way to consolidate or reorder them.
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 need to activate the 'Opportunity Stage Update' flow by Friday, but there are two old…+
A new automation needs to go live, but it overlaps with old ones.
I need to activate the 'Opportunity Stage Update' flow by Friday, but there are two old workflow rules and a process builder that also touch opportunity stages. I'm afraid of creating duplicate actions or breaking existing logic. What's the best approach to ensure a smooth transition without disrupting current processes, and what should I disable first?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur instance has become a spaghetti of old workflow rules, process builders, and new flows,…+
Our org's automation is a tangled mess, making changes risky and slow.
Our instance has become a spaghetti of old workflow rules, process builders, and new flows, making any change a high-risk operation. I spend too much time untangling dependencies and fixing unintended consequences. What habit should I change in how I approach new automation requests to prevent this complexity from spiraling further?
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.