Sales Automation #963: NPS Collection with HubSpot + Slack + Typeform

Problem

Reps lose time copying nps collection updates from HubSpot into Slack, which delays follow-ups and skews pipeline reporting.

This pattern connects the stack so sales data stays in sync without manual exports.

Workflow

HubSpot stage change → map pipeline fields → upsert Slack → log activity for nps collection.

Tools Used

• HubSpot
• Slack
• Typeform

Setup Steps

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

Expected Outcome

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

Benefits & ROI

• Library metadata: High ROI tier · Hard difficulty · ~46 min setup estimate.
• Reduces manual nps collection steps between HubSpot, Slack, Typeform.
• Provides a baseline you can extend with approvals, logging, or QA gates.

Variations

• Route enterprise accounts to a dedicated owner queue in Typeform.
• Require manager approval before updating closed-won records in Slack.

Troubleshooting

• Compare field types between source and destination mappings.
• Inspect execution logs for HTTP 429 rate-limit responses.
• Run a single test record before bulk backfill.