The ChatBotKit SDK for NextAuth.js enables passwordless email authentication that integrates directly with ChatBotKit. This allows you to authenticate users without building separate user management infrastructure.
This SDK provides two adapters for different use cases:
Use ChatBotKitPartnerAdapter when you want each user to have their own isolated ChatBotKit sub-account:
Use ChatBotKitContactAdapter when you want all users to be contacts within a single ChatBotKit account:
Authentication is complex and risky to build yourself. This SDK lets you skip all of that.
Instead of spending weeks building and maintaining authentication infrastructure, you can:
Add the SDK to your project using npm:
npm install @chatbotkit/nextauth next-auth
Use this approach when each user needs their own isolated ChatBotKit environment:
import {
ChatBotKitEmailProvider,
ChatBotKitPartnerAdapter,
MemoryStore,
} from '@chatbotkit/nextauth/partner'
const nextAuthConfig = {
adapter: ChatBotKitPartnerAdapter({
secret: process.env.CHATBOTKIT_API_SECRET,
// Use Redis or another persistent store in production
store: new MemoryStore(),
// Control user lifecycle
autoCreateUser: false,
autoUpdateUser: true,
autoDeleteUser: false,
}),
providers: [
ChatBotKitEmailProvider({
async sendVerificationRequest({ identifier, token }) {
await sendEmail({
to: identifier,
subject: 'Sign in to your account',
text: `Your verification code is: ${token}`,
})
},
}),
],
session: {
strategy: 'jwt',
},
callbacks: {
async session({ session, token }) {
session.user = token.user
return session
},
async jwt({ token, user }) {
if (user) {
token.user = user
}
return token
},
},
pages: {
signIn: '/signin',
signOut: '/signin',
verifyRequest: '/verify',
},
debug: !!process.env.DEBUG,
}
export default nextAuthConfig
Use this approach when users are contacts within a single ChatBotKit account:
import {
ChatBotKitContactAdapter,
ChatBotKitContactEmailProvider,
ContactMemoryStore,
} from '@chatbotkit/nextauth/contact'
const nextAuthConfig = {
adapter: ChatBotKitContactAdapter({
secret: process.env.CHATBOTKIT_API_SECRET,
// Use Redis or another persistent store in production
store: new ContactMemoryStore(),
// Control contact lifecycle
autoCreateContact: true,
autoUpdateContact: true,
autoDeleteContact: false,
}),
providers: [
ChatBotKitContactEmailProvider({
async sendVerificationRequest({ identifier, token }) {
await sendEmail({
to: identifier,
subject: 'Sign in to your account',
text: `Your verification code is: ${token}`,
})
},
}),
],
session: {
strategy: 'jwt',
},
callbacks: {
async session({ session, token }) {
session.user = token.user
return session
},
async jwt({ token, user }) {
if (user) {
token.user = user
}
return token
},
},
pages: {
signIn: '/signin',
signOut: '/signin',
verifyRequest: '/verify',
},
debug: !!process.env.DEBUG,
}
export default nextAuthConfig
Create pages/api/auth/[...nextauth].js:
import NextAuth from 'next-auth'
import nextAuthConfig from '../../../nextauth.config.js'
export default NextAuth(nextAuthConfig)
Add your ChatBotKit API secret to .env:
CHATBOTKIT_API_SECRET=your_api_secret_here
| Feature | Partner Adapter | Contact Adapter |
|---|---|---|
| User isolation | Complete (separate sub-accounts) | Partial (shared account, individual contacts) |
| Resource sharing | None (each user has own resources) | Full (all contacts share bots/datasets) |
| API type | Partner API | Standard API |
| User identity | Separate ChatBotKit accounts | Contacts within single account |
| Best for | SaaS, white-label, multi-tenant | Chat apps, support systems, communities |
A complete working example demonstrating passwordless authentication with the ChatBotKit Partner API can be found in the partner-auth example.
For comprehensive information about the ChatBotKit NextAuth SDK, including detailed documentation on its functionalities, helper methods, and configuration options, please visit our type documentation page.
If you find a bug or would like to contribute to the ChatBotKit SDK, please open an issue or submit a pull request on the official GitHub repository.