Connect GitBook to Perplexity
Send GitBook users, organizations, insights traffics and 2 more data types to Perplexity on a schedule. Refresh as often as every 15 minutes.
Perplexity
What changed in our GitBook data this week?
Querying the GitBook data set in Coupler.io
How to connect GitBook and Perplexity
4 steps. You can preview the GitBook data in Coupler.io before anything reaches Perplexity.
Step 1 of 4
Connect GitBook
Enter your GitBook access token. You only do this once per account.
Step 2 of 4
Choose what to export
Pick the GitBook data you want in Perplexity.
Step 3 of 4
Connect Perplexity
In Perplexity, add a connector named coupler-io that runs the Coupler.io MCP server in Docker, then paste your personal access token.
Step 4 of 4
Set a schedule
Perplexity sees the data as of the last run. Run it as often as every 15 minutes.
Coupler.io made it easy to create dashboards and reports from different data sources. The sync is reliable and the user experience is amazing.
Take your data analytics to the next level
Sign Up with Google
Sign Up with MICROSOFT
SIGN UP WITH EMAIL
By signing up to Coupler.io, you agree to our Privacy Policy and Terms of Use.
Build your GitBook integrations with these destinations
Get the most of GitBook to Perplexity integration
Gather data
Understand data
Automate data
Act on data
5 data types, including Users, Organizations, Insights traffics, Contents and Org members.
With your GitBook access token, entered once when you add the connection.
No. The data stays in Coupler.io, and Perplexity queries it read-only when you ask a question. It can't edit or delete GitBook rows.
A Perplexity account and Docker. Perplexity reaches Coupler.io through a local MCP server that runs in Docker.
On a schedule you choose, from monthly down to every 15 minutes, depending on your Coupler.io plan.
Yes. Add more sources to the same data flow, for example 100ms or Amazon Seller Central, and join or append them before the data reaches Perplexity.
