Seismic

Live

OAUTH 2.0

SALES ENABLEMENT

CRM & Sales

Seismic gives agents authenticated access to your sales enablement content: search the library, browse teamsites, manage files and workflows, and pull the right collateral under the rep's own account.

  • Per-user credentials: each search and file action runs as the actual rep, scoped to the content they can see.
  • Encrypted per-tenant vault: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: pre-call scope check, 90-day SIEM-exportable audit chain.
Seismic
agent · Acme Q3
Run
Find the latest security one-pager approved for enterprise deals.
S
seismic_search_content
88ms
Seismic agent
Found the enterprise security one-pager, approved 4 days ago, current version. 2 older drafts are still in review.
Content: 1 approved, 2 drafts
seismic
1 item
18:29
Message Claude...

Tools your sales agent reaches for in Seismic, scoped per user.

CALL ANY TOOL
Work sales enablement content end to end: search the library, browse and manage teamsites, work with personal workspace files, and move items through approval workflows.
seismic_list_users
List users
Get a list of users in the Seismic tenant (legacy endpoint). Supports pagination via limit/offset and a starts-with text filter matched against email, username, first name, or last name. New integrations should prefer the SCIM API to manage users.
Parameters
Name
Type
Required
Description
filter
string
Optional
Free text filter. Performs a starts-with match against email, username, first name, or last name.
limit
string
Optional
Maximum number of users to return. Default 1000 per the API, though the endpoint's own schema default is 10.
offset
string
Optional
Number of users to skip before returning results. Default 0.
schema_version
string
Optional
Schema version
tool_version
string
Optional
Tool version
seismic_search_content
Search content
seismic_list_teamsites
List teamsites
seismic_get_user
Get user
seismic_list_user_recents
List user recents
seismic_get_teamsite
Get teamsite
seismic_list_item_comments
List item comments
seismic_get_library_url
Get library url
seismic_list_item_versions
List item versions
seismic_get_teamsite_item
Get teamsite item
seismic_list_user_profiles
List user profiles
seismic_get_workspace_file
Get workspace file
seismic_list_teamsite_items
List teamsite items
seismic_get_teamsite_folder
Get teamsite folder
seismic_list_user_favorites
List user favorites
seismic_get_livesend_link_version
Get livesend link version
seismic_list_user_teamsites
List user teamsites
seismic_get_generated_livedoc_status
Get generated livedoc status
seismic_list_approval_workflows
List approval workflows
seismic_get_or_create_library_folder_path
Get or create library folder path
seismic_list_teamsite_folder_items
List teamsite folder items
seismic_add_item_comment
Add item comment
seismic_list_livedoc_generator_inputs
List livedoc generator inputs
seismic_create_library_url
Create library url
seismic_update_library_file
Update library file
seismic_create_library_file
Create library file
seismic_update_library_folder
Update library folder
seismic_create_livesend_link
Create livesend link
seismic_update_workspace_file
Update workspace file
seismic_create_library_folder
Create library folder
Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Seismic tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["seismic"], toolNames: [
    "seismic_list_users",
    "seismic_search_content",
    "seismic_list_teamsites"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Find the latest security one-pager approved for enterprise deals." }] });
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["seismic"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Find the latest security one-pager approved for enterprise deals." }],
  tools,
});

// Execute the tool call with the user's vaulted Seismic credential
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["seismic"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Find the latest security one-pager approved for enterprise deals." }],
  tools,
});

// Tool call runs with the user's vaulted Seismic credential
await sk.tools.executeTool(msg.content, "user_123");
import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["seismic"] }, pageSize: 100,
});

const agent = new Agent({
  name: "seismic_agent",
  model: "gemini-2.5-pro",
  instruction: "Manage Seismic for the signed-in user.",
  tools,
});

await agent.run("Find the latest security one-pager approved for enterprise deals.");
Try these prompts
Copy any prompt into your agent. Each maps directly to a Seismic tool. Click to copy, paste into your agent, done.
Find content
Copy the prompt
Copied
Find the latest security one-pager for enterprise.
Copy the prompt
Copied
Which case studies are approved for fintech?
Copy the prompt
Copied
Search the library for the Q3 pricing deck.
Manage files
Copy the prompt
Copied
Copy this library item into my workspace.
Copy the prompt
Copied
Create a folder for the Globex deal.
Copy the prompt
Copied
Which of my files are out of date?
Approvals
Copy the prompt
Copied
What is waiting on my approval?
Copy the prompt
Copied
Approve the enterprise one-pager.
Copy the prompt
Copied
Which content is stuck in review?
SEE HOW AUTH WORKS
Your users connect once. Their Seismic credentials stay vaulted, every call is scope-checked, and every action is logged.
1
Authorize
Your user connects
Seismic
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Seismic
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Seismic
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Seismic
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other crm & sales connectors.
People Ops and HR teams
New Hire Provisioning Agent
Open-source Python template. Creates or detects the hire in Deel, provisions their Workspace account, builds the Notion onboarding page, posts the welcome.
People Ops and HR teams
PTO & Leave Request Agent
Open-source Python template. Resolves the employee in Deel, validates against their real entitlement, submits the request for approval, blocks the calendar.
Engineering Teams
Incident Response Agent
Open-source Python template. Triggers the PagerDuty page, opens the Jira incident, notifies the on-call Slack channel, and drafts the Confluence postmortem.
GTM and RevOps Teams
Competitive intelligence briefing agent
Scans Gong calls for competitor mentions, matches each one to its Notion battlecard, and DMs every affected rep a single Slack digest per cycle. Every call runs as the PMM who owns the briefing, never a shared bot.
Test other agents
See the same per-user auth pattern across other crm & sales connectors.
GTM
CRM AI agent
Turn each Granola call transcript into a HubSpot record update, a drafted Gmail follow-up, and a Slack recap.
SALES
Deal intelligence agent
Score Gong call risk with an LLM, cross-reference the Attio record, and DM each owner their at-risk deals in Slack.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
A shared key ignores content permissions
A shared Seismic token looks fine in a demo. In production it exposes content and approvals to every agent regardless of the rep's own access. Scalekit resolves the credential of the actual user who triggered the agent, so Seismic's own permissions still apply.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Seismic today. Ten connectors tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access Seismic as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Seismic OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Seismic?
Yes. Pass a tool name filter to listScopedTools so the sales agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Seismic.

What happens when a user revokes Seismic access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Does the agent respect Seismic permissions?
Yes. Every call runs as the authorizing user. Native roles, sharing settings, and scope restrictions in Seismic apply to each request, and actions log to the audit chain.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""seismic"": {
""url"": ""https://mcp.scalekit.com/seismic"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.seismic]
url = ""https://mcp.scalekit.com/seismic""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""seismic"": {
""url"": ""https://mcp.scalekit.com/seismic"",
""type"": ""http""
}
}
}