Customer Success Automation #1771: NPS Collection with Jira + Discord + MongoDB

Problem

CS teams track nps collection across Jira, Discord, MongoDB, but manual updates mean health scores and account notes drift out of date.

This workflow keeps customer records consistent after each lifecycle event.

Workflow

Webhook or schedule from Jira → business rules for nps collection → write to Discord.

Tools Used

• Jira
• Discord
• MongoDB

Setup Steps

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

Expected Outcome

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

Benefits & ROI

• Library metadata: Medium ROI tier · Medium difficulty · ~38 min setup estimate.
• Reduces manual nps collection steps between Jira, Discord, MongoDB.
• 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.
• Map account IDs consistently across CS tools.