Zoho Notebook

Zoho Notebook is the note taking app in the Zoho suite. Agents create notebooks, add and update notecards with tags and reminders, read versions, search, read and empty the trash, and sync changes across an account.

35 actions OAuth available

Zoho Notebook website Capability data verified 2026-08-24

A weekly tidy-up run opens against the connected Zoho Notebook account

List Notebooks and List Notecards read the current structure and the cards in it

Search finds the duplicates and the superseded cards across the account

Agent separates the changes that version history can undo from the ones nothing can

Update Notecard consolidates the duplicates, whose earlier text stays readable in the version list

The permanent deletions post to the owner with a summary of what each card holds

The owner names what actually goes, because no operation here brings a trashed card back

What This Integration Enables

Zoho Notebook is the note app in the Zoho suite, and it is built around the notecard rather than the document: a card holds a note, a checklist, a link, an image or a file, it wears tags, it can carry a reminder, and it lives inside a notebook. That shape makes it a better target for automation than a long-form editor, because a card is small enough to be created, filed and superseded by a flow without a person having to reconcile paragraphs afterwards.

FlowRunner agents create notebooks and cards, move cards between notebooks, maintain tags and reminders, read a card's version history, search across the account, and work the trash. What they do not do is guess. This connector deserves a caveat that most of the catalog does not need, and stating it is more useful than hiding it: Zoho publishes no reference, no schema and no SDK for this API. Every route, verb and required parameter in the connector was mapped against the live API, using the fact that Zoho Notebook answers a different numeric code for a missing route, a wrong verb and a missing parameter. That verifies which routes exist, which verbs they take and which parameters they demand. It does not verify the field names inside a body, so where those are unpublished the connector passes a properties object straight through rather than inventing named fields. You should know which half is which before you build on it, and this page would rather tell you than let you find out.

Without FlowRunner

Notes pile up unsorted Cards accumulate faster than anyone tags or files them, and search becomes the only navigation

Context lives away from the work The decision is in a note and the task is in another tool, and neither points at the other

Cleanup is avoided Nobody empties the trash because nobody is sure what is in it, so it grows instead

With FlowRunner

Filing happens on arrival Cards land in the right notebook with their tag set and their source attached

Notes carry their follow-up A reminder on the card means the decision has a date, not just a paragraph

Cleanup is a reviewed list Permanent deletions are proposed with their contents summarized and confirmed by a person

Use Case Scenarios

Research and meeting notes filed on arrival

A summary produced upstream needs a durable home that a person will actually open. A flow searches the account for an existing card on the same subject, creates one where there is none, attaches the source through Add Notecard Resource so the link travels with the note, and applies the card's whole tag set in a single write. A reminder goes on the card for the date the decision has to be revisited. The related follow-up work goes to the task tool it belongs in, and a pointer to it goes on the card, so neither side is orphaned. A digest of the week's new cards posts to Slack.
Account notes that stay next to the account

Notes taken about a customer are usually written where the writing is comfortable and needed where the customer record lives. A flow reads the cards tagged for an account, summarizes them, and writes the summary onto the record in Zoho CRM, with a link back to the notebook for the detail. The salesperson keeps taking notes the way they already do, and the account record stops being the place where context goes missing.
Consolidation that keeps a way back

Duplicate cards are the normal state of a working notebook. A flow finds near-duplicates with Search, reads each with Get Notecard, and merges the content into one card through Update Notecard. Because Zoho Notebook keeps versions server side, the card's earlier text remains readable through List Notecard Versions afterwards, which is what makes the merge safe to run without asking. The losing cards are proposed for deletion rather than deleted, and that list is where a person comes in.

Human-in-Loop Highlight

This connector has a clean line running through it, and it is worth building every workflow around. On one side, an edit is recoverable: Update Notecard changes a card, and List Notecard Versions still shows what it said before, because Zoho Notebook keeps versions on the server. On the other side, a removal is not. Empty Trash permanently deletes, Delete Trashed Item permanently deletes, and Delete Notebooks takes every notecard inside the notebook with it. There is no restore operation anywhere in this surface. The connector can read the trash and it can destroy what is in it, and it cannot put a single card back.

So a FlowRunner cleanup agent runs freely on the recoverable side and stops at the line. It consolidates, retags, moves cards between notebooks and rewrites content without asking, because all of that can be read back. Then it stops and asks: "The tidy-up leaves 34 cards in the trash. Nine carry attachments, three are the only card in their notebook, and two were edited in the last month. Emptying the trash cannot be undone from here. Empty all, empty the 23 with no attachments, or leave it?" The owner answers. An agent that empties a trash on a schedule is not saving anyone time, it is removing the only safety net the product has, and the human-in-the-loop step is what keeps that net in place.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

35 actions

Notebooks

List Notebooks Reads the notebooks on the account.
Get Notebook Returns one notebook by id.
Create Notebook Creates a notebook. Zoho publishes no field list here, so the notebook's properties are passed through rather than mapped to named parameters.
Update Notebook Changes a notebook, with its properties passed through for the same reason.
Delete Notebooks Deletes notebooks by id, and the notecards inside them go too. The route takes a list even for a single notebook.
List Notebook Covers Reads the cover images a notebook can wear.

Notecards

List Notecards Reads the notecards in one notebook. There is no account-wide card listing, so every read is scoped to a notebook.
Get Notecard Returns one notecard by id.
Create Notecard Creates a notecard in a notebook. Zoho requires a parsable document on this route and publishes neither its format nor a schema, so this is the one operation worth reading the connector's own notes on before using.
Update Notecard Changes a notecard. The card's earlier text stays readable through its version history, which is what makes automated consolidation safe.
Delete Notecard Deletes one notecard by id.
Delete Notecards Deletes several notecards at once.
Delete Notebook Notecards Deletes several notecards from one notebook, which is the route the Notebook app itself uses when clearing a book.
Move Notecard Moves a notecard into another notebook, which is how a filing pass reorganizes without recreating anything.
List Notecard Versions Reads a notecard's version history. Zoho Notebook keeps versions server side, so this is how a flow recovers what a card said before an edit.
Add Notecard Resource Attaches a resource to a notecard, which is how an embedded link or media card gets its content.

Reminders

List Reminders Reads the reminders on the account.
List Notecard Reminders Reads the reminders set on one notecard.
Create Reminder Sets a reminder on a notecard, which is how a note acquires a date rather than just a paragraph.
Update Reminder Changes a reminder.
Delete Reminder Deletes a reminder. The notecard survives.

Trash

List Trash Reads what is in the trash, which is the input to any cleanup proposal.
Get Trashed Notecard Returns one trashed item. Zoho wants the notebook id alongside the item id here, which no other read on this API does.
Empty Trash Permanently deletes trashed items. This cannot be undone, and no operation in this connector restores a trashed card.
Delete Trashed Item Permanently deletes one trashed item.

Search and Sync

Search Searches the account's notes, which is the read behind duplicate detection and any filing decision.
Sync Runs Zoho Notebook's own sync exchange, the mechanism its clients use to reconcile changes since a point in time. Zoho publishes no schema for it, so the body is passed through untouched.

Frequently Asked Questions

What can FlowRunner do with Zoho Notebook?

FlowRunner agents can run List Notebooks, Get Notebook, and Create Notebook in Zoho Notebook, plus 32 more actions.

Does connecting Zoho Notebook to FlowRunner require OAuth?

Yes. Zoho Notebook connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Zoho Notebook trigger a FlowRunner workflow automatically?

Zoho Notebook doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Zoho Notebook

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us