# Getting started

> Create an agent, give it knowledge and tools, and deploy it to Slack.

Source: https://docs.runbear.io/getting-started

Last updated: 2026-08-26

This guide takes an empty Runbear organization to an agent answering questions in
a Slack channel.

## Before you begin

- A Runbear account. Sign up at [runbear.io](https://runbear.io).
- Permission to install apps in your Slack workspace, or an admin who can approve
  the installation.

## 1. Create the agent

Open **Agents** in the dashboard and select **Create Agent**. Give it a name that
says what it is for, such as `HR Helper`, then choose how it should work:

| Choice       | What you get                                                                      |
| ------------ | --------------------------------------------------------------------------------- |
| **Standard** | The current runtime. Recommended unless you have a reason to pick otherwise.      |
| **Classic**  | The previous engine. Faster and sufficient for simple question-and-answer agents. |

If your organization is on HIPAA mode, the Standard option is labeled accordingly
and the other runtimes are marked as not covered. See
[Agent settings](/agents/settings.md) for what the mode changes.

## 2. Write the instructions

Open the **Instructions** tab and describe what the agent does, who it serves, and
what it should refuse. Instructions are stored as named blocks, so keep one
subject per block rather than writing a single long page.

A first block for an HR agent might read:

> You answer employee questions about company policy using the HR handbook. Quote
> the relevant section. If the handbook does not cover the question, say so and
> suggest contacting the People team rather than guessing.

[More about instructions](/agents/instructions.md)

## 3. Connect knowledge, tools, or both

Open **Knowledge** and connect the source that holds the answers. Notion,
Confluence, Google Drive, Slack, SharePoint, and public websites sync
automatically; you can also upload files directly. The first sync runs
immediately and later syncs are incremental.

Open **Tools** if the agent needs to do something rather than answer from
documents, such as creating a Linear issue or looking up a HubSpot contact.

Knowledge answers "what does our documentation say", tools answer "what is true
right now" and "do this for me". Most agents use both.

[Knowledge sources](/agents/knowledge/overview.md) · [Tools](/agents/tools/overview.md)

## 4. Try it before anyone sees it

Open **Improve & Try** and ask the agent the questions you expect real users to
ask. Wrong answers here are usually missing knowledge or vague instructions, and
both are faster to fix now than after the agent is live.

[More about testing](/agents/testing.md)

## 5. Deploy to Slack

Open the **Chatbots** tab and select **Connect** on the Slack tile, then follow the
installation prompts. When the workspace is connected, invite the bot to a channel
and mention it:

```text
@Runbear What is our parental leave policy?
```

[Slack setup in detail](/channels/slack.md)

## What to do next

- Deploy the same agent to [Microsoft Teams](/channels/microsoft-teams.md),
  [Discord](/channels/discord.md), [HubSpot](/channels/hubspot.md), or
  [Zendesk](/channels/zendesk.md).
- Run it without being asked, on a schedule or an incoming event, with
  [triggers](/triggers.md).
- Watch what it costs on the [billing and credits](/administration/billing-and-credits.md) page.
- Restrict who can use it in [agent settings](/agents/settings.md).