Skip to content

Latest commit

 

History

History
61 lines (42 loc) · 1.6 KB

File metadata and controls

61 lines (42 loc) · 1.6 KB

HubSpot Credentials Update - Instructions

New HubSpot Credentials

Access Token: pat-na1-a5d53194-3c15-48c5-a32e-ee5a493fd521 Client Secret: e3d8b2c2-218f-46c6-acd1-80e20094c3f0

Environment Variable Updates

Update your .env file with the new credentials:

# HubSpot Integration - Updated Credentials
HUBSPOT_PRIVATE_APP_TOKEN=pat-na1-a5d53194-3c15-48c5-a32e-ee5a493fd521
HUBSPOT_CLIENT_SECRET=e3d8b2c2-218f-46c6-acd1-80e20094c3f0
HUBSPOT_BASE_URL=https://api.hubapi.com
WSA_YEAR=2026

Production Environment Variables

For production deployment (Netlify/Vercel), set these environment variables:

HUBSPOT_PRIVATE_APP_TOKEN=pat-na1-a5d53194-3c15-48c5-a32e-ee5a493fd521
HUBSPOT_CLIENT_SECRET=e3d8b2c2-218f-46c6-acd1-80e20094c3f0
HUBSPOT_BASE_URL=https://api.hubapi.com
WSA_YEAR=2026

Testing the New Credentials

Run the test script to verify the new credentials work:

node scripts/test-hubspot-new-credentials.js

What Changed

  1. Access Token: Updated from old token to pat-na1-a5d53194-3c15-48c5-a32e-ee5a493fd521
  2. Client Secret: Added new client secret e3d8b2c2-218f-46c6-acd1-80e20094c3f0
  3. Region: Token indicates NA1 region (North America)

Verification Steps

  1. Update environment variables
  2. Run the test script
  3. Check HubSpot connection in admin panel
  4. Test a nomination submission to verify sync
  5. Test a vote to verify voter sync

Rollback Plan

If issues occur, you can temporarily disable HubSpot sync by setting:

HUBSPOT_PRIVATE_APP_TOKEN=""

The application will continue to work without HubSpot integration.