AI Chatbots

Chatbotkit, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Chatbotkit account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • AI Chatbots
  • Connects with a key
  • 11 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Chatbotkit is

ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.

You paste in a key from your own Chatbotkit account. It is kept encrypted, and you can withdraw it from inside Chatbotkit whenever you like.

How a run works

One message in, the work done in Chatbotkit.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Chatbotkit. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Chatbotkit account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

11 tools it already has

What it can do in Chatbotkit

These are the ready-made tools your AI employee already has in Chatbotkit. It is not limited to them, but it never has to be taught these.

  • Complete ConversationTool to send a message to a conversation and receive the bot’s reply. use after retrieving or initiating a conversation id.
  • Create IntegrationTool to create a new integration. use when you need to set up a support channel integration for a bot after collecting the integration details.
  • Create SkillsetTool to create a new skillset. use when you need to group multiple skills into a single reusable unit.
  • List BotsTool to retrieve a paginated list of all bots. use when you need to browse or manage multiple bots, and iterate pages via cursor.
  • List conversation messagesTool to list messages in a conversation with pagination. use after obtaining a conversation id to fetch messages page by page.
  • List ConversationsTool to retrieve a paginated list of conversations. use when you need to page through conversation history.
  • List DatasetsTool to list datasets. use when you need to browse or paginate through available datasets.
  • List IntegrationsTool to retrieve a list of trigger integrations. use when you need to browse or manage configured trigger integrations and iterate pages via cursor.
  • List PartnersTool to retrieve a list of all partner accounts associated with the main account. use when you need to view or manage all sub-accounts under your partner umbrella.
  • List SkillsetsTool to retrieve a list of all skillsets available in the system. use when you need to enumerate existing skillsets.
  • List TokensTool to retrieve a list of all api tokens. use when you need to audit or manage existing tokens.
Access, and who is in charge of it

You stay the boss of your Chatbotkit account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Chatbotkit account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Chatbotkit is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Chatbotkit and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

Questions people ask about Chatbotkit

Can an AI employee really work inside Chatbotkit?
Yes. It signs in to your own Chatbotkit account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Chatbotkit?
No. Nothing moves and nothing is replaced. Your records stay in Chatbotkit, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Chatbotkit account?
You paste in a key from your own Chatbotkit account. It is kept encrypted, and you can withdraw it from inside Chatbotkit whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Chatbotkit?
It has 11 ready-made tools in Chatbotkit today, among them Complete Conversation, Create Integration and Create Skillset. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Chatbotkit and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Chatbotkit and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Chatbotkit?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Chatbotkit is written down with what it did and when.