NanoSeal NB
Surface Intelligence
Demo environment. Admin/sales access only.
Internal setup guide. Do not expose secrets in client-side code.

CRM Integration Setup

NanoSeal NB Surface Intelligence can route leads to external systems using environment variables.

Top priority: Teams email connector

The first live routing target is a Microsoft Teams channel email connector. Set the destination email in your Vercel environment variables to send plain-text lead notifications directly to your Sales channel.

How it works

  1. 1. Get Teams channel email address (Channel options > Get email address)
  2. 2. Set LEAD_NOTIFICATION_EMAIL_TO to that address in Vercel
  3. 3. Set LEAD_NOTIFICATION_EMAIL_FROM (e.g. leads@nanosealnb.ca)
  4. 4. Set RESEND_API_KEY or configure SMTP env vars
  5. 5. Redeploy → visit /notification-test to send a safe test lead

Email notification environment variables

These env vars control where and how lead notifications are emailed. All optional — the app works without them.

LEAD_NOTIFICATION_EMAIL_TO

Destination email (use your Teams channel email connector address)

LEAD_NOTIFICATION_EMAIL_FROM

Sender email (defaults to leads@nanosealnb.ca)

RESEND_API_KEY

Resend API key for email sending (recommended over SMTP)

SMTP_HOST

SMTP server hostname

SMTP_PORT

SMTP server port (e.g. 587)

SMTP_USER

SMTP username

SMTP_PASS

SMTP password

SMTP_SECURE

Set to "true" for SSL port 465, omit for STARTTLS on port 587

Security warning: Do not commit Teams channel email addresses, SMTP passwords, or API keys to GitHub. Use Vercel environment variables only.

Lead payload structure (for webhooks)

Each webhook receives a JSON object with these fields:

{
  "name": "string",
  "email": "string",
  "phone": "string",
  "company": "string",
  "role": "string",
  "organizationType": "string",
  "leadType": "string",
  "source": "string",
  "interest": "string",
  "urgency": "string",
  "pilotInterest": "string",
  "portfolioSize": "string",
  "budgetRange": "string",
  "region": "string",
  "cities": "string",
  "surfaceConcerns": ["string"],
  "message": "string",
  "selectedPackage": "string",
  "leadScore": 0,
  "leadQuality": "string",
  "recommendedFollowUp": "string",
  "utmSource": "string",
  "utmMedium": "string",
  "utmCampaign": "string",
  "capturedAt": "ISO timestamp",
  "source": "building-passport",
  "environment": "production"
}

Setup checklist

  1. 1Get your Teams channel email address (Channel options > Get email address)
  2. 2Set LEAD_NOTIFICATION_EMAIL_TO in Vercel project environment variables
  3. 3Set LEAD_NOTIFICATION_EMAIL_FROM (e.g. leads@nanosealnb.ca)
  4. 4Set RESEND_API_KEY or configure SMTP_* env vars
  5. 5Redeploy the project on Vercel
  6. 6Visit /notification-test and send a safe test lead
  7. 7Confirm the Teams channel receives the lead notification
  8. 8Leads also appear in /leads-demo regardless of email config

Test your routing

Send a test lead through the notification pipeline to verify Teams email delivery.

Future routing targets

Additional webhook integrations are planned but scoped as future work until NanoSeal NB creates a dedicated Surface Intelligence pipeline in each platform.

GHL_WEBHOOK_URL

GoHighLevel pipeline routing — future work

TEAMS_WEBHOOK_URL

Teams adaptive card webhook — future work (email connector is the current Teams integration)

LEAD_WEBHOOK_URL

Generic webhook for Zapier, Make, n8n, or custom endpoints — future work