Troubleshooting

​

Common Errors

​

Authentication Errors

​

401 Unauthorized

{
  "status": "error",
  "message": "This request requires authentication",
  "correlationId": "..."
}

1. Verify your access token is correctly set in events.js:2:
   const accessToken = "pat-na1-your-token-here";
   
2. Check that the token hasn’t expired. Generate a new token if needed:
   • Go to HubSpot Settings → Integrations → Private Apps
   • Create a new token or regenerate an existing one
3. Ensure the token has the required scopes:
   • crm.objects.deals.read
   • crm.objects.deals.write
   • crm.schemas.deals.read
   • marketing-events.read

​

403 Forbidden

{
  "status": "error",
  "message": "This app does not have permission to access this resource",
  "correlationId": "..."
}

1. Update your Private App scopes to include:
   • Marketing Events API read access
   • CRM Objects (Deals) read/write access
2. After updating scopes, the token may be regenerated automatically. Update your script with the new token.

​

Validation Errors

​

VALIDATION_ERROR: Duplicate Record

❌ Error creando record: {
  status: 'error',
  message: 'Property values were not valid: ...',
  category: 'VALIDATION_ERROR'
}

// Check if record exists by name to avoid VALIDATION_ERROR
const nameExists = await recordExistsByName(e.eventName);
if (nameExists) {
  skippedEvents.push({ name: e.eventName, reason: "exists_by_name" });
  console.log(`⏭️  Evento ya existe por nombre: ${e.eventName}`);
  continue;
}

1. Review skipped events in the output:
   {
     "skippedEvents": [
       {
         "name": "Event Name",
         "reason": "exists_by_name"
       }
     ]
   }
   
2. If you need to update existing records instead of skipping them, modify the script to use a PATCH request instead.

​

Invalid Property Values

{
  "status": "error",
  "message": "Property values were not valid",
  "errors": [
    {
      "message": "Property \"organizador_evento\" has invalid value"
    }
  ]
}

const mapOrganizerToValidOption = (organizer) => {
  if (!organizer) {
    return "Icare"; // Default
  }

  const organizerStr = organizer.toLowerCase();

  if (organizerStr.includes("icare") || organizerStr.includes("simpleevents")) {
    return "Icare";
  }

  if (organizerStr.includes("g12") || organizerStr.includes("cfo")) {
    return "G12";
  }

  // Add your custom mappings here
  if (organizerStr.includes("yourcompany")) {
    return "YourCompany";
  }

  // Fallback to default
  return "Icare";
};

1. Go to HubSpot Settings → Properties → Deal Properties
2. Find the organizador_evento property
3. Note the exact values in the “Options” list
4. Update the return values in the mapping function to match exactly

​

Rate Limiting

​

429 Too Many Requests

{
  "status": "error",
  "message": "You have reached your API rate limit",
  "errorType": "RATE_LIMIT"
}

• 100 requests per 10 seconds (default)
• Varies by subscription tier

1. Reduce batch size: The script processes 100 events per page (events.js:12). Consider reducing:
   let url = `${EVENTS_API}?limit=50`; // Reduced from 100
   
2. Add delays between requests: Insert a delay between API calls:
   const delay = (ms) => new Promise(resolve => setTimeout(resolve, ms));
   
   for (const e of todayEvents) {
     await delay(100); // 100ms delay between creates
     // ... existing logic
   }
   
3. Implement exponential backoff:
   const createWithRetry = async (eventData, retries = 3) => {
     for (let i = 0; i < retries; i++) {
       try {
         return await createCustomRecord(eventData);
       } catch (err) {
         if (err.statusCode === 429 && i < retries - 1) {
           const backoff = Math.pow(2, i) * 1000;
           console.log(`⏳ Rate limited, retrying in ${backoff}ms...`);
           await delay(backoff);
         } else {
           throw err;
         }
       }
     }
   };
   

​

Date Parsing Issues

​

Events Not Filtered Correctly

1. Add logging to see what dates are being parsed:
   const filtered = events.filter((event) => {
     const candidate = findHsCreatedate(event);
     console.log(`🔍 Event: ${event.eventName}, createdate: ${candidate}`);
     
     if (!candidate && candidate !== 0) return false;
     
     let ms = null;
     if (typeof candidate === "number") ms = candidate;
     else if (/^\d+$/.test(String(candidate))) ms = parseInt(candidate);
     else {
       const parsed = Date.parse(String(candidate));
       if (!isNaN(parsed)) ms = parsed;
     }
     
     console.log(`   📅 Parsed to: ${new Date(ms).toISOString()}`);
     console.log(`   ✅ In range: ${ms >= todayStart && ms <= todayEnd}`);
     
     return ms >= todayStart && ms <= todayEnd;
   });
   
