Skip to content

docs: Add Scalekit integration for authenticated tool calling#3956

Open
saif-at-scalekit (saif-at-scalekit) wants to merge 5 commits into
langchain-ai:mainfrom
saif-at-scalekit:add-scalekit-integration
Open

docs: Add Scalekit integration for authenticated tool calling#3956
saif-at-scalekit (saif-at-scalekit) wants to merge 5 commits into
langchain-ai:mainfrom
saif-at-scalekit:add-scalekit-integration

Conversation

@saif-at-scalekit
Copy link
Copy Markdown

Summary

Add Scalekit as a LangSmith integration under Developer tools.

Scalekit provides authenticated tool calling for AI agents — 60+ pre-built connectors
(Gmail, Slack, Salesforce, GitHub, Notion, etc.) with delegated OAuth, token management, and native LangChain
StructuredTool support. When LangSmith tracing is enabled, Scalekit tool calls appear as tool spans automatically.

Files changed

  • src/langsmith/trace-with-scalekit.mdx — new integration page (SDK adapter + MCP methods)
  • src/images/providers/light/scalekit.svg — provider icon (light mode)
  • src/images/providers/dark/scalekit.svg — provider icon (dark mode)
  • src/langsmith/integrations.mdx — added Scalekit card to Developer tools grid
  • src/docs.json — added nav entry

Testing

Code examples verified with traces received in LangSmith UI.
See scalekit-developers/agent-auth-examples#3 for the tested script.

References

Add Scalekit as a LangSmith integration under Developer tools.
Scalekit provides authenticated tool calling for AI agents with 60+
pre-built connectors and native LangChain StructuredTool support.

Files:
- trace-with-scalekit.mdx: integration page (SDK adapter + MCP methods)
- Provider icons for light and dark mode
- Integration card and navigation entry
@github-actions github-actions Bot added external User is not a member of langchain-ai langsmith For docs changes to LangSmith labels May 12, 2026
@github-actions
Copy link
Copy Markdown
Contributor

Thanks for opening a docs PR, saif-at-scalekit (@saif-at-scalekit)! When it's ready for review, please add the relevant reviewers:

  • @katmayb or @fjmorris (LangSmith)

@github-actions
Copy link
Copy Markdown
Contributor

❌ Import check failed

This PR contains imports from langchain_core that should be imported from langchain instead.

Detailed issues
Analyzing diff for import issues...
 Found 2 import issues:

File: src/langsmith/trace-with-scalekit.mdx
Line: 97
Issue: Import from langchain.messages instead of langchain_core.messages
Current:   from langchain_core.messages import HumanMessage, ToolMessage
Suggested: from langchain.messages import HumanMessage, ToolMessage
--------------------------------------------------------------------------------
File: src/langsmith/trace-with-scalekit.mdx
Line: 147
Issue: Import from langchain.messages instead of langchain_core.messages
Current:   from langchain_core.messages import HumanMessage, ToolMessage
Suggested: from langchain.messages import HumanMessage, ToolMessage
--------------------------------------------------------------------------------

 Found 2 import issues that need to be fixed.

Why this is a problem

The langchain package re-exports many modules and classes from langchain_core. When possible, imports should use langchain instead of langchain_core for:

  • Better user experience (single import source)
  • Consistency across documentation
  • Reduced cognitive load for users

How to fix

Replace the imports as suggested above. For example:

  • from langchain_core.messages import HumanMessage
  • from langchain.messages import HumanMessage

🤖 Automated check

This check is based on the latest analysis of langchain re-exports from langchain_core.

@saif-at-scalekit
Copy link
Copy Markdown
Author

Addressed the import issue that's pointed out by github actions.

Saif (saif-shines) and others added 2 commits May 12, 2026 19:01
Use the real S-mark path from scalekit-web-ui/public/scalekit-icon.svg
instead of the approximate stroke-based icon.
@saif-at-scalekit
Copy link
Copy Markdown
Author

Kathryn May (@katmayb) / Florence Morris (@fjmorris) – I’ve gone through other PRs and the contribution guidelines to this pull request. Since this is my first time working on this PR and on #3963, I may have missed a few things. Please let me know if there’s anything I can adjust to make this PR as clean as possible and straightforward for you to review and merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

external User is not a member of langchain-ai langsmith For docs changes to LangSmith

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants