◆ Salesforce

Design Salesforce integration patterns

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 taskConnect our marketing automation platform to our customer relationship management system so…+
Connect our marketing automation platform to our customer relationship management system so that new leads generated from our website forms are automatically created as Lead records in the system.
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 acceptDesign an integration between our customer relationship management system and our new ERP…+
Design an integration between our customer relationship management system and our new ERP system that ensures customer order data flows accurately into the customer relationship management system, updating the relevant Account and Opportunity records, so our sales reps have real-time visibility into order status without leaving the system.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur sales team is reporting that customer order statuses in our customer relationship…+
Sales is complaining that customer data from the ERP isn't always up-to-date in Salesforce, but the integration logs look fine.
Our sales team is reporting that customer order statuses in our customer relationship management system aren't always current, despite our integration with the ERP system running every hour. The integration logs show successful data transfers, and there are no obvious errors. I'm concerned there's a subtle data mapping issue or a timing conflict that's hard to trace. What's the most likely reason for this data discrepancy, and what's the first step I should take to pinpoint the root cause before our end-of-quarter push?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery time we integrate a new system with our customer relationship management platform, it…+
Every time we integrate a new system with Salesforce, it becomes a maintenance nightmare.
Every time we integrate a new system with our customer relationship management platform, it quickly becomes a maintenance nightmare, with constant data discrepancies or broken connections, wasting my team's time. We're losing credibility with the business. What's one habit I should change in our approach to designing new integrations to ensure they are robust, reliable, and minimize future maintenance headaches?
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.