◆ JavaScript

Create a workflow automation

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 JavaScript tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskI need to automate the process of sending a welcome email to new users. When a new user signs…+
I need to automate the process of sending a welcome email to new users. When a new user signs up, trigger an email to their registered address using the welcome email template.
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 deploy the new user onboarding workflow, make sure it's robust. If the email service…+
Before I deploy the new user onboarding workflow, make sure it's robust. If the email service fails, it should retry sending the welcome email a few times before logging an error. Also, add a check to ensure the user hasn't already received a welcome email to prevent duplicates.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentSome new users aren't getting their welcome emails, and the marketing team is pressing for a…+
The marketing team just reported that some new users aren't receiving their welcome emails, and we have no visibility into why or how many.
Some new users aren't getting their welcome emails, and the marketing team is pressing for a fix. I'm afraid this is causing early churn, and I don't have good logging to diagnose the failure points. I'm unsure if it's a transient email service issue, a bug in the user creation hook, or something else. What's the fastest way to diagnose why emails are failing and implement a temporary retry mechanism while I investigate the root cause?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often build automated workflows, like email triggers or data syncs, without sufficiently…+
I frequently build automated workflows without adequate error handling or observability, leading to silent failures that impact users and business operations.
I often build automated workflows, like email triggers or data syncs, without sufficiently robust error handling, retries, or clear logging. This leads to silent failures that only surface when a user complains or a business metric drops. What habit should I change to consistently incorporate comprehensive error handling, retry logic, and clear monitoring from the start, especially when a workflow relies on external services?
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 JavaScript'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.