◆ Apache Airflow

Integrate Airflow with other systems

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 taskSet up a new connection to the Marketo API for the lead scoring workflow. Use the credentials…+
Set up a new connection to the Marketo API for the lead scoring workflow. Use the credentials provided in LastPass under 'Marketo Production API'.
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 acceptWe're integrating our customer feedback survey data from Qualtrics into our data warehouse.…+
We're integrating our customer feedback survey data from Qualtrics into our data warehouse. Design a robust workflow that handles Qualtrics' API rate limits, retries transient errors, and ensures data consistency even if the API sends duplicate records, so the analytics team has clean data.
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 HR system integration keeps failing when processing certain employee records, but only…+
The new integration with the HR system is failing on specific employee records.
The new HR system integration keeps failing when processing certain employee records, but only for employees hired before 2010. The error message is generic, and I suspect a schema mismatch or an encoding issue with legacy data. The HR team needs this data for payroll by tomorrow. I'm not sure if I should try to clean the data pre-ingestion or modify the target schema. What's the quickest, safest path forward to get this data flowing?
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 external data source, it becomes a multi-week saga of debugging…+
Integrating new data sources always takes longer and is more fragile than expected.
Every time we integrate a new external data source, it becomes a multi-week saga of debugging and unexpected data quirks, often leading to fragile pipelines. This makes us slow to respond to business needs. What habit should we change in our approach to new integrations to make them faster and more resilient from the start?
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 Apache Airflow'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.