Sales Automation #973: NPS Collection with Intercom + HubSpot + GitLab

Problem

When nps collection depends on hand-offs between Intercom, HubSpot, GitLab, ownership breaks down and records arrive late in the CRM.

Automating the Intercom → HubSpot path keeps the revenue workflow auditable.

Workflow

New or updated record in Intercom → qualify/enrich → sync to HubSpot → notify owner in GitLab.

Tools Used

• Intercom
• HubSpot
• GitLab

Setup Steps

1. Connect Intercom and HubSpot with scoped API permissions.
2. Configure the nps collection entry condition (Easy difficulty in this library entry).
3. Set field transforms and default values between tools.
4. Add a dead-letter or retry path for failed runs.
5. Validate with sample data before go-live.

Expected Outcome

• nps collection runs without manual copy-paste between Intercom, HubSpot, GitLab.
• Status updates stay aligned across the connected tools.
• Failures surface in one place instead of silent drift.

Benefits & ROI

• Ranked as Medium ROI in our template dataset for Sales.
• Typical implementation complexity: Easy.
• Frees ops time from repetitive nps collection tasks in this stack.

Troubleshooting

• Confirm CRM pipeline stage IDs match your production workspace.
• Verify lead owner and account IDs exist on both sides of the sync.
• Check duplicate rules before enabling bi-directional updates.