Support Automation #3379: NPS Collection with ClickUp + Email + Raycast

Problem

Agents switch between ClickUp and Email to complete nps collection, which slows resolution and fragments ticket history.

Connecting the tools keeps customer context in one thread.

Workflow

ClickUp ticket event → classify/priority rules → update Email → ping channel in Raycast.

Tools Used

• ClickUp
• Email
• Raycast

Setup Steps

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

Expected Outcome

• A repeatable nps collection path for support teams.
• Less context switching between ClickUp and Email.
• Easier hand-offs for the next ops owner.

Benefits & ROI

• Library metadata: High ROI tier · Medium difficulty · ~10 min setup estimate.
• Reduces manual nps collection steps between ClickUp, Email, Raycast.
• Provides a baseline you can extend with approvals, logging, or QA gates.

Variations

• Batch non-urgent nps collection runs on a schedule instead of realtime.
• Archive raw payloads to a datastore for audit.

Troubleshooting

• Run a single test record before bulk backfill.
• Pause the workflow before rotating API keys, then resume after credentials update.
• Confirm ticket status enums match between helpdesk and downstream tools.