Shata Solutions
← Back to marketplace
Customer Support

Priority Detection

Elevate ticket priority when sentiment, SLA risk, or customer tier signals demand faster response.

Automation overview

What this automation does

This automation starts when zendesk ticket create or update webhook. It openai create, hubspot create, and slack process via slack, then monitors SLA clock, and bumps priority to urgent when angry sentiment + enterprise tier or SLA <2h remaining. PagerDuty incident fires for P1; Slack @mention fo.

Trigger
Zendesk ticket create or update webhook
Main actions
OpenAI create → HubSpot create …
Final outcome
monitors SLA clock, and bumps priority to urgent when angry sentiment + enterpri…
Execution time
30–90 seconds
Apps used
5 integrations
AI-powered
No
Difficulty
Beginner
Beginner
Workflow diagram

End-to-end scenario flow

Read-only visualization of how data moves from trigger to final result.

Trigger
Zendesk
Webhook received
AI
OpenAI
Create
Step 2
HubSpot
Create
Step 3
Slack
Process via Slack
Result
Slack
Workflow complete
Step-by-step

How each step runs

  1. 1
    ZendeskTrigger
    Webhook received

    Zendesk ticket create or update webhook

  2. 2
    OpenAI
    Create

    On Zendesk ticket create or update, workflow scores sentiment via GPT-4o, checks customer tier from HubSpot

  3. 3
    HubSpot
    Create

    On Zendesk ticket create or update, workflow scores sentiment via GPT-4o, checks customer tier from HubSpot

  4. 4
    Slack
    Process via Slack

    monitors SLA clock, and bumps priority to urgent when angry sentiment + enterprise tier or SLA <2h remaining. PagerDuty incident fires for P1; Slack @mention fo

  5. 5
    Slack
    Workflow complete

    monitors SLA clock, and bumps priority to urgent when angry sentiment + enterprise tier or SLA <2h remaining. PagerDuty incident fires for P1; Slack @mention fo

Apps used

Connected applications

Zendesk

Create

Webhooks

Create

OpenAI

Create

HubSpot

Create

Slack

Process via Slack

Summary

Automation summary

Trigger
Zendesk ticket create or update webhook
Inputs
Zendesk ticket create or update webhook, Business Name, Notification Email, Timezone
Outputs
monitors SLA clock, and bumps priority to urgent when angry sentiment + enterprise tier or SLA <2h remaining. PagerDuty incident fires for P1; Slack @mention fo, HubSpot create, Slack process via Slack
Business goal
Automate priority detection end-to-end with accurate app routing.
Execution frequency
Real-time on event
Estimated runtime
30–90 seconds
Error handling
Failed steps retry up to 3 times with exponential backoff; persistent failures notify your configured channel and log to the run history.
Dependencies
Zendesk, Webhooks, OpenAI
Benefits

Why use this automation?

Save ~12 hours/week

Remove repetitive steps from Priority Detection so your team focuses on high-value work.

Reduce manual work

Connected apps sync data automatically instead of copy-paste between dashboards.

Prevent human errors

Standardized logic runs the same way every time, with retries on failure.

Requirements

What you need to get started

Required apps

  • Zendesk
  • Webhooks
  • OpenAI

Required accounts

  • Active Zendesk workspace with API access
  • Active Webhooks workspace with API access
  • Active OpenAI workspace with API access
  • Shata Automation workspace (free tier supported)

Required API keys

  • OAuth tokens for each connected integration

Permissions

  • Read access on trigger sources (forms, sheets, webhooks, or CRM objects)
  • Write access on destination apps (email, chat, CRM, or storage)

Estimated setup time

  • 5 min including app authorization and test run
  • Difficulty: Beginner

Optional apps

  • HubSpot (optional)
  • Slack (optional)

Automation runtime

Activate this template

PartialSome steps run in preview until their integrations go live.

Connect required apps via OAuth or API keys. Credentials are encrypted server-side. Dev test runs mock external actions when connections are missing.

Draft
0%
Activation readiness

Est. setup time: ~10 min

Required connections

  • zendesk(required)
    Previewzendesk: workflow actions run in preview
    Missing
  • OpenAI(required)
    Missing
  • HubSpot(required)
    PreviewHubSpot: workflow actions run in preview
    Missing
  • Missing connection: zendesk
  • Missing connection: OpenAI
  • Missing connection: HubSpot
Manage all connections →View all installations →

Workflow summary

Trigger
Zendesk ticket create or update webhook
Steps
5 nodes
Required apps
3
Optional apps
1

Trigger

Webhook trigger

Activate this workflow to provision the trigger endpoint.

Run history

No runs yet. Install the template and run a test, or activate to receive webhook/schedule runs.

FreeBeginnerPartial5 min setup4.13.8k installs · 273 reviews
Customize for My Business
Analytics

Template performance

24.9k
Views
3.8k
Installs
454
Favorites
4.1
Avg rating
15.1%
Conversion
5 min
Setup time
96%
Success rate
77
Trending score
Most used integrations
ZendeskOpenAIHubSpot

On Zendesk ticket create or update, workflow scores sentiment via GPT-4o, checks customer tier from HubSpot—enterprise, pro, free—monitors SLA clock, and bumps priority to urgent when angry sentiment + enterprise tier or SLA <2h remaining. PagerDuty incident fires for P1; Slack @mention for P2; normal queue for P3.

Some steps run in preview until their integrations go live.

Required apps
ZendeskPreviewOpenAILiveHubSpotPreview
Optional apps
SlackLive
All integrations
ZendeskOpenAIHubSpotSlack
Workflow preview

How Priority Detection runs

1
Trigger
Define tier matrix
2
Process
Rule engine
3
Action
zendesk
4
Notify
Alert & log
ZendeskOpenaiHubspotSlack
Setup steps

Get started in 5 steps

  1. 1
    Connect ticketing and CRM

    Zendesk, HubSpot customer tier, PagerDuty, Slack, OpenAI sentiment.

  2. 2
    Define tier matrix

    Enterprise + negative sentiment = P1; pro + SLA risk = P2.

  3. 3
    Configure SLA sources

    Pull SLA policy from Zendesk by plan type and ticket category.

  4. 4
    Set alert channels

    P1 PagerDuty on-call; P2 Slack with 15-minute ack requirement.

  5. 5
    Simulate scenarios

    Test enterprise angry, free tier question, SLA breach mock tickets.

Variables

Configurable settings

VariableTypeDefaultRequired
Business NametextYour BusinessYes
Notification EmailemailYes
TimezoneselectYes
Slack Channeltext#generalNo
FAQ

Frequently asked questions

False urgent spikes?

Sarcasm detection layer reduces false positive angry classification.

Manual priority lock?

Agent-set priority not downgraded by automation.

Off-hours P1?

PagerDuty schedule respects on-call rotation timezone.

Re-opened tickets?

Priority re-scored on customer reply after solve.

Get started

Customize Priority Detection for your business

Our team can adapt this template to your exact workflow, apps, and brand requirements.