Slab

This connector uses the Slab GraphQL API (https://api.slab.com/v1/graphql). Schema reference: https://studio.apollographql.com/public/Slab/variant/current/schema/reference

Setup:

1. Slab's API is available on the Business and Enterprise plans only.
2. In Slab open Team Settings → Developer and copy the API token.
3. Set SLAB_API_TOKEN.

Authentication: Authorization: Bearer ${SLAB_API_TOKEN}.

What the token can see: the API acts as the Slab Bot user. A post or topic Slab Bot has no access to is missing from every result — if something you expect is not there, give Slab Bot access to it in Slab.

Workflow:

1. slab_search_posts to find posts by text (cursor-paginated: pass pageInfo.endCursor back as after), or slab_list_topics → slab_get_topic_posts to browse.
2. slab_get_post with a post ID for the full post.
3. slab_create_post to add a new, empty post, optionally inside a topic.

Post content is Quill Delta JSON, not Markdown: content is a list of { insert, attributes } operations — the text is the concatenation of the insert strings, formatting sits in attributes. Writing content goes through updatePostContent(id, delta) with a Delta change (retain / delete / insert), which you can send with slab_graphql_mutation.

Topics = folders: posts live in topics, which can be nested (parent).

Beyond the typed tools: every GRAPHQL adapter gets slab_graphql_query / slab_graphql_mutation for any operation in the schema reference above (users, comments, updatePost, addTopicToPost, syncPost for mirroring an external Markdown document, …).

Out of scope here: integrations, billing, workspace export.