- Home
- Resources
- Integrations
- Google Books
Google Books n8n integrationAutomate Google Books with n8n.
Book data belongs in your workflows, not in a browser tab. The Google Books n8n integration hands you 9 operations across 3 resources: volumes, bookshelves, and the volumes sitting on those shelves. No trigger node exists here, so a schedule or another app starts the run.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Google Books n8n integration actually do?
The Google Books node ships with n8n and gives a workflow a way into Google Books data and into the bookshelves attached to a Google account. It covers 9 operations spread over 3 resources: Volume, Bookshelf, and Bookshelf Volume. Looking up a title, pulling one book record by its identifier, filling a shelf, and reordering that shelf all become steps in a workflow instead of manual clicks.
Start with the lookup desk. A colleague drops a title into a form or a chat message, the workflow runs volume.getAll with that text as the Search Query, and the matching records come back as items. From there you can post a short answer into Slack or park the results in a sheet for later review. Nothing about the search is manual after the first setup.
Second pattern: a reading list that fills itself. Rows arrive in Google Sheets with a volume identifier per line, a Schedule Trigger walks the new rows, and bookshelfVolume.add puts each one on the right shelf. Run bookshelfVolume.move straight after and the shelf ends up in the order you want rather than the order things arrived.
Third pattern: reporting on what is already there. bookshelf.getAll lists the shelves for a user, bookshelfVolume.getAll reads what sits on one of them, and the output feeds a summary document in Google Docs. Teams that curate recommended reading run this weekly and stop wondering which shelf changed.
When the operation you need is not one of the 9 in the node, the HTTP Request node calls the API endpoint directly and reuses the same credential through predefined authentication. That keeps the workflow on one login instead of a second set of keys.
Two things to plan for. Reading operations respect Return All: leave it off and n8n stops at Limit, turn it on and n8n pages through the API until everything is back. And any field marked required in the node stops the execution when it arrives empty, so map it from a previous step or a fixed value. If you want the wider picture before committing, the n8n review covers how the platform behaves day to day, and the n8n training walks through building a workflow end to end.
How do you connect Google Books to n8n?
- 01
Pick your authentication method
The node accepts two credential types: OAuth2, which n8n recommends because it is easier to set up, and Service Account, the heavier option for cases that really need it. A credential is created once in the Credentials menu and then offered in the node dropdown in every workflow. On n8n Cloud, check whether the credential screen shows a Sign in with Google button: that is Managed OAuth2, and it skips the Google Cloud Console entirely.
- 02
Build the OAuth client in Google Cloud
Custom OAuth2 starts with a Google Cloud Console project and the APIs you need enabled on it. Then configure the OAuth consent screen: an App name, a User support email, and an Audience set to Internal for your own workspace or External for any Google account. Under Branding, add an authorized domain:
n8n.cloudfor the hosted service, or the domain of your own instance if you self-host. - 03
Wire the keys back into n8n
In APIs & Services, create an OAuth client ID of type Web application, give it a name you will recognize, then copy the OAuth Redirect URL shown in your n8n credential and paste it into Authorized redirect URIs. Google hands back a Client ID and a Client Secret; both go into the n8n credential, which you then save and reuse across workflows.
Every Google Books operation in the n8n node
The Google Books node exposes 9 operations across 3 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
| Resource | Get | Get Many | Add | Remove | Clear | Move |
|---|---|---|---|---|---|---|
| Bookshelf | ✓ | ✓ | ||||
| Bookshelf Volume | ✓ | ✓ | ✓ | ✓ | ✓ | |
| Volume | ✓ | ✓ |
Operations index
Bookshelf
2 operationsGet a bookshelf
bookshelf.getWhat you see in n8n
Notes & use cases
Retrieves one specific bookshelf resource for the user you name, so a workflow can check a single shelf instead of walking the whole account.
Key parameters
- My Library: required switch the operation needs set before it runs; the catalog does not specify what each position changes, so a quick test against your account settles it.
- User ID: required, the ID of the user whose shelf you are reading.
- Bookshelf ID: required, the ID of the bookshelf itself, usually carried in from the operation that listed the shelves.
Get many bookshelves
bookshelf.getAllWhat you see in n8n
Notes & use cases
Returns many public bookshelf resources for a user in one execution, which is how you discover shelf IDs before doing anything else with them.
Key parameters
- My Library: required, same as the other shelf reads; nothing in the catalog says what each position does, so confirm with a short test run.
- User ID: required, the ID of the user being listed.
- Return All: on, n8n follows the API pages until every shelf is back; off, it stops at Limit.
- Limit: the maximum number of shelves returned when Return All stays off.
Bookshelf Volume
5 operationsAdd a bookshelf volume
bookshelfVolume.addWhat you see in n8n
Notes & use cases
Puts one volume onto one shelf. This is the write operation behind any workflow that turns a suggestion into an actual entry in a library.
Key parameters
- Bookshelf ID: required, the ID of the shelf receiving the volume.
- Volume ID: required, the ID of the volume being added, usually the one a search step just produced and passed along as
{{ $json.field }}.
Clear a bookshelf volume
bookshelfVolume.clearWhat you see in n8n
Notes & use cases
Empties a shelf in one call: every volume on it goes, and the shelf itself stays. Useful when a shelf is rebuilt from scratch rather than edited.
Key parameters
- Bookshelf ID: required, the ID of the shelf to empty. There is no second field to narrow it down, so double check the value before the workflow runs unattended.
Get many bookshelf volumes
bookshelfVolume.getAllWhat you see in n8n
Notes & use cases
Reads the contents of one shelf and returns the volumes on it as items, one per book, ready for the next node to loop over.
Key parameters
- My Library: required, mirrors the other shelf operations; the catalog leaves what each setting changes undocumented, so verify once against your account.
- User ID: required, the ID of the user who owns the shelf.
- Bookshelf ID: required, the ID of the shelf being read.
- Return All: turn it on for a full export; left off, the run stops at Limit.
- Limit: caps how many volumes come back.
Move a bookshelf volume
bookshelfVolume.moveWhat you see in n8n
Notes & use cases
Changes where a volume sits on its shelf. Order is the whole point here: the operation moves an existing entry rather than adding or deleting one.
Key parameters
- Bookshelf ID: required, the shelf holding the volume.
- Volume ID: required, the volume being moved.
- Volume Position: required, the position on the shelf. 0 puts the item before the current first item, 1 puts it between the first and the second, and so on.
Remove a bookshelf volume
bookshelfVolume.removeWhat you see in n8n
Notes & use cases
Takes a single volume off a shelf and leaves the rest untouched, which is the surgical version of clearing everything.
Key parameters
- Bookshelf ID: required, the ID of the shelf being edited.
- Volume ID: required, the ID of the volume to take off.
Volume
2 operationsGet a volume
volume.getWhat you see in n8n
Notes & use cases
Fetches one volume resource from its ID. Where the search operation guesses, this one is exact: you already know which book you mean.
Key parameters
- Volume ID: required, the ID of the volume. It is the only field the operation asks for, and it commonly arrives from whatever node ran before it in the workflow.
Get many volumes
volume.getAllWhat you see in n8n
Notes & use cases
Runs a search and returns many volumes filtered by your query. This is usually the first Google Books node in a workflow, because it turns text into volume records.
Key parameters
- Search Query: required, the full-text search query string sent to Google Books.
- Return All: on, n8n keeps requesting pages until the result set is complete.
- Limit: with Return All off, the ceiling on how many volumes come back, which keeps a chat reply short.
Need help automating Google Books with n8n?
A person reads every message.
Google Books and n8n, answered
01Is the Google Books n8n integration free?
02What credentials does the Google Books node need?
03What are the limits of the Google Books node in n8n?
04Can a workflow react to Google Books in real time?
05n8n or Make for Google Books?
Get our weekly integration tips.
No spam. Unsubscribe anytime.



