Agent Templates
Slack Triage Agent

Slack triage agents that route bugs and support tickets automatically

Connect Slack, GitHub, and Zendesk. The agent listens to your support channel, classifies messages by intent, and creates issues — no human router needed.

Slack Triage Agent
Sample Agent for Acme
May 22 · 10:00 AM ·
47s
Message Claude...
Trusted by teams shipping agents to production
Slack Triage Agent
Sample Agent for Acme
May 22 · 10:00 AM ·
47s
Message Claude...

How the LangGraph workflow routes a Slack message to the right tool in five steps

A real working agent you can deploy

This agent uses keyword classification as its routing layer — swap it for an LLM call for nuanced intent detection. Scalekit handles OAuth for Slack, GitHub, and Zendesk so the agent never stores tokens in application code.

Why choose Scalekit

Delegated identity. Not service accounts.

Credentials never touch agent code or LLM context. The agent acts as the user, not as a shared bot.
Delegated OAuth - Agent reads your calendar, your inbox — scoped to the authorizing identity, not org-wide.
Credentials outside agent runtime  -  Tokens never touch agent code or LLM context. Both failure modes covered.
Token lifecycle automatic  -  Refresh, expiry, rotation across all connectors. One SDK call. Zero management code.
200+ prebuilt connectors  -  Google, Slack, HubSpot, GitHub, Jira, Notion, Salesforce — same auth pattern everywhere.

Agents that route support, without the auth plumbing

Three things you'd otherwise build: OAuth to Slack, token storage for GitHub, and Zendesk API auth. Handled.

OAuth flow per connector
One SDK call returns a delegated token for any connector. Google, HubSpot, Slack, same pattern across all 200+ connectors
Secure token vault  
Scalekit stores OAuth credentials outside agent code and outside LLM context. Both are separate failure modes. Both covered
Token refresh logic
Token lifecycle handled automatically — expiry, rotation, re-auth — across every connector. Agent runs in 6 months. Same call works
Try other Agent Templates

Prebuilt agents you can ship today

Each one runs on delegated identity, scoped per user.

ENGINEERING
Auto-release notes agent
Group merged GitHub PRs by feature, fix, or chore and publish release notes per tag. No manual changelog grooming.
ENGINEERING
DevOps assistant agent
Triage GitHub incidents, open Linear tickets, and notify the on-call channel in Slack with context already attached.
ENGINEERING
Engineering standup agent
Aggregate GitHub and GitLab activity, link to Jira, and post a daily standup digest to Slack. No async updates.
SUPPORT
Support triage agent
Read Zendesk tickets, fetch runbooks from Notion, and route to the right Slack channel with a drafted response.
GTM
HubSpot to Slack updates agent
Watch HubSpot deal stage changes and post structured updates to the right Slack channel. Reps stop checking the CRM all day.
GTM
CRM AI agent
Log calls, update opportunity stages, and surface stalled deals across HubSpot or Salesforce. No manual data entry.
Customize the sample

Clone it and own it with connectors you choose

Don't sweat the integration. Point a coding agent at the repo. It clones, swaps in your connectors, and adds new steps for you.

1
Install a coding agent
2
Give it this prompt
Connectors used
No items found.

Build your own
multi-connector agent

Add connectors. Change the LLM. Same delegated auth pattern.