Build your own Zapier.

# Build an original app inspired by Zapier

You are an experienced product designer and full-stack engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Web. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original automation workbench called Flowbridge, inspired by Zapier. A small team configures a webhook trigger, maps fields into a few approved actions, tests the workflow, and inspects real run results. Start with three allowlisted connector types and linear workflows, not a general-purpose platform with arbitrary code execution.

## Design
Use an original trigger-to-action editor with a step list, field-mapping inspector, test sample, publish review, and a run-history timeline. Clearly distinguish draft versus published workflow versions, test data versus live events, and queued/running/succeeded/failed steps.

## Features
1. Workflow versions: create draft linear workflows with one trigger, up to three actions, validated field mappings, and an explicit publish/disable operation. Freeze the version used for each run.

2. Triggers: accept authenticated or signed webhook events with body limits, timestamps, rate limits, and event IDs for deduplication. Store the event before acknowledging and give users a way to rotate or revoke the endpoint secret.

3. Approved actions: implement three documented adapters such as creating an internal task, sending to a configured email sandbox, and posting to a fixed approved webhook destination. Store connector credentials encrypted and never allow arbitrary destination URLs or shell snippets.

4. Durable execution: queue runs, persist each step, retry transient failures with bounded backoff, and use idempotency keys or an explicit uncertain-outcome state. Promise at-least-once execution rather than unprovable exactly-once external side effects.

5. Testing and history: dry-run mappings with redacted sample data, inspect step inputs/outputs safely, replay only with explicit confirmation and documented side-effect semantics, and retain logs for a bounded period.

## Tech stack
Use a TypeScript workflow editor, Python or TypeScript API/worker, PostgreSQL, and a durable queue. Implement a typed connector registry and per-workspace credentials. Isolate outbound networking, reject private/reserved addresses at resolution and redirects, and enforce host allowlists. Do not evaluate user expressions as code.

## Data & behavior
Workspace; Membership; ConnectorCredential {encrypted}; Workflow; WorkflowVersion {steps, mappings}; TriggerEndpoint {secretHash}; TriggerEvent {externalId}; Run {versionId, state}; StepRun {attempt, idempotencyKey, outcome}; RetryJob; AuditEvent. Redact secrets and minimize payload retention.

Acceptance checks and scope:
Test duplicate webhooks, disabled workflows, mapping errors, a worker crash after an external side effect, bounded retries, revoked credentials, cross-workspace access, and blocked internal-network destinations. Exclude arbitrary code nodes, thousands of integrations, unrestricted outbound fetches, unattended financial actions, and exactly-once guarantees.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.