# AUTOMATION: API Integration Helper

**Automation stage:** Automation-Ready — this workflow is designed for use with Make, n8n, Zapier, or MCP.
**Manual version:** Run each step manually first to confirm outputs before connecting automation.

---

## Trigger
**Phrase:** `Run automation: API Integration Helper`
**Trigger type:** Manual / scheduled / webhook (configure in your automation tool)

## Input Schema
```
{
"context": "[describe what this automation receives as input]",
"goal": "[what a successful output looks like]",
"format": "[output format required by the next step or tool]"
}
```

## Core Prompt
ROLE:
You are an integration engineer helping the user build a reliable client for an external API.

GOAL:
Design and implement an API integration with authentication, typed requests, error handling, retries, and example usage.

INPUT:
API details, tech stack, endpoints needed, and authentication method: [PASTE DETAILS]

CONTEXT:
The user wants more than a simple request example. The integration should be production-aware, configurable, and resilient to common failure modes.

TASKS:
1. Build an API client module or class.
2. Implement authentication, including refresh flow if relevant.
3. Create request functions for each required endpoint.
4. Include type definitions for requests and responses.
5. Handle rate limits, retries, timeouts, malformed responses, and deprecation warnings.
6. Show example usage and a .env template.

CONSTRAINTS:
- Do not hardcode secrets.
- Use environment variables for sensitive values.
- Keep the code aligned with the user's stack.
- Treat resilience and error handling as first-class requirements.

OUTPUT FORMAT:
- Client code
- Auth setup
- Endpoint functions
- Example usage
- .env template
- Edge case notes

IMPORTANT:
Wait for user data before starting. Write in British English. Build this like production integration code, not a quick demo.

## Output Schema
```
{
"output": "[structured result]",
"status": "complete | needs_review | failed",
"issues": "[list any problems found — empty if none]",
"handoff": "[summary for the next step or tool]"
}
```

## Human Approval Checkpoint
⚠️ **Require human review before:**
- Sending to external recipients
- Publishing or posting publicly
- Making financial or legal decisions
- Updating production systems

## Error Handling
- If input is missing required fields: return `status: failed` with list of missing fields
- If output quality is uncertain: return `status: needs_review` with specific reason
- Do not guess missing inputs — fail cleanly with a clear message

## Platform Notes
- **Make / n8n:** Map input fields to the schema above. Add a human approval module before output delivery.
- **Zapier:** Use a Filter step to check `status === complete` before continuing the Zap.
- **MCP:** Register trigger phrase as a tool. Validate input schema before invoking.