Support Automation #3948: Identity Verification with Zendesk + Slack + Asana

Problem

Agents switch between Zendesk and Slack to complete identity verification, which slows resolution and fragments ticket history.

Connecting the tools keeps customer context in one thread.

Workflow

Zendesk ticket event → classify/priority rules → update Slack → ping channel in Asana.

Tools Used

• Zendesk
• Slack
• Asana

Setup Steps

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

Expected Outcome

• A repeatable identity verification path for support teams.
• Less context switching between Zendesk and Slack.
• Easier hand-offs for the next ops owner.

Benefits & ROI

• Library metadata: Medium ROI tier · Hard difficulty · ~49 min setup estimate.
• Reduces manual identity verification steps between Zendesk, Slack, Asana.
• Provides a baseline you can extend with approvals, logging, or QA gates.

Troubleshooting

• Confirm ticket status enums match between helpdesk and downstream tools.
• Test reopened tickets to avoid duplicate threads.
• Map priority and assignee fields explicitly.