Skip to main content

​
Overview

The Sanka connector for Claude lets you manage deals, contacts, companies, invoices, and more using natural language inside any Claude conversation. Connect once via OAuth and start working immediately. Three ways to use Sanka with AI:
PathAudienceSetup time
Claude ConnectorEveryone0 min — just click Connect
MCP ServerDevelopers in IDEs2 min — add config to your editor
SDKDevelopers in code5 min — install package, write code
This page covers the Claude Connector. For MCP and SDK, see the Quickstart.

​
Connect Sanka to Claude

  1. Open Claude → Settings → Connectors
  2. Find Sanka and click Connect
  3. Sign in to your Sanka workspace and grant permissions
  4. Done — Claude can now access your Sanka data
The OAuth flow uses PKCE (no client secret). Claude stores a refresh token so you stay connected across sessions.

​
Scopes

When you connect, you can grant Claude access to:
  • Deals, contacts, companies — create, read, update
  • Invoices, estimates, orders — create, read, update
  • Subscriptions, payments, bills — manage billing lifecycle
  • Items, inventory — read stock levels and product catalog
  • Workflows — trigger and manage automations
  • Reports — query business metrics
You can revoke access at any time from Sanka’s developer settings.

​
Usage Examples

​
Example 1: Create and enrich a deal

Ask Claude to create a new deal and automatically enrich the company data:
“Create a deal for jane@acme-corp.com — they’re evaluating our platform for their 50-person sales team. Enrich the company data so we know their industry and tech stack.”
What happens behind the scenes:
  1. Claude calls execute to create a contact for jane@acme-corp.com
  2. Claude calls execute to enrich the company (acme-corp.com) — pulling industry, employee count, tech stack, and funding data
  3. Claude calls execute to create the deal linked to the contact and enriched company
  4. Claude returns a summary with the deal details and enriched firmographic data
Result: A fully enriched deal record with company firmographics, created in seconds without leaving the conversation.

​
Example 2: Pipeline review with filters

Ask Claude to analyze your current pipeline:
“Show me all deals closing this month with a value over $10,000. Sort by close date and flag any that haven’t been updated in the last 7 days.”
What happens behind the scenes:
  1. Claude calls execute to list deals with date and amount filters
  2. Claude processes the results, checking last-updated timestamps
  3. Claude returns a formatted table with flagged stale deals
Result: A pipeline summary with actionable flags — no dashboard switching required.

​
Example 3: Invoice a closed deal

When a deal closes, ask Claude to generate the invoice:
“The Acme Corp deal just closed for $24,000/year. Generate an invoice with NET30 terms and send it to their billing contact.”
What happens behind the scenes:
  1. Claude calls execute to retrieve the deal and associated contacts
  2. Claude calls execute to create an invoice with the deal amount, NET30 terms, and billing contact
  3. Claude returns the invoice details with a link to review before sending
Result: A draft invoice linked to the deal, ready for review.

​
Example 4: Lead scoring

Ask Claude to score and prioritize your leads:
“Score all contacts added this week by ICP fit. Our ideal customer is a B2B SaaS company with 50-500 employees in North America.”
What happens behind the scenes:
  1. Claude calls execute to list recently created contacts
  2. Claude calls execute to enrich each contact’s company data
  3. Claude calls execute to score each contact against the ICP criteria
  4. Claude returns a ranked list with scores and reasoning
Result: A prioritized lead list with enrichment data and fit scores.

​
Available Tools

The connector exposes two MCP tools:

​
execute

Runs JavaScript/TypeScript code against the Sanka SDK in a sandboxed environment. This is the primary tool — it can call any Sanka API endpoint.
  • Annotations: readOnlyHint: false, destructiveHint: true
  • Capabilities: Full CRUD on all Sanka resources (deals, contacts, invoices, etc.)
  • Security: Code runs in an isolated Deno subprocess with network access limited to the Sanka API

​
search_docs

Searches the Sanka SDK documentation to find methods, parameters, and usage examples.
  • Annotations: readOnlyHint: true
  • Use case: Claude uses this to discover the right API methods before writing code

​
Technical Details

​
OAuth Configuration

ParameterValue
Authorization URLhttps://app.sanka.io/oauth/authorize
Token URLhttps://app.sanka.io/oauth/token
Revoke URLhttps://app.sanka.io/oauth/revoke
JWKS URLhttps://app.sanka.io/oauth/jwks.json
Grant typeAuthorization Code with PKCE
Token formatJWT (RS256 or HS256)
Token lifetime15 minutes (auto-refreshed)
Refresh token30 days, stored in httponly cookie

​
MCP Server

ParameterValue
TransportStreamable HTTP
Endpointhttps://mcp.sanka.io/mcp
AuthenticationBearer token (OAuth access token)
Tool response limitUnder 25,000 tokens

​
Privacy & Security

  • Privacy policy: sanka.io/privacy
  • Data handling: Claude sends API requests to Sanka on behalf of the user. No data is stored by the connector beyond the OAuth token.
  • Token storage: OAuth tokens are managed by Claude and refreshed automatically.
  • Revocation: Users can revoke access from Sanka’s developer settings at any time.

​
Troubleshooting

“App is not installed” Your Sanka workspace admin needs to enable the Claude connector. Go to Sanka → Settings → Integrations → Claude and click Install. “Requested scopes not approved” The workspace admin may have restricted which scopes the Claude connector can use. Contact your admin to approve the required scopes. “Origin not allowed” This typically indicates a configuration issue. Contact Sanka support. Token expired errors Claude automatically refreshes tokens. If you see persistent auth errors, disconnect and reconnect the Sanka connector in Claude Settings.