@awesomate/hosting-mcp/skill/awesomate-app-builder/references/solutions.md

Awesomate MCP server — lets Claude manage your Awesomate WordPress hosting, plan, limits, n8n automations, and build Node/static apps + databases

# Solutions — the recipes the greeter offers from

Business-outcome recipes, each composed only of parts that exist. Lead with
the outcome, never the technology. Reads work on every plan; **every build
below needs Support Plus+** — say so once, honestly, before starting (a 403
on a write is the plan gate; offer the upgrade, don't retry). Anything that
sends email needs an email credential in THEIR n8n — check the inventory
(`awesomate_n8n_inspect {what:'credentials'}`) before promising it.

## capture-leads-and-follow-up

**What you get:** every enquiry on your website lands in your inbox and on a
list — answered the same day, never lost, never duplicated.
**Made of:** a WP page or `static-landing` page with a form → server-side
forwarder → n8n webhook workflow that emails the owner, saves the lead to a
data table (deduped by email), and optionally sends the lead an instant reply.
**Needs:** Support Plus+. Email credential (existing Gmail, or SMTP/Resend
key). WP wiring per awesomate-n8n `references/wp-form-handler.md`.
**Build order:**
1. awesomate-n8n — webhook workflow + lead data table; test with fake payloads.
2. awesomate-credentials — email key if none exists (routes to n8n).
3. awesomate-app-builder (static page) or awesomate-hosting (WP page) — form +
   forwarder per wp-form-handler.md; verify both hops end-to-end.
4. awesomate-seo — the page is public.

## take-bookings

**What you get:** customers pick a time on your site; it lands in your
calendar with a confirmation email to both of you — no double bookings.
**Made of:** WP/static page with a booking form → forwarder → n8n webhook
workflow: check a slots data table (double-booking guard) → create the
calendar event → send confirmations.
**Needs:** Support Plus+. Google Calendar credential + email credential in
their n8n (guided OAuth if missing).
**Build order:**
1. awesomate-n8n — workflow + slots data table; test slot-taken and happy path.
2. awesomate-credentials — calendar/email credentials (routes to n8n).
3. awesomate-app-builder or awesomate-hosting — booking page + forwarder.
4. awesomate-seo — the page is public.

## customer-database-plus-simple-portal

**What you get:** one place holding all your customers, and a login page
where each customer sees their own details.
**Made of:** Node app (`node-auth-sync` — signup/login built in) + its own
app database (`awesomate_app_provision_db` — one Postgres per env,
`DATABASE_URL` injected). Customer data lives in the app DB, never a data
table. Optional n8n workflow for "new customer" email alerts.
**Needs:** Support Plus+ (app building). No external credential to start;
email credential only if alerts are wanted.
**Build order:**
1. awesomate-app-builder — confirm name + stack, `awesomate_app_create`,
   scaffold, build on dev; awesomate-github backup immediately after scaffold.
2. awesomate-credentials — any secrets the app needs (encrypted, injected).
3. awesomate-n8n — optional alert workflow called from the app.
4. Promote dev → live only on explicit approval; awesomate-seo if public.

## quote-or-invoice-follow-up

**What you get:** quotes and invoices that go quiet get a polite chaser
automatically — you stop leaving money on the table.
**Made of:** n8n scheduled workflow + data table holding each quote's status
and last-chase date (the cursor + dedupe) + email credential. Source of
quotes: a data table the owner updates, or an already-connected app from the
credential inventory — verify, never assume a credential works.
**Needs:** Support Plus+. Email credential. No page required.
**Build order:**
1. awesomate-n8n — quotes data table + scheduled chaser workflow.
2. awesomate-credentials — email key if none exists.
3. Test with fake quotes ([TEST] subjects to the owner's own inbox); hand
   over the workflow URL and how to add/close a quote.

## newsletter-signup

**What you get:** a signup box on your site that builds a clean subscriber
list and sends each new subscriber a welcome email.
**Made of:** WP/static page with a signup form → forwarder → n8n webhook
workflow → subscriber data table (deduped by email) + welcome email.
**Needs:** Support Plus+. Email credential.
**Build order:**
1. awesomate-n8n — webhook workflow + subscriber data table.
2. awesomate-credentials — email key if none exists.
3. awesomate-app-builder or awesomate-hosting — signup form + forwarder
   (wp-form-handler.md); verify a test signup lands once, not twice.
4. awesomate-seo — the page is public.

## ai-chat-on-your-site

**What you get:** a chat bubble on your site that answers customer questions
about your business, day and night.
**Made of:** n8n chat agent (chatTrigger `mode:"webhook"` → agent + model
credential — awesomate-n8n `references/ai-agents.md`, incl. the chat widget
embed) + the embed snippet on their WP or static page. Optional data table
for FAQs the agent looks up.
**Needs:** Support Plus+. A model credential (OpenRouter/OpenAI/Anthropic)
in their n8n — none = stop and ask, never invent one.
**Build order:**
1. awesomate-n8n — agent workflow per ai-agents.md; test conversations first.
2. awesomate-credentials — model API key if none exists (routes to n8n).
3. awesomate-app-builder or awesomate-hosting — embed the widget on the page.
4. Try it together on the live page; agree what the agent must NOT answer.

## order-status-notifications

**What you get:** customers hear from you automatically the moment their
order is received, shipped, or delayed — fewer "where's my order?" emails.
**Made of:** n8n webhook workflow fed by their shop (WooCommerce webhook,
server-to-server) or their own Node app → status-ledger data table (dedupe:
one notification per order per status) → email to the customer.
**Needs:** Support Plus+. Email credential. A shop or app that emits order
events — if neither exists yet, this recipe comes after the shop does.
**Build order:**
1. awesomate-n8n — webhook workflow + status data table; test every status.
2. awesomate-credentials — email key if none exists.
3. awesomate-hosting — point the WooCommerce webhook at the workflow (or
   wire the app's order code to call it).
4. Confirm a real test order notifies exactly once per status change.

## Offering these

After understanding the business (first-run questions + inventory), offer
the **2–3 most relevant recipes** as a one-line menu — "I could set up A, B,
or C — which sounds most useful?" Never list all seven, never lead with the
technology, and state the plan requirement before building. If none fit,
ask one more short question instead of forcing a recipe.