Using site:script:inject scope for a Private Integration to embed an AI Chatbot #1013
Unanswered
hasitparmar-snyk
asked this question in
0. General bugs and questions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm currently working on adding an AI-powered chatbot to my product's documentation site, which is hosted on GitBook. My goal is to embed this chatbot directly into our GitBook pages to provide real-time assistance to our users.
From my investigation, it appears the most suitable way to achieve this is by building a custom GitBook integration that leverages the
site:script:inject
scope. I've studied the existing marketplace integrations like Crisp, Intercom, and Help Scout, which all utilize this scope to dynamically inject their chat widgets. My plan involves creating a similar integration that injects our AI chatbot's script and initialization code.My specific challenge and question is regarding the
site:script:inject
scope when building a private integration.According to the GitBook documentation (Developer Reference - Scopes), it states that
site:script:inject
is "restricted for use by GitBook staff only for security reasons."Given this, I'm trying to understand:
Is it possible for me to use the
site:script:inject
scope within a private GitBook integration for my own organization's use cases? My intention is purely to add an internal AI chatbot to our own documentation, not to create a public marketplace integration.If it's not directly possible, what would be the recommended alternative approach to inject a custom AI chatbot script into GitBook documentation pages, especially for private, internal use?
Thank you in advance for your insights!
Beta Was this translation helpful? Give feedback.
All reactions