SSO, RBAC & audit · Any model, your keys · No seat tax
Territory map, segment specialists, stateless round-robin pool, intent scoring, HubSpot writes, and escalation rules for routing a new inbound lead to the right rep.
kortix marketplace install kortix-starter:lead-routing-rules-skillkortix_routing_status property + timestamp + reason marks a lead handled),
not in a local ledger file. The round-robin pool is stateless by design too:
"whose turn is it" is answered by counting each rep's current lead load in
HubSpot, not by a rotating pointer that would need to persist somewhere. A
single sweep can find several new leads at once; handle each as an
independent unit — a scoring or routing failure on one lead is logged and
skipped, and never blocks or corrupts routing for any other lead in the same
sweep.
GET /crm/v3/objects/contacts/search
filterGroups: [
{ propertyName: "lifecyclestage", operator: "EQ", value: "{{hubspot_lifecycle_stage}}" },
{ propertyName: "kortix_routing_status", operator: "NOT_HAS_PROPERTY" }
]
kortix_routing_status (whether routed or
flagged) was handled by a prior run — skip it. A flagged lead stays
skipped until a human resolves it directly in HubSpot (assigning an owner
clears the need for another routing pass).| Signal | High-intent if |
|---|---|
| Title | VP-level or above, or an explicit buyer/economic-decision-maker title |
| Company size | At or above the team's enterprise threshold in memory |
| Stated timeline/budget | Filled in and inside the current quarter |
| Engagement | Multiple pricing-page visits, a demo request, or a direct sales-contact form (vs. a passive newsletter signup) |
kortix_routing_status of routed and a creation date in the
current week; assign the new lead to whichever pool rep has the fewest. Ties
break alphabetically by rep name — this keeps the pool stateless and
reproducible without a rotating pointer to persist between sessions.kortix_routing_status = flagged (with a timestamp and
reason) so it isn't re-flagged on the next sweep.kortix_routing_status = routed with a timestamp and
the reason (e.g. "territory: US-West", "segment: enterprise", "round-robin:
fewest current leads"). These are the only fields this skill ever writes.The role-to-grant policy, extra-scrutiny cases, the approval handshake, and how an applied grant gets logged.
Get a complete picture of any company or person before outreach. This skill always works with web search, and gets significantly better with enrichment and CRM data.
Daily runbook for budget pacing, CPA/ROAS drift, underperformer detection, and anomaly flags across Google Ads and Meta Ads, plus how to rank and word optimization recommendations.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
Extract-and-match runbook for incoming vendor invoices: line-item extraction, PO/prior-invoice matching, duplicate + overcharge detection, and the ledger + approval hand-off.
Search, dedupe against the seen-mentions ledger, classify sentiment and notability, and post a digest with suggested response drafts — the daily brand-monitor runbook.