Spec a no-code automation

Turn a recurring manual task into a buildable no-code workflow spec with dedupe, retries and tests.

Run it as a prompt

Paste this into any AI agent, or fetch it: curl -s https://uplift.page/api/v1/prompts/no-code-automation-spec/raw

prompt.md

# Spec a no-code automation

Turn a recurring manual task into a step-by-step spec that someone can build in a no-code tool without writing code.

## Input
- The task as people do it today, with volume and frequency: [TASK DESCRIPTION]
- Preferred platform, or "any": [PLATFORM] (e.g. Zapier, Make, n8n, Power Automate)
- Apps involved: [APPS]

## Produce
1. Trigger: the exact event that starts a run, the fields it provides, validation rules, and one example record.
2. Steps: numbered actions with exact branch conditions (e.g. "if Priority equals Urgent go to step 5, else step 7"), lookups, and field transformations.
3. Duplicates: how each run marks an item as processed (e.g. a Processed At column or a stored ID) so retries and re-triggers never act twice.
4. Errors: retry policy (count and delay), what happens after a partial failure, and who is alerted, on which channel, with what message.
5. Outputs: a table mapping source field to destination field with an example value.
6. Connections: each app connection and the minimum permission it needs. Flag any step that needs an API call or webhook and give its request shape.
7. Test plan: 4-6 cases (normal, missing field, duplicate, upstream app down), with one sample input to paste into the platform's test run and the expected result.
8. Build checklist: ordered setup steps with effort (low / medium / high) and the monthly usage in the platform's billing unit (Zapier tasks, Make credits, n8n executions, Power Automate runs) at the stated volume.

## Rules
- No custom code. If a step truly needs code, say so and give the closest no-code alternative.
- Use a shared service account for connections where the platform allows it, not a personal login.
- Never put passwords or API keys in the spec; point to the platform's credential store.
- List assumptions separately.

## Output
A numbered spec with the 8 sections above, under 1,500 words.

The full prompt

Turn a recurring manual task into a step-by-step spec that someone can build in a no-code tool without writing code.

Input

The task as people do it today, with volume and frequency: [TASK DESCRIPTION]
Preferred platform, or "any": [PLATFORM] (e.g. Zapier, Make, n8n, Power Automate)
Apps involved: [APPS]

Produce

Trigger: the exact event that starts a run, the fields it provides, validation rules, and one example record.
Steps: numbered actions with exact branch conditions (e.g. "if Priority equals Urgent go to step 5, else step 7"), lookups, and field transformations.
Duplicates: how each run marks an item as processed (e.g. a Processed At column or a stored ID) so retries and re-triggers never act twice.
Errors: retry policy (count and delay), what happens after a partial failure, and who is alerted, on which channel, with what message.
Outputs: a table mapping source field to destination field with an example value.
Connections: each app connection and the minimum permission it needs. Flag any step that needs an API call or webhook and give its request shape.
Test plan: 4-6 cases (normal, missing field, duplicate, upstream app down), with one sample input to paste into the platform's test run and the expected result.
Build checklist: ordered setup steps with effort (low / medium / high) and the monthly usage in the platform's billing unit (Zapier tasks, Make credits, n8n executions, Power Automate runs) at the stated volume.

Rules

No custom code. If a step truly needs code, say so and give the closest no-code alternative.
Use a shared service account for connections where the platform allows it, not a personal login.
Never put passwords or API keys in the spec; point to the platform's credential store.
List assumptions separately.

Output

A numbered spec with the 8 sections above, under 1,500 words.

Served from the uplift.page library and refreshed within 5 minutes of every update.