Some links on this page are affiliate links. If you buy through them, we may earn a commission at no extra cost to you.
· By IMRAN HOSSAIN
Quick answer: Use Readwise as the central highlights hub for Kindle, Apple Books and Pocket, export Goodreads or StoryGraph libraries when needed, and choose Zapier or Make for lightweight automations; direct, two‑way live sync between StoryGraph and Goodreads is not available, so expect one source of truth and periodic imports. StoryGraph vs Goodreads
- Key takeaways: Readwise centralises highlights, Kindle exports and Amazon Your Highlights are the raw source, StoryGraph imports CSVs while Goodreads supports more legacy API and CSV flows, and Zapier/Make can automate copies but not full two‑way live progress sync.
- Decide your source of truth first: device ecosystem (Kindle/Kobo/Apple) or reading‑note hub (Readwise/Notion).
- Watch for duplicate editions, date mismatches and privacy permissions when connecting third parties.
Which major integrations work with StoryGraph and Goodreads?
Both StoryGraph and Goodreads accept imports and connect to a handful of third party services, but the exact paths differ: Goodreads has long supported CSV import/export and an API for libraries, while StoryGraph focuses on CSV imports and internal analytics without a public write API.
Goodreads supports an export of your entire library as a CSV and has a documented API for reading data, which makes it easier for older integrations to pull library lists. StoryGraph provides import tools for Goodreads CSVs and limits for tags and custom fields; you can import reading dates, ratings and shelves but edition matching sometimes fails. Because neither app offers a seamless, native two‑way live sync, third‑party tools like Readwise, Calibre or federated alternatives such as Bookwyrm are commonly used to bridge data, with Readwise handling highlight aggregation and Calibre handling local ebook metadata management. If you plan to migrate or run both in parallel, choose one app as your primary logging ground to avoid conflicts.
How do Kindle highlights reach StoryGraph or Goodreads?
Kindle highlights do not send directly to StoryGraph or Goodreads; you must export them through Amazon, Readwise, or a third‑party tool.
Amazon keeps your highlights accessible via Amazon Your Highlights (the read.amazon.com/highlights page), and you can copy or export them manually. For automation, Readwise connects to Amazon Kindle (including Kindle cloud) and pulls highlights automatically into Readwise Reader or Readwise Books, then exports notes in CSV or integrates into Notion, Obsidian, or Evernote. If you prefer a local workflow, Calibre can extract metadata from ebooks you own but does not harvest highlights from Kindle cloud. For Goodreads, many users copy key quotes into reviews or private notes manually because Goodreads has no standardized highlights import. When you use Readwise you centralise highlights and then import or link derived CSVs to StoryGraph or attach notes to Goodreads entries; treat Readwise as the bridge not the final reading log unless you use Readwise Books as your tracker.
Is Readwise the best central hub for highlights?
Readwise is the most widely used central hub because it aggregates Kindle, Apple Books, Pocket, Instapaper and RSS highlights into one place and offers exports and connectors to note apps.
Readwise provides automatic syncing from Amazon Kindle, Apple Books, Pocket and Instapaper, plus manual import for other sources. Readwise can export highlights as CSV or push to Notion and Obsidian, and it keeps your highlights searchable. Compared with using ad hoc CSV exports, Readwise reduces manual work and retention loss. If you want a single place to review highlights, Readwise Reader or Readwise Books makes that workflow consistent. Note that Readwise is centered on highlights and review features, not detailed reading stats; for time read and pages, pair Readwise with StoryGraph or Goodreads. Readwise also supports developer access and an API for exports and automations, which makes it useful in Zapier and Make flows when you need programmatic exports to StoryGraph or other services.
What are the best workflows for Kobo and Apple Books?
Kobo and Apple Books do not feed Goodreads or StoryGraph directly; use their export features or Readwise to centralise highlights and metadata first.
Apple Books stores highlights locally on your device and, when enabled, synchronises them through iCloud, but there is no single export button to push highlights to trackers. Readwise can connect to Apple Books to capture highlights on macOS and iOS. Kobo holds annotations in its cloud for Kobo devices and the Kobo app; you can export annotations manually or use Readwise if supported in your region. After collecting highlights with Readwise or manual export, export a CSV with your reading dates and ratings to import into StoryGraph or use Goodreads CSV import. For ebook files you manage yourself, Calibre helps normalise metadata including editions and ISBNs before import. If your reading happens mostly on iPad or phone, see the device guidance in our Kindle vs iPad guide for choosing a primary ecosystem.
Can you use APIs and Zapier to automate StoryGraph and Goodreads updates?
Yes for partial automation: Zapier and Make can move data between services, but Goodreads write APIs are limited and StoryGraph has no public write API for full sync, so automation is constrained to exports, notifications and partial updates.
Zapier and Make are useful for automating tasks such as saving new Readwise highlights to Notion, sending a Slack message when you finish a book, or appending CSV rows for weekly backups. However, you cannot rely on Zapier to push live “currently reading” progress into StoryGraph unless you use an approved integration path from the app. A practical Zapier workflow is: Kindle highlights to Readwise, Readwise to Notion, Notion to a CSV that you manually import into StoryGraph. If you need deeper automation examples for CRM‑style workflows or recipe patterns, see automation case studies like the Zapier automation guide. Use Make or self‑hosted scripts that read Readwise exports for advanced users who can manage API keys and rate limits.
How can you keep reading progress in sync across devices?
Keep one device ecosystem as the single source of truth for progress, enable device cloud sync, and only copy progress data into trackers at controlled intervals to avoid conflicting dates.
Reading progress is best maintained by a single device family: for example, use Kindle devices and the Kindle app as your progress master because Amazon stores location and last page in the cloud. If you also read on Kobo or Apple Books, manually record end dates and pages in your chosen tracker after finishing each session. Automations can append a reading session log to Notion or Google Sheets via Readwise exports, but they rarely update the “currently reading” status live on StoryGraph or Goodreads. To keep progress consistent, export reading session summaries weekly and import them to StoryGraph; for Goodreads, update the “progress” field manually or with an approved third‑party tool that supports Goodreads write operations. This reduces duplicated date edits and mismatched page counts across platforms.
How does StoryGraph import/export compare to Goodreads?
StoryGraph imports Goodreads CSVs but treats ratings, dates and tag fields differently, offering stronger analytics while Goodreads retains broader social features and legacy API access.
Goodreads exports include shelf, title, author, date read and rating in a familiar CSV format, and many migration tools were built around that format. StoryGraph can import that CSV, map ratings, and compute its signature statistics such as mood, pace and genre breakdown. StoryGraph emphasises reading stats and mood tagging, which is useful for analytics, while Goodreads focuses on social discovery and discussion. If you import a Goodreads CSV into StoryGraph you will often need to tidy edition mismatches and reassign custom shelves. For ongoing parallel use, run periodic exports from Goodreads and import to StoryGraph, or keep StoryGraph as your analytic mirror and Goodreads as your social front end. For note sync you will still rely on Readwise or manual copy into Goodreads reviews or StoryGraph notes.
What decision framework should you use to choose a sync setup?
Choose a single source of truth, pick an aggregator for highlights, and decide whether you need live two‑way writes or periodic imports, because most integrations support only one or the other.
Decision steps: 1) Pick source of truth: device ecosystem (Kindle/Kobo/Apple) if you care about progress, or Readwise/Notion if highlights matter more. 2) Determine synchronization style: live two‑way write (rare, limited to certain apps) versus periodic import/export (reliable and widely supported). 3) Evaluate automation cost and privacy: use Readwise or self‑hosted scripts if you want continuous sync; prefer manual CSVs if you want minimal third‑party access. A hidden cost to watch is time spent reconciling duplicates and editions; migration and ongoing cleanup can add hours per month unless you standardise on one edition source. Goodreads is better if you need social features and legacy API hooks, while StoryGraph is better for analytics and mood tracking. Use Zapier or Make for notifications and backups, but not as a substitute for a native two‑way sync.
How much will integrations cost in 2026?
Costs depend on choices: device ecosystems are free to use, Readwise and automation platforms have subscription tiers, and professional automation or developer scripts may add hosting costs.
| Option | Price range | Best for | Key strengths | Main limits |
|---|---|---|---|---|
| Readwise (Readwise Reader / Readwise Books) | Subscription (varies) | Highlight centralisation | Auto sync from Kindle, Apple Books, Pocket | Subscription cost, focused on highlights |
| Amazon Kindle | Free app, paid ebooks | Primary reading device | Cloud sync of progress, Your Highlights | No direct tracker export |
| StoryGraph | Free and paid tiers | Reading analytics | Detailed stats, CSV import | No public write API |
| Goodreads | Free | Social reading | Large discovery community, CSV export | Limited modern integrations |
| Zapier / Make | Free tiers, paid tiers | Automations and notifications | Many connectors, low code | API limits, cannot force two‑way writes |
Note: subscription prices change; always check each vendor’s official pricing page for current plans and limits. Goodreads was founded in 2006, which explains its extensive legacy ecosystem (Wikipedia, 2026), but also its reliance on older APIs.
Which one fits you?
Choose based on how you read and what you value: highlights, progress, or community.
- Beginner reader: Use StoryGraph for stats and import a Goodreads CSV occasionally, because StoryGraph analyses are easier than managing automations. See the main comparison StoryGraph vs Goodreads.
- Tight budget: Use Goodreads plus manual Kindle exports, because both are free and avoid subscription fees; export CSVs for backups and import into StoryGraph when you want analytics.
- Power note taker: Use Readwise as highlights hub and push highlights to Notion or Obsidian for longform notes; see our note-taking sync guide Connect OneNote and Notion for similar patterns.
- Automation enthusiast: Use Readwise, Make and small serverless scripts; consult automation patterns in our Zapier automation guide for similar workflows.
Who should NOT use this system: readers who want instantaneous two‑way sync between StoryGraph and Goodreads should not expect that capability; instead pick one as primary and mirror selectively.
Worked examples with costs and steps
Example: A solo creator reading 5 books a month who wants highlights in Notion and statistics in StoryGraph would subscribe to Readwise, export monthly CSVs to StoryGraph, and use a Notion integration for highlights. This setup minimises manual copy and centralises highlights.
Example: A budget reader who reads 1 book per month can keep everything free by using Kindle for reading, manual export of highlights via Amazon Your Highlights, and quarterly CSV imports into StoryGraph or Goodreads. For a middle ground, use Readwise for highlights only when you hit 10+ highlights a month to justify the subscription.
Practical checklist before you connect anything
- Decide your source of truth: device or highlight hub.
- Export current libraries from Goodreads and StoryGraph as CSV backups.
- Check privacy settings and revoke permissions you do not want third parties to have.
- Standardise editions and ISBNs for new imports using Calibre or manual checks.
- Set a schedule for periodic imports and duplicates cleanup.
- Document your workflow in Notion or Obsidian so you can repeat it later; if you use Obsidian, compare tools in our Obsidian vs xTiles and Obsidian vs Craft writeups.
Common mistakes and how to avoid them
Many users expect seamless two‑way syncing and are surprised when duplicate editions, mismatched dates and lost highlights appear; avoid this by centralising writes and performing regular cleanups.
Common errors: 1) Treating StoryGraph and Goodreads as equal writable mirrors; pick one writer. 2) Importing different editions without normalising ISBNs; fix this with Calibre metadata or by choosing the edition you own. 3) Granting broad third‑party permissions without reviewing privacy policies; revoke unnecessary tokens. 4) Expecting Zapier to update “currently reading” live; use scheduled exports instead. If you want automated backups, set a Zapier or Make flow to save CSV exports of Readwise or Goodreads to Google Drive on a weekly schedule, using Zapier alternatives if you prefer the workflows in our Zapier Alternatives guide.
How to export and import without losing data?
Export full CSVs from Goodreads and Readwise, use Calibre to normalise metadata, then import into StoryGraph and check duplicates before finalising import.
Step 1: Export Goodreads library via the account settings export function. Step 2: Export Readwise highlights and save as CSV or JSON. Step 3: Use Calibre to align metadata such as ISBN and edition; Calibre is useful when you own ebook files. Step 4: Import to StoryGraph using its CSV import and map fields manually to avoid dropping dates or ratings. Always keep a backup copy of your CSVs in cloud storage. If you want to also keep longform notes, push Readwise highlights into Notion or Obsidian automatically; our Headway Review 2026 discusses other summary app workflows that pair well with Readwise exports.
Where should I put my longform notes and summaries?
Store longform notes and summaries in a dedicated note app such as Notion or Obsidian and use Readwise to push highlights into those notes automatically for review and tagging.
Readwise offers direct integrations to Notion and Obsidian that append highlights and maintain context. Notion is convenient for structured databases of books, tags and summaries, while Obsidian is better for backlinking and local vault control. If you prefer quick summaries, services like Headway or Blinkist handle condensed content, but they do not replace your primary highlights archive. For connecting notes with task systems or teams, consider a linked workflow to ClickUp or Notion; compare team task approaches in our ClickUp vs Notion guide when you bring reading into workflows for collaborators.
Does Readwise import Goodreads highlights and notes?
Readwise does not provide a one‑click native import of Goodreads highlights and notes automatically.
Goodreads exports your library CSV but it does not expose a standard, complete quotes/highlights export that Readwise can ingest out of the box, so the usual path is manual or semi‑automated: export your Goodreads library for metadata, then extract quotes or notes from Goodreads pages or your reviews, format them into a Readwise import CSV or JSON, and upload to Readwise. Typical steps are: 1) download Goodreads library CSV from Account Settings; 2) copy or scrape quotes from your Goodreads quotes or reviews (Goodreads does not include quotes in the library CSV); 3) build a CSV with columns Readwise expects (title, author, highlight text, note, location/page, date); 4) import to Readwise via its CSV/JSON import or API. This suits users who want to centralise scattered quotes; casual users may prefer manual copy/paste for a handful of highlights while power users use scripts to convert Goodreads pages into a Readwise import file.
Can I use Zapier or Make to update my StoryGraph reading status automatically?
No, Zapier and Make cannot reliably write live reading status into StoryGraph because StoryGraph provides no public write API for status updates.
Zapier and Make remain useful for preparatory automation: they can detect events (for example, a Kindle finished notification or a Readwise finished highlight) then build a properly formatted CSV row or add an entry to a Google Sheet or Notion database that you later import into StoryGraph. Practical workflows include: 1) a Zap that appends finished‑book rows to a Google Sheet with columns StoryGraph accepts; 2) scheduled runs that export the sheet as CSV and email it to you or store it in cloud storage for one‑click import; 3) notifications or Slack messages for manual confirmation. This approach avoids conflicting writes and preserves StoryGraph as the authoritative record while automating repetitive preparation tasks. For users who must have programmatic updates, self‑hosted scripts that simulate CSV imports and prompt for manual upload are the most reliable option.
What is the best way to merge my Goodreads and StoryGraph libraries without losing data?
Export both Goodreads and StoryGraph as CSVs, normalise metadata with Calibre, deduplicate carefully, and import the cleaned file into the target app.
Recommended stepwise approach: 1) Export Goodreads library and StoryGraph export as CSV backups. 2) Use Calibre or a spreadsheet to normalise ISBNs, titles and author name formats so edition matching behaves. 3) Merge rows and mark duplicates using a composite key such as ISBN plus title plus publication year. 4) Preserve important fields (date started, date finished, rating, review, private notes) by mapping all columns to your target app. 5) Import the cleaned CSV into StoryGraph or Goodreads and verify a small sample before full import. Keep original exports in cloud storage in case you need to revert. If you want a step‑by‑step migration walkthrough specific to moving Goodreads data into StoryGraph, follow our detailed migration guide for practical screenshots and mapping tips: How to Migrate from Goodreads to StoryGraph (Step-by-Step, 2026). This workflow suits readers who want to retain history, ratings and reading dates while avoiding edition fragmentation.
How do I export my Goodreads library as CSV or other formats for import into StoryGraph?
From Goodreads, use Account Settings Export Library to download a CSV containing your shelves, dates and ratings suitable for StoryGraph import.
Steps to export: sign into Goodreads, open Account Settings, choose the Import/Export section and click Export Library to download a CSV file. That CSV includes title, author, ISBN, user shelves, date read, date added and rating, which StoryGraph can map during import. Note that Goodreads does not include quote/highlight exports in the library CSV; quotes and review texts are separate and may require manual copy or scraping. If you need quotes or annotated text, export reviews individually or use a scraping approach to collect quotes into a CSV with columns StoryGraph or Readwise expects. Before importing into StoryGraph, check date formats (YYYY-MM-DD recommended), clean empty columns, and ensure numeric ratings are within expected ranges. For advanced imports preserve ISBNs and edition data to reduce duplicate editions on import.
How can I keep reading progress in sync across Kindle, Kobo, and StoryGraph?
You cannot maintain live cross‑device progress sync; pick one device cloud (Kindle or Kobo) as the source of truth and push periodic summaries into StoryGraph.
Practical setup: choose your primary device family (for example Kindle if you use Kindle devices and apps) and enable cloud sync so progress and last location are saved. Use automation to log book sessions into a central sheet or database, either via Readwise for highlights or by logging “finished” events detected from reading apps, and schedule a weekly CSV export that you import to StoryGraph. For cross‑platform reading, track progress fields you can export: title, timestamp, percent complete, pages or location. If you need page counts, convert Kindle locations to pages using book metadata or use reader app APIs where available to translate locations. This approach reduces conflicts: the device cloud keeps accurate in‑app progress, and StoryGraph receives regular, reconciled snapshots rather than conflicting live updates from several sources. It fits users who accept a short delay in StoryGraph reflecting the latest progress in exchange for consistency across devices.
How much do Readwise, StoryGraph, and Zapier/Make cost in 2026?
In 2026 each service offers a free tier plus paid plans; typical monthly costs range from free to roughly US 5 to 40 per service depending on features and billing cycle.
Common 2026 pricing patterns you can expect: Readwise Reader or Readwise Books typically offers a free trial and a paid Reader plan for power users (commonly in the US 5 to 10 per month range when billed monthly, lower when billed annually); StoryGraph continues to provide a fully free tier plus an optional premium subscription for extras (often around US 3 to 6 per month on annual billing); Zapier retains a free tier with limited tasks and paid tiers starting around US 20 to 30 per month for small automations, rising to US 50 to 100+ per month for professional needs; Make (Integromat) offers a free tier and paid plans that commonly start in the low double digits per month. Which plan suits you depends on volume: occasional readers can use free tiers, heavy highlighters and automation users will save time with mid‑tier Readwise and Zapier/Make plans, and teams may require higher Zapier/Make tiers. Always confirm current pricing and billing options on each vendor’s official pricing page before subscribing.
How to build a custom API integration to sync highlights between Kindle/Readwise and StoryGraph/Goodreads?
Build a custom integration by pulling highlights from Readwise using its API, transforming them, and importing them into StoryGraph via CSV or into Goodreads via its supported endpoints where available.
High level steps: 1) Register and secure API keys or OAuth tokens for Readwise and Goodreads and confirm StoryGraph import constraints. 2) Use Readwise’s API to fetch highlights programmatically (paginated endpoints returning book, text, note, location, created_at). 3) Transform the payload into the target schema: for StoryGraph produce CSV rows with title, author, highlight/note, date; for Goodreads check whether the Goodreads API accepts adding quotes or whether you must use CSV/review import or manual UI. 4) Store transformed records in a temporary datastore (JSON, S3 or a small database) and schedule a job to export CSVs for StoryGraph or to call a Goodreads endpoint. 5) Handle rate limits and retries, normalise editions using ISBN and clean text encoding. 6) Secure secrets, use token rotation and log actions for audit. Typical stack: a small serverless function (AWS Lambda, Cloud Run), a scheduler (cron or Cloud Scheduler), and a secure vault for API keys. Endpoint and auth checklist:
| Service | Typical Endpoint Type | Auth |
|---|---|---|
| Readwise | Highlights REST API (GET /highlights) | API Key / OAuth token |
| Goodreads | Limited public API; many write paths restricted | OAuth (varies) or CSV/manual import |
| StoryGraph | CSV import (preferred) or limited API | Manual upload or app token if available |
This approach suits builders who can manage authentication, transformation and scheduled exports; for most readers a CSV import flow is simpler and more robust than trying to force live writes into Goodreads or StoryGraph.
FAQ
Below are conversational answers to common voice queries about syncing StoryGraph and Goodreads.
Can StoryGraph import my Goodreads library?
Yes. StoryGraph supports importing a Goodreads CSV export, but you should clean up duplicate editions and check imported dates and ratings after import to avoid mismatches.
Will Kindle highlights sync automatically to StoryGraph?
No. Kindle highlights do not sync directly to StoryGraph; use Readwise or manual export from Amazon Your Highlights, then import highlights or reference them in your StoryGraph notes.
Is Readwise worth the cost for syncing highlights?
It is for readers who create many highlights and want automated aggregation and push to Notion or Obsidian; casual highlighters may prefer periodic manual exports instead.
Can Zapier update my StoryGraph reading status?
Not reliably. StoryGraph lacks a public write API for full status updates, so Zapier can handle exports and notifications but cannot fully automate live reading status changes into StoryGraph.
How do I merge two libraries from Goodreads and StoryGraph?
Export both libraries to CSV, normalise metadata with Calibre, remove duplicates and import the cleaned CSV into your target app; always keep backups before merging.
Will third‑party syncing risk my data privacy?
Yes, any third party you grant access to your Kindle, Goodreads or StoryGraph data can read that data. Review each service’s privacy policy and minimise permissions when possible.
Summary: Use Readwise as your highlights aggregator, pick one primary device ecosystem for progress, automate safe exports with Zapier or Make, and treat StoryGraph and Goodreads as complementary rather than two writable mirrors. For more on choosing between StoryGraph and Goodreads themselves, see our detailed comparison StoryGraph vs Goodreads.
External resources: check the Readwise pricing page for current subscription details and Amazon’s Your Highlights page to export Kindle highlights.