Workato

Build me a focused enterprise automation workflow for the personal core of Workato. Requirements:

- Use exactly this stack: Next.js 15 + TypeScript + PostgreSQL + BullMQ. Model workflows, triggers, step executions, retries, and external receipts; keep stable source IDs and timestamps.
- Paid product context: Enterprise integration, workflow automation, governance, and connectors. Build only this DIY scope: Build one explicit enterprise automation workflow with a trigger, validated steps, retries, logs, and a manual replay button.
- For enterprise automation, define trigger, input schema, steps, outputs, and an idempotency key.
- Execute one supported connection path and persist each step result before advancing.
- Show a run log, retry a failed step, and export a complete execution trace.
- Use a local web page with input, progress, review, and export views. Required input or access: hosted PostgreSQL and Redis; API credentials for the two chosen services.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A retry after a provider timeout must not repeat a completed external action without an explicit reconciliation step.
- Out of scope: schema drift handling and enterprise controls; hundreds of maintained connectors. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for Workato

## Project scope
Build one explicit enterprise automation workflow with a trigger, validated steps, retries, logs, and a manual replay button.

Catalogue verdict: no. Do not mistake the interface for the product. Workato's durable value is connectors, auth, reliability, which a solo one-shot build cannot reproduce responsibly. The prompt therefore builds only the closest honest personal consolation tool.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- hosted PostgreSQL and Redis
- API credentials for the two chosen services
- Node.js 22
- Explicit README warning that this is a consolation build, not a production replacement

## Stack and architecture
- Use exactly this stack: Next.js 15 + TypeScript + PostgreSQL + BullMQ.
- Model workflows, triggers, step executions, retries, and external receipts; keep stable source IDs and timestamps.
- Interface for this enterprise automation workflow: a local web page with input, progress, review, and export views.

## Security and data integrity
- A retry after a provider timeout must not repeat a completed external action without an explicit reconciliation step.
- Validate imported records and file paths; keep user data within the storage location named in the prompt.
- State the practical limit: schema drift handling and enterprise controls.

## Agent implementation rules
- Project rule, data: Model workflows, triggers, step executions, retries, and external receipts; keep stable source IDs and timestamps.
- Project rule, behavior: For enterprise automation, define trigger, input schema, steps, outputs, and an idempotency key.
- Project rule, recovery: A retry after a provider timeout must not repeat a completed external action without an explicit reconciliation step.

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this enterprise automation operation with sample or user-owned data: For enterprise automation, define trigger, input schema, steps, outputs, and an idempotency key.
- Show a concrete result or export: Show a run log, retry a failed step, and export a complete execution trace.
- State the practical limit: schema drift handling and enterprise controls.

## Engineering roadmap
1. Phase 1, architecture and data: Use exactly this stack: Next.js 15 + TypeScript + PostgreSQL + BullMQ. Model workflows, triggers, step executions, retries, and external receipts; keep stable source IDs and timestamps.
2. Phase 2, implement: For enterprise automation, define trigger, input schema, steps, outputs, and an idempotency key.
3. Phase 3, implement: Execute one supported connection path and persist each step result before advancing.
4. Phase 4, review and output: Show a run log, retry a failed step, and export a complete execution trace.
5. Phase 5, recovery and acceptance: Verify this invariant with a saved fixture: A retry after a provider timeout must not repeat a completed external action without an explicit reconciliation step. State the practical limit: schema drift handling and enterprise controls.

## Paid-product capabilities outside this build
- schema drift handling and enterprise controls
- hundreds of maintained connectors
- OAuth app verification
- durable execution at scale

## Implementation prompt
Build me a focused enterprise automation workflow for the personal core of Workato. Requirements:

- Use exactly this stack: Next.js 15 + TypeScript + PostgreSQL + BullMQ. Model workflows, triggers, step executions, retries, and external receipts; keep stable source IDs and timestamps.
- Paid product context: Enterprise integration, workflow automation, governance, and connectors. Build only this DIY scope: Build one explicit enterprise automation workflow with a trigger, validated steps, retries, logs, and a manual replay button.
- For enterprise automation, define trigger, input schema, steps, outputs, and an idempotency key.
- Execute one supported connection path and persist each step result before advancing.
- Show a run log, retry a failed step, and export a complete execution trace.
- Use a local web page with input, progress, review, and export views. Required input or access: hosted PostgreSQL and Redis; API credentials for the two chosen services.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A retry after a provider timeout must not repeat a completed external action without an explicit reconciliation step.
- Out of scope: schema drift handling and enterprise controls; hundreds of maintained connectors. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.