◆ Salesforce

Perform HTTP callout from triggers

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 taskWhen an Opportunity Stage changes to 'Closed Won', make an HTTP callout to our external…+
When an Opportunity Stage changes to 'Closed Won', make an HTTP callout to our external invoicing system to create a new invoice record, passing the Opportunity ID and Amount.
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 we go live with the invoicing integration, ensure the HTTP callout includes robust error…+
Before we go live with the invoicing integration, ensure the HTTP callout includes robust error handling. If the external system is down or returns an error, log the failure, notify the sales operations team, and implement a retry mechanism for the callout, so no 'Closed Won' opportunities are missed for invoicing.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentFinance just called, frantic, saying that several 'Closed Won' opportunities from yesterday…+
Finance just called, frantic, saying that several 'Closed Won' opportunities from yesterday haven't appeared in the invoicing system.
Finance just called, frantic, saying that several 'Closed Won' opportunities from yesterday haven't appeared in the invoicing system. I'm afraid the HTTP callout from the trigger might have failed silently, or hit a governor limit. I don't know how to quickly check the status of those specific callouts or what went wrong without potentially overwhelming the system. What's the best way to diagnose these missed callouts and ensure they're processed without manual intervention?
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 worried that external system integrations triggered by record changes are…+
I'm constantly worried that external system integrations triggered by record changes are failing without anyone knowing.
I'm constantly worried that external system integrations triggered by record changes are failing without anyone knowing, leading to data discrepancies and angry calls from other departments. I usually just hope for the best. What habit should I change to proactively monitor the success and failure of these critical HTTP callouts, so I can catch issues before they become crises and ensure data integrity across systems?
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.