Sales Automation #976: NPS Collection with Asana + Slack + HubSpot

Problem

Reps lose time copying nps collection updates from Asana 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

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

Tools Used

• Asana
• Slack
• HubSpot

Setup Steps

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

Expected Outcome

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

Benefits & ROI

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

Troubleshooting

• Test with won/lost opportunities to ensure terminal stages do not re-open.
• Re-authenticate OAuth tokens if the flow stops unexpectedly.
• Compare field types between source and destination mappings.