Customer Success Automation #1773: NPS Collection with Intercom + HubSpot + Redis

Problem

CS teams track nps collection across Intercom, HubSpot, Redis, but manual updates mean health scores and account notes drift out of date.

This workflow keeps customer records consistent after each lifecycle event.

Workflow

Event in Intercom → validate payload → update HubSpot → log outcome for review.

Tools Used

• Intercom
• HubSpot
• Redis

Setup Steps

1. Create credentials for Intercom, HubSpot, Redis in your orchestration platform.
2. Define the nps collection trigger in Intercom.
3. Map required fields from Intercom to HubSpot.
4. Add error handling appropriate for a Medium workflow.
5. Run a test payload, then enable production execution (~23 min typical setup in our dataset).

Expected Outcome

• A repeatable nps collection path for customer success teams.
• Less context switching between Intercom and HubSpot.
• Easier hand-offs for the next ops owner.

Benefits & ROI

• Library metadata: Low ROI tier · Medium difficulty · ~23 min setup estimate.
• Reduces manual nps collection steps between Intercom, HubSpot, Redis.
• Provides a baseline you can extend with approvals, logging, or QA gates.

Troubleshooting

• Map account IDs consistently across CS tools.
• Verify health-score or NPS fields accept automated updates.
• Exclude churned accounts with an explicit filter node.