scalekit

A real working agent you can deploy

This repo uses a single SCALEKIT_USER_ID env var to simulate one user. In production, pass each user's real ID as the identifier on every Scalekit call, and send them an authorization link whenever their connector status is not ACTIVE.

01

Authorize, then orchestrate

main.py

Every connection is authorized once via a one-time link. Scalekit refreshes tokens for you across all three connectors. main.py polls Zendesk on a configurable interval, verifies each connector is ACTIVE, and runs the triage pipeline for all unassigned or new tickets.

main.py

Copy

import os
from scalekit import ScalekitClient
from langchain.agents import create_tool_calling_agent

client = ScalekitClient(
    env_url=os.environ["SCALEKIT_ENV_URL"],
    client_id=os.environ["SCALEKIT_CLIENT_ID"],
    client_secret=os.environ["SCALEKIT_CLIENT_SECRET"],
)

# LangChain-compatible tools scoped to this user
tools = client.actions.langchain.get_tools(
    identifier="user@example.com",
    connection_names=["zendesk", "notion", "slack"],
)

agent = create_tool_calling_agent(llm, tools, prompt)

02

Fetch new Zendesk tickets

fetch_tickets.py

03

Look up Notion knowledge base

lookup_notion.py

04

Classify urgency and assign owner

classify.py

05

Notify team via Slack

notify_slack.py

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 triage support tickets, without the auth plumbing

Three things you'd otherwise build: Zendesk API auth, Notion OAuth for KB search, Slack credentials. Handled.

OAuth flow per connector

One SDK call returns a delegated token for any connector. Google, HubSpot, Slack, same pattern across all 200+ connectors

tools = client.actions.langchain.get_tools(
    identifier=user_id,
    connection_names=["zendesk", "notion", "slack"],
)
agent = create_tool_calling_agent(llm, tools, prompt)

Secure token vault

Scalekit stores OAuth credentials outside agent code and outside LLM context. Both are separate failure modes. Both covered

client = ScalekitClient(
    env_url=os.environ["SCALEKIT_ENV_URL"],
    client_id=os.environ["SCALEKIT_CLIENT_ID"],
    client_secret=os.environ["SCALEKIT_CLIENT_SECRET"],
)
# Credentials never in agent code or LLM context

Token refresh logic

Token lifecycle handled automatically — expiry, rotation, re-auth — across every connector. Agent runs in 6 months. Same call works

# Day 1 or day 180 - same call works
tools = client.actions.langchain.get_tools(
    identifier=user_id,
    connection_names=["zendesk", "notion", "slack"],
)

Try other Agent Templates

Prebuilt agents you can ship today

Each one runs on delegated identity, scoped per user.

SUPPORT

Support triage agent

Read Zendesk tickets, fetch runbooks from Notion, and route to the right Slack channel with a drafted response.

SUPPORT

Support ticket automation (Google ADK)

Google ADK agent that classifies Zendesk tickets, pulls Notion context, and posts to Slack. End-to-end ticket handoff.

SUPPORT

Freshdesk CSAT follow-up agent

Google ADK agent that watches low CSAT scores in Freshdesk and drafts personalised follow-ups for support leads.

Freshdesk

View agent

OPS

Email-to-calendar scheduling agent

Parse scheduling intent from Gmail threads and create Google Calendar events with the right attendees and timezone.

Gmail

Google Calendar

View agent

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.

HubSpot

Slack

View agent

GTM

CRM AI agent

Log calls, update opportunity stages, and surface stalled deals across HubSpot or Salesforce. No manual data entry.

HubSpot

Salesforce

View agent

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

terminal

Copy Copied

claude "Set up a support triage agent using Zendesk, Notion, and Slack via Scalekit"

terminal

Copy Copied

codex "Set up a support triage agent using Zendesk, Notion, and Slack via Scalekit"

terminal

Copy Copied

gh copilot suggest "Set up a support triage agent using Zendesk, Notion, and Slack via Scalekit"

terminal

Copy Copied

Open Cursor Composer (Cmd+Shift+I) Paste the prompt from the Prompt tab

terminal

Copy Copied

npx skills add scalekit-inc/skills --skill setup-scalekit

2

Give it this prompt

prompt

Copy Copied

Clone github.com/scalekit-inc/python-connect-demos/langchain. Set connection_names = ["zendesk", "notion", "slack"]. Build a support triage pipeline: poll Zendesk for new and unassigned tickets, search Notion KB for matching articles, classify urgency P1-P4 with the LLM, post to the right Slack channel with suggested owner and KB link. P1 tickets DM the on-call rep directly. Set SCALEKIT_ENV_URL, SCALEKIT_CLIENT_ID, SCALEKIT_CLIENT_SECRET in .env.

Support triage agents that route tickets on-behalf-of your users

How the agent fetches, classifies, and routes support tickets in five steps

A real working agent you can deploy

Delegated identity. Not service accounts.

Agents that triage support tickets, without the auth plumbing

Prebuilt agents you can ship today

Clone it and own it with connectors you choose

Build your own
‍multi-connector agent

Support triage agents that route tickets on-behalf-of your users

How the agent fetches, classifies, and routes support tickets in five steps

A real working agent you can deploy

Delegated identity. Not service accounts.

Agents that triage support tickets, without the auth plumbing

Prebuilt agents you can ship today

Clone it and own it with connectors you choose

Build your own‍multi-connector agent

Build your own
‍multi-connector agent