Integration · Docs and data
AI agents for Slab
Search a Slab knowledge base, read posts and topics, create posts, publish Markdown as synced posts, and publish, archive or file posts under topics, through Slab's GraphQL API as the workspace's Slab Bot user.
- Actions
- 8
- Read
- 4
- Write
- 4
Actions
What your agents can do in Slab
8 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 4
Look things up. Nothing changes.
Search Slab
Searches posts, topics, people and comments by keywords, best match first, up to 20 a page.
Get a post
Reads one post by its ID (the last part of its slab.com/posts/ link, after the final dash).
List topics
Lists every topic (Slab's folders) the bot can see, with id, name, privacy and its parent topic's id.
Get a topic and its posts
Reads one topic by ID: its name, privacy, parent, subtopics and the posts filed under it (id, title, published and updated times).
Write 4
Create, change or send.
Create a post
Creates a new blank post with a title, optionally filed under a topic and started from a template.
Publish Markdown as a synced post
Creates or updates a read-only Slab post whose content is Markdown (or HTML) kept somewhere else, keyed by your own external_id: sending the same id again replaces the content.
Publish, archive or share a post
Changes a post's state: publish or unpublish it, archive or restore it, or set who its link works for (INTERNAL, INTERNAL_VIEW, PUBLIC, PUBLIC_EDIT, DISABLED).
File a post under a topic
Adds a topic to a post (a post can be in several topics).
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your Slab account.
What you enter
- API token
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Slab data
Ask a question in plain words. The agent can search Slab, get a post or list topics in Slab, then answers with what it found.
- 02
Let an agent update Slab
Have the agent create a post or publish Markdown as a synced post in Slab as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Slab and Slack: it can search Slab in Slab and post a summary to a Slack channel in the same run.
FAQ
Slab and MyDeepAgents
Can MyDeepAgents connect to Slab?
Yes. The Slab connector has 8 actions: 4 read and 4 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Slab?
Paste an API key from your Slab account. You'll need: API token. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Slab without asking?
Only if you let it. Each of the 4 actions that change data can be set to wait for a person's approval before it runs.
Can I use Slab in workflows as well as agents?
Yes. Every Slab action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Slab to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.