> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/developers/integrations/quickstart.md). # Quickstart GitBook’s developer platform allows you to build integrations that seamlessly connect GitBook to internal tools, third‑party services, custom workflows and more. {% stepper %} {% step %} ### Getting started You’ll need a GitBook account to start using the developer platform. If you don’t already have an account, you can sign up for free [here](https://app.gitbook.com/join). {% endstep %} {% step %} ### Create a personal access token After creating a GitBook account, you'll be able to create a personal access token in your [developer settings](https://app.gitbook.com/account/developer). This token represents your user in GitBook, and allows you to make API calls, create integrations, and publish them to any GitBook spaces you're a part of to test them. {% hint style="warning" %} As always with access tokens, this token is specific to your user and should not be shared for use outside of your personal account. {% endhint %} Once you have your personal access token, you'll want to understand the differences between the pieces of the GitBook Integrations Platform in order to start developing your first app. {% endstep %} {% step %} ### Install the GitBook CLI The [GitBook CLI](/docs/developers/integrations/reference.md) requires Node v18 or later. It can be installed from NPM using: ```bash npm install @gitbook/cli -g ``` #### Authenticate with your account Once you have the CLI installed, you can run the following command and authenticate yourself with your personal access token using the following command: ```bash gitbook auth ``` {% endstep %} {% step %} ### Create your integration You can bootstrap your first integration by running the following command in your terminal: ```bash gitbook integrations new ``` The prompts will ask you for a `name`, `title`, `organization`, and `scopes` for your integration. {% hint style="warning" %} In order to publish your integration, your integration must: * Include a unique `name` * Include an `organization` id that your authenticated user is a member of. {% endhint %} After bootstrapping your integration, you’re ready to open your integration in an IDE and start building. {% endstep %} {% step %} ### Develop your integration locally In order to [develop your integration](/docs/developers/integrations/development.md) on your local machine, you’ll first need to publish your integration. In the root of your integration, run: If you use an AI coding assistant, add GitBook’s [`build-integration`](https://github.com/GitbookIO/gitbook-skills/tree/main/skills/build-integration) skill. It gives your assistant integration-specific guidance. 1. In your integration repository’s root directory, run: ```bash npx skills add GitBookIO/gitbook-skills ``` 2. Start a new agent session after the installation completes. 3. Ask your assistant to read the `build-integration` skill before building your integration. ```bash gitbook integrations publish ``` This will publish your integration to GitBook, and return a link with which you can install your integration. After installing your integration into your organization, space, or site, you can then run the development command to work on your integration locally. Return to your integration on your local machine, and in the root of the integration, run the following development command: ```bash gitbook integrations dev ``` After running the development script, you’re ready to start building your integration. Any changes made in your local version of the integration will be sent to the space you have your integration installed in. You’ll also be able to see logs in your console where applicable. {% endstep %} {% step %} ### Install and use your integration Once you’re ready to start using your integration in GitBook, you’ll need to install your integration into a space or site. You can find your integration’s install link returned in your terminal after publishing your integration with the `gitbook integrations publish` command. {% endstep %} {% endstepper %} ### Continue building your integration Continue with one of these integration guides:

:puzzle-piece:

Create interactive blocks

Build a custom block with a button that updates its text./spaces/2SyQSbIa1iYS7z6Dx5di/pages/KjMg5KpVuCoy8cBMeZQR

:bell:

Receive webhook notifications

Receive external events and handle them in your integration./spaces/2SyQSbIa1iYS7z6Dx5di/pages/OU70FDTSaoxYJ1j88iCm

:globe:

Handle an HTTP request

Return a JSON response from your integration’s public endpoint./spaces/2SyQSbIa1iYS7z6Dx5di/pages/HqfdsRiDAPttZ4B4m2h4
### Explore the integration platform

:sliders:

Configure your integration

Define your integration’s metadata, scopes, blocks, and settings./spaces/2SyQSbIa1iYS7z6Dx5di/pages/AHSnlbVtNiu2LbaUQ1JA/spaces/2SyQSbIa1iYS7z6Dx5di/pages/M46X8Qp6VKYd78tOOfDe/spaces/2SyQSbIa1iYS7z6Dx5di/pages/qUUhbveADO2RbiC3fhat

:puzzle-piece:

Build components

Create custom blocks with ContentKit and add interactive behavior./pages/M46X8Qp6VKYd78tOOfDe/spaces/2SyQSbIa1iYS7z6Dx5di/pages/WlSC8EW1d53AlhIt5VGM/spaces/2SyQSbIa1iYS7z6Dx5di/pages/NlYKQXxZ0x7lLCu2TPtU/spaces/2SyQSbIa1iYS7z6Dx5di/pages/KjMg5KpVuCoy8cBMeZQR

:rocket:

Publish your integration

Publish, install, and submit your integration for review./pages/RJdVRGBKuleXc5XdL73p/spaces/2SyQSbIa1iYS7z6Dx5di/pages/RJdVRGBKuleXc5XdL73p/spaces/2SyQSbIa1iYS7z6Dx5di/pages/l68HvDxlLrJQn16DCpxN/spaces/NkEGS7hzeqa35sMXQZ4X/pages/Prdad2Ahkhurtc9aMFEO
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://gitbook.com/docs/developers/integrations/quickstart.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.