2. Check timezone issues: The script uses local time (events.js:45-46):
   const today = new Date();
   today.setHours(0, 0, 0, 0); // Local midnight
   
   If your HubSpot events use UTC timestamps, you may need to adjust:
   const today = new Date();
   const todayStart = Date.UTC(
     today.getUTCFullYear(),
     today.getUTCMonth(),
     today.getUTCDate(),
     0, 0, 0, 0
   );
   
3. Verify date format: Check that hs_createdate is in milliseconds or ISO format:
   // Valid formats:
   1699963200000  // Milliseconds since epoch
   "1699963200000" // String of milliseconds
   "2025-11-14T10:00:00.000Z" // ISO 8601
   

​

Network and Connection Errors

​

ECONNREFUSED / ETIMEDOUT

Error: connect ECONNREFUSED

1. Check your internet connection
2. Verify that api.hubapi.com is accessible:
   curl -I https://api.hubapi.com/
   
3. Check proxy settings if behind a corporate firewall
4. Ensure Node.js can make HTTPS requests

​

Fetch is not defined

ReferenceError: fetch is not defined

1. Upgrade to Node.js 18+ (recommended):
   node --version
   
2. Or install node-fetch:
   npm install node-fetch
   
   Then update events.js:
   const fetch = require('node-fetch');
   

​

Reading Error Logs

​

Console Log Structure

console.log(`📍 Página obtenida: ${data.results?.length || 0} eventos encontrados`); // Info
console.log(`✅ Total de eventos obtenidos: ${events.length}`); // Success
console.log(`⚠️  No se encontró la propiedad 'pipeline'...`); // Warning
console.error(`❌ Error al obtener eventos (${res.status}):`, errorData); // Error

​

Error Context

console.error(
  `❌ Error al obtener eventos (${res.status}):`,
  errorData
);

console.error("❌ Error creando record:", data);

console.error(
  `❌ Error creando evento "${e.eventName}":`,
  eventErr.message
);

​

Final Output

{
  "outputFields": {
    "totalEvents": 150,
    "todayEvents": 12,
    "createdCount": 8,
    "skippedCount": 3,
    "failedCount": 1,
    "createdEvents": "[{\"id\": \"123\", \"dealname\": \"Event 1\"}, ...]",
    "skippedEvents": "[{\"name\": \"Event 2\", \"reason\": \"exists_by_id\"}, ...]",
    "failedEvents": "[{\"name\": \"Event 3\", \"error\": \"Validation error\"}, ...]"
  }
}

• createdCount: Successfully created deals
• skippedCount: Events that already exist (not an error)
• failedCount: Events that encountered errors (investigate failedEvents)

​

Debugging Tips

​

Enable Verbose Logging

const DEBUG = true;

if (DEBUG) {
  console.log(`🔍 Processing event:`, JSON.stringify(event, null, 2));
  console.log(`🔍 Pipeline value:`, pipelineValue);
  console.log(`🔍 Deal stage:`, dealStage);
  console.log(`🔍 Request body:`, JSON.stringify(body, null, 2));
}

​

Capture Full API Responses

const res = await fetch(url, options);
const rawText = await res.text();
console.log(`📡 Raw response (${res.status}):`, rawText);

const data = JSON.parse(rawText);

​

Test Individual Functions

// Test pipeline extraction
const testEvent = {
  customProperties: [
    { name: "pipeline", value: "732960029" }
  ]
};
console.log(getPipelineFromCustomProperties(testEvent.customProperties));
// Expected: "732960029"

// Test deal stage mapping
console.log(getDealStageByPipeline("732960029"));
// Expected: "1067986567"

​

Use the Test Script

node test.js

​

Check HubSpot API Status

1. Check HubSpot’s status page: status.hubspot.com
2. Review HubSpot’s API changelog for recent changes
3. Test API endpoints directly with curl:
   curl -H "Authorization: Bearer pat-na1-..." \
     https://api.hubapi.com/marketing/v3/marketing-events/?limit=1
   

​

Getting Help

1. Collect diagnostic information:
   • Node.js version (node --version)
   • Full error message and stack trace
   • Sample event data (redact sensitive info)
   • Console output from test script
2. Review the source code:
   • events.js:7-40 - Event fetching logic
   • events.js:54-123 - Date filtering
   • events.js:126-180 - Duplicate detection
   • events.js:269-319 - Record creation
3. Contact support with the diagnostic information

​

Next Steps