Overview of integration options
Cortex Voice offers three levels of integration depending on your technical maturity and requirements:
| Method | Complexity | Best for |
|---|---|---|
| Zapier | Low — no code | SMBs without a developer, simple CRM flows |
| Webhooks | Medium — basic JSON | Technical teams, custom real-time flows |
| REST API | High — development required | Custom integrations, bidirectional synchronization |
If you use a CRM (HubSpot, Salesforce, Pipedrive) or a task management tool (Notion, Asana, Monday), start with Zapier — setup takes less than 30 minutes and requires no technical skills. The API is documented in Resources & Documentation.
Integration via Zapier
Settings → Integrations → API Keys → Generate a key. Name the key (e.g. Zapier — Production) and copy it immediately — it will only be displayed once. Store it in your password manager.
In Zapier, search for Cortex Voice by Comulead in the app directory. Select the trigger (New NPS Response) and connect your account using the API key you generated. Test the connection — Zapier will load the 3 most recent responses to validate.
Recommended workflow examples:
- Detractor → HubSpot: create a follow-up task assigned to the account manager + add a note to the contact record with the score and verbatim
- Promoter → Slack: send a message to the #nps-wins channel with the positive verbatim
- Any response → Google Sheets: add a row with score, segment, verbatim and date for external analysis
Add a Filter step in your Zap to trigger the action only for a specific segment. Example: Filter → Score is less than 7 → create the HubSpot task. Without this filter, every response (including promoters) will trigger the follow-up task.
Integration via Webhooks
Settings → Integrations → Webhooks → Add a webhook. Enter your endpoint URL (must accept JSON POST requests) and select the events to listen to: response.created, response.detractor, response.promoter.
Each event sends a structured payload containing:
event— event type (response.created, etc.)respondent.email— respondent's email addressresponse.score— NPS score given (0–10)response.segment— promoter / neutral / detractorresponse.verbatim— open-ended response textresponse.themes— array of Cortex AI themessurvey.idandsurvey.name— source survey identifier
Cortex Voice signs each payload with HMAC-SHA256 using your webhook secret. Verify the signature in the X-Cortex-Signature header before processing the payload — this prevents fraudulent data injection.
Your endpoint must return an HTTP 200 code within 5 seconds. If Cortex Voice does not receive a 200, it retries 3 times at increasing intervals (1 min, 5 min, 30 min). After 3 failures, the webhook is automatically disabled and you receive an alert email.
Security best practices
- Never share your API key in a public code repository (GitHub, GitLab)
- Create a separate API key for each integration — makes revocation easier if one is compromised
- Enable automatic key rotation under Settings → Integrations → Security
- Always verify the HMAC-SHA256 signature on all incoming webhooks
- Review API access logs under Settings → Integrations → Logs
Key takeaways
- Start with Zapier — no code, under 30 minutes to set up, compatible with 6,000+ tools
- The API key is only displayed once — store it immediately in a password manager
- Use segment filters in Zapier to avoid triggering actions on every response
- Webhooks deliver the full Cortex AI payload (themes included) — use the
response.themesfield to enrich your CRM - Your webhook endpoint must return HTTP 200 within 5 seconds to avoid automatic deactivation