← All documents  ·  Download PDF

09 · Making changes after handoff (via Bento / an AI assistant)

How to connect an MCP-capable AI assistant ("Bento") to the NIE systems so you can safely make changes after handoff — edit the automation flows, the website code, the database, and the CRM. Written tool-generically: the URLs/keys below apply whatever the assistant; the exact "add a connector" screen is Bento-specific.

What you connect (and what it lets you change)

1. n8n — the automation flows

• Instance: https://n8n.nieexpertsspain.com
• Get an API key: n8n → Settings → n8n API → Create an API key. Copy it (shown once).
• Connect (MCP config example):

{
  "mcpServers": {
    "n8n-mcp": {
      "command": "npx",
      "args": ["n8n-mcp"],
      "env": {
        "N8N_API_URL": "https://n8n.nieexpertsspain.com",
        "N8N_API_KEY": "<your n8n API key>"
      }
    }
  }
}

• Now the assistant can list workflows, read a flow's structure, edit nodes, validate, and activate/deactivate. Flow reference: 03-flow-catalog.md.
• Safe practice: duplicate a flow (or test it) before changing a live one; the MCP can validate before you activate. Snapshot the workflow JSON first so you can restore.

2. Website code — the GitHub repo

• Repo (private): https://github.com/nieexpertsspain/nie-experts-site
• Connect: give Bento's GitHub connector access to that repo (or use a GitHub Personal Access Token with repo scope, or the gh CLI signed into the nieexpertsspain org).
• Deploy model: Vercel auto-deploys on push to main (project nie-experts-site, team Node AI). So the change workflow is:
  1. branch → make the change → open a PR → review → merge to main → Vercel deploys automatically.
  2. Verify the deployment is Ready in Vercel.
• Never commit secrets. All keys live in Vercel → Settings → Environment Variables (and in n8n's own credentials), never in git. Env reference: 06-env-secrets.md.

3. Supabase — the database

• Project ref: kbmvtawsdhmzjnsonazr (region eu-west-1).
• Connect: the Supabase MCP (OAuth), or a Personal Access Token created at https://supabase.com/dashboard/account/tokens.
• Lets the assistant read the schema, run read queries, and (carefully) DDL. Schema reference: 01-data-model.md.
• Schema changes go through migrations: add a timestamped file in supabase/migrations/ (e.g. 20260701120000_<name>.sql) so the change is tracked and reproducible — see the D2 RLS migration as a template.

4. Notion — the CRM

• Database: "NIE Website Orders" (id 36dfd253-5094-80ae-83e3-fdd8a10425c4).
• Connect: create an internal integration at https://www.notion.so/my-integrations, copy its token, then share the database with that integration (Notion → the DB → ⋯ → Connections → add it).
• Lets the assistant read/update the orders board (Tier, Stato Pratica, etc.). Mapping: 04-integrations.md.

The safe change workflow (always)

1. Stay in test mode until a deliberate go-live. The whole system keys off the Stripe sk_test_/sk_live_ prefix — see 07-go-live-checklist.md. Don't touch live Stripe keys for routine changes.
2. Code: branch → change → PR → merge to main → auto-deploy → verify. Small, reviewable commits.
3. n8n: validate + test a flow before activating; snapshot before editing a live one.
4. DB: never edit data blindly; schema changes as migrations.
5. Secrets: generate/rotate at the source (provider dashboard) and set them in Vercel/n8n env — never in git or chat.
6. When unsure what a piece does, read the matching doc in this set first (00–08, AUDIT-FINDINGS).

Where to generate each credential

Guardrails recap

• Deploys are automatic on main — treat main as production.
• Site stays in Stripe test mode until go-live (07).
• Rotate any key that's ever been shared; keys live in env, not git.
• Open items / known issues to be aware of before changing things: AUDIT-FINDINGS.md.