Make.com Integration Guide

Prerequisites

Before beginning your integration, ensure you have all required components and access.

Required Access

✅ Make.com account with HTTP module access
✅ Novus API credentials (Username and Password)
✅ Whitelisted IP address for API access
✅ Access to QA and/or Production environments
✅ Understanding of JSON and API authentication

Environment Information

Integration Overview

The Novus API integration follows a two-step authentication process with specific considerations for Make.com workflows.

Workflow Architecture

1. Request Authentication Token
   ├── POST /WAEPANYL/Token
   ├── Headers: UserName, Password
   └── Response: Token (expires in 5 minutes)

2. Retrieve Member Information  
   ├── POST /WAEPANYL/GetMemberInfo
   ├── Headers: UserName, Password, Token
   ├── Body: Member identification data
   └── Response: Member details and policies

3. Process Response Data
   ├── Parse JSON response
   ├── Handle empty responses
   └── Extract required information

HTTP Module Selection

The Novus API requires specific Make.com HTTP module configuration due to its custom authentication method.

Correct Module Selection

Token Request Setup

Configure your first HTTP module to request an authentication token from the Novus API.

Module Configuration

Header 1:
Name: UserName
Value: [YOUR_USERNAME]

Header 2:
Name: Password  
Value: [YOUR_PASSWORD]

{
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
  "expires_in": 300,
  "token_type": "Bearer"
}

Member Info Request Setup

Configure your second HTTP module to retrieve member information using the authentication token.

Module Configuration

Header 1:
Name: UserName
Value: [YOUR_USERNAME]

Header 2:
Name: Password
Value: [YOUR_PASSWORD]

Header 3:
Name: Token
Value: {{token_from_previous_module}}

{
  "MembershipID": "{{membershipId}}",
  "MemberSSN": "{{memberSSN}}",
  "DateOfBirth": "{{dateOfBirth}}",
  "FirstName": "{{firstName}}",
  "LastName": "{{lastName}}"
}

Response Parsing

Configure JSON parsing and response handling for the API responses.

Add JSON Parse Modules

1. After Token Request: Add a "JSON > Parse JSON" module to extract the token
2. After Member Request: Add another "JSON > Parse JSON" module to process member data

Response Handling Strategies

[
  {
    "coveredPersonType": "Member",
    "demographics": { /* member details */ },
    "Products": [ /* policy information */ ]
  },
  {
    "coveredPersonType": "Spouse", 
    "demographics": null,
    "Products": null
  }
]

// In a Filter or Router module
{{if(length(response) > 0; "has_data"; "no_data")}}

Token Management

Implement smart token management to handle the 5-minute expiration efficiently.

Token Management Strategies

For each member:
1. HTTP: Request Token
2. JSON: Parse Token  
3. HTTP: Get Member Info (use fresh token)
4. JSON: Parse Member Response
5. Process member data

// Check if cached token is still valid (4-minute buffer)
{{if(and(
  length(get("cached_token")) > 0;
  ((formatDate(now; "X")) - get("token_timestamp")) < 240
); "use_cached"; "get_new")}}

Member Info HTTP Module:
1. Add Error Handler
2. Filter: Status Code = 401
3. HTTP: Get New Token
4. Set Variable: Update cached token
5. Resume: Retry original request

Error Handling

Implement comprehensive error handling for robust Make.com workflows.

Common Error Scenarios

Error Handler Implementation

1. Right-click HTTP module → "Add error handler"
2. Add "HTTP Status Code" filter
3. Configure handling based on error type:
   - 401: Refresh token and retry
   - 403: Send notification about IP restriction  
   - 500: Wait and retry (max 3 attempts)
   - Other: Log error and continue

Best Practices

Follow these recommendations for production-ready Make.com integrations.

Security & Credentials

• Use Data Stores: Store API credentials in Make.com Data Stores, not hardcoded in scenarios
• Environment Variables: Use different credentials for QA vs Production
• IP Monitoring: Monitor for IP changes that might affect whitelisting
• Credential Rotation: Plan for regular credential updates

Performance Optimization

• Token Caching: Implement smart token caching to reduce API calls
• Batch Processing: Process multiple members with same token when possible
• Parallel Processing: Use Router for independent operations
• Rate Limiting: Add delays between requests if processing large volumes

Monitoring & Logging

Add logging modules to track:
✅ API request/response times
✅ Token refresh events  
✅ Error occurrences and types
✅ Empty response rates
✅ Daily usage statistics

Data Validation

• Input Validation: Validate member data format before API calls
• Date Formatting: Ensure dates are in YYYY-MM-DD format
• SSN Formatting: Include dashes in SSN format
• Name Accuracy: Verify exact spelling of names

Troubleshooting

Common issues and their solutions for Make.com + Novus API integration.

Quick Diagnostic Checklist

✅ Verify API credentials are correct
✅ Check IP address is whitelisted  
✅ Confirm using correct environment URLs
✅ Test token generation manually
✅ Validate request body JSON format
✅ Check Make.com scenario execution history
✅ Review error logs for specific error codes

Common Issues

Getting Help