Can I vibe code ChannelReply?

Build a Node.js and TypeScript microservice that acts as a middleware relay between seller marketplace APIs (Etsy API v3, eBay Trading API) and a helpdesk system (Gorgias REST API).

1. DATA MODEL:
Create a PostgreSQL schema to manage:
- Marketplace Accounts: store account_id, platform ('ebay', 'etsy'), refresh_token, access_token, token_expires_at.
- Ticket Mappings: store helpdesk_ticket_id, marketplace_platform, marketplace_thread_id, buyer_id, order_id, last_synced_at.
- Message Logs: payload history for debugging.

2. CORE FUNCTIONALITY:
- Webhook Listener / Poller: Ingest inbound buyer messages from Etsy and eBay endpoints.
- Data Normalizer: Standardize raw marketplace payloads into a uniform structure: sender_name, buyer_email_or_id, message_body, marketplace_order_id, platform_type.
- Ticket Creator: Check if a thread mapping exists for the given marketplace_thread_id. If not, call Gorgias POST /api/tickets to create a new ticket with custom fields (Marketplace, Order ID, Tracking Number). If existing, append the message via Gorgias POST /api/tickets/{id}/messages.
- Outbound Relay: Set up a HTTP webhook endpoint targetable by Gorgias outbound integrations. When an agent replies in Gorgias, intercept the webhook payload, look up the marketplace_thread_id, and execute the correct REST request to the respective marketplace's reply API.

3. FAILURE MODES & EDGE CASES:
- Token Expiration: Implement automatic token refresh logic prior to executing any marketplace API call.
- Rate Limiting: Implement exponential backoff queues using BullMQ and Redis for outbound marketplace API calls.
- Format Cleaning: Strip HTML tags and normalize plain text to prevent formatting bugs on marketplace buyer portals.

4. OUT OF SCOPE:
- Amazon SP-API integration (do not attempt Amazon due to PII compliance rules).
- Multi-tenant billing UI.

$ each button prefixes agent-specific run instructions · build your own product, never copy proprietary code, trademarks or designs