HolyCRM

Setup

Core configuration OK

1 · Fill in .env.local

The file already exists in the project root. Add the values below, then restart npm run dev — Next.js only reads env files at startup.

Supabase

Required for the app to start at all.
  • NEXT_PUBLIC_SUPABASE_URL

    Supabase → Project Settings → API → Project URL

  • NEXT_PUBLIC_SUPABASE_ANON_KEY

    Same page → anon / public key

  • SUPABASE_SERVICE_ROLE_KEY

    Same page → service_role key. Server-side only.

Demo data

Printed by 0002_demo_seed.sql when you run it.
  • DEMO_ORG_ID

    The org id printed by 0002_demo_seed.sql

DeepSeek

Required for the AI bot. Not needed to browse the inbox.
  • DEEPSEEK_API_KEY

    platform.deepseek.com → API keys

Green API

Required to send and receive WhatsApp messages.
  • GREEN_API_BASE_URL

    Console → apiUrl, e.g. https://7107.api.greenapi.com (per-instance host)

  • GREEN_API_ID_INSTANCE

    Green API console → idInstance

  • GREEN_API_TOKEN

    Green API console → API token

  • GREEN_API_WEBHOOK_SECRET

    Any random string. Forms the webhook URL path.

  • GREEN_API_WEBHOOK_TOKEN

    Must match webhookUrlToken in the Green API console.

  • GREEN_API_OWN_JID

    e.g. 9665XXXXXXXX@c.us — used to detect @mentions in groups

2 · Run the migrations

Supabase SQL Editor, in order: 0001_hollycrm_init.sql, 0002_demo_seed.sql, 0003_storage_and_ops.sql.

3 · Create an agent profile

RLS returns nothing to a user with no row in profiles — see DEMO_RUNBOOK §2.2.