Resources · Make integration

Zoho Notebook Make integrationAutomate Zoho Notebook with Make.

Can Make keep your Zoho Notebook tidy while you work elsewhere? The Zoho Notebook Make integration gives you 20 modules: 2 scheduled triggers, 16 actions and 2 searches. This guide shows how to link your account, build a first scenario and pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Zoho Notebook Make integration do for you?

The Zoho Notebook Make integration links your Zoho account to Make, a visual tool where you chain apps without code. You build a scenario, which is the automation itself, out of modules: each module is one brick, such as a trigger that watches notecards or an action that creates a notebook.

Capture ideas from other tools. A form entry, a support ticket or a message from another app can land as a fresh note through Create a Notecard, so nothing stays stuck in an inbox. Attachments follow with Create a File Card, and voice memos with Create an Audio Card.

React when your notes change. Watch Notecards and Watch Notebooks pick up items that were created or updated, and pass each one to the next module. A sales rep adds a meeting note, and Make copies the text into your CRM or pings the team.

Keep checklists in step with projects. Create a Checklist opens a to-do list when a project starts elsewhere, and Update a Checklist edits it as the work moves on.

Both triggers are scheduled: Make checks Zoho Notebook on the scenario's schedule, so a change shows up at the next run, not the second it happens. Each card type also carries a single file, so several attachments mean several cards. To weigh your options, read the Make review and the n8n vs Make comparison. If you want to learn the editor properly, the Make training starts from zero.

Connect

How do you connect Zoho Notebook to Make?

  1. 01

    Add a Zoho Notebook module

    Open your scenario, add any Zoho Notebook module and click Create a connection. A connection is your Zoho account linked to Make once, then reused by every Zoho Notebook module you add later.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear label such as the account owner's name saves confusion when a teammate opens the scenario and sees several Zoho accounts listed.

  3. 03

    Enter your credentials

    Paste the credentials copied from your Zoho account, or follow the on-screen instructions. You need an active Zoho account with Zoho Notebook set up; for a custom client, the API console gives you a Client ID and a Client secret.

First scenario

Your first scenario with Zoho Notebook

GoalWhen a new item shows up in another app, Make saves it as a notecard in Zoho Notebook.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big +. Pick the app that feeds you ideas or requests, and its trigger, as the first module.

  2. 02

    Add Create a Notecard

    Click the + on the right of that first module, search for Zoho Notebook and choose Create a Notecard. Click Create a connection if your account is not linked yet.

  3. 03

    Map the content

    Fill the module fields. Once the connection exists, Make lists what it can read in your account, and you drag data from the first module into the notecard so each item becomes its own note.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received; a bundle is one item passed along, here one request turned into one notecard.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Every module run counts as one operation on your Make plan.

Triggers

What starts a Zoho Notebook scenario?

2 modules start a scenario when something happens in Zoho Notebook. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Zoho Notebook as soon as it happens.

Zoho Notebook1Watch Notebooks

Watch Notebooks

Scheduled trigger

In Make“Triggers when a notebook has been created or updated.”

This trigger hands your scenario every notebook that was created or updated since the previous check, one bundle per notebook, so a new client binder or a renamed project space can set things moving in other tools.

How it fires
scheduled; Make checks the app on the scenario's schedule, every 15 minutes by default and never faster than that on the Free plan.
When to use it
when opening a notebook is the signal that a project has begun and other apps should hear about it.
Watch out
updates count as well as creations, so add a filter if only brand new notebooks matter.
Zoho Notebook2Watch Notecards

Watch Notecards

Scheduled trigger

In Make“Triggers when a notecard has been created or updated.”

Pick this one to follow the notes themselves: each notecard created or updated since the last check reaches the scenario as its own bundle, ready to be copied, shared or filed in another app.

How it fires
scheduled; Make checks the app on the scenario's schedule, so a note written right now is picked up at the next run, not instantly.
When to use it
when your team drafts meeting notes in Zoho Notebook and the content has to reach a CRM or a chat channel.
Watch out
if a later module in the same scenario edits notecards, you can feed the trigger its own changes; keep writes elsewhere.
Modules

What can Make do in Zoho Notebook?

Zoho Notebook gives you 18 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Zoho Notebook1

Create a Checklist

Action

In Make“Creates a new checklist.”

You get a ready to-do list in Zoho Notebook without typing it, built from whatever the earlier modules pass along, such as the tasks of a new project or the items of an onboarding.

When to use it
when a deal is won or a project opens elsewhere and the same steps must be ticked off each time.
Watch out
to change a list later, reach for Update a Checklist instead of creating a second one.
Zoho Notebook2

Create a File Card

Action

In Make“Creates a file card with one file.”

A document received somewhere else ends up as a card in your notebook, so contracts, briefs or scans sit next to the notes that explain them.

When to use it
when an email attachment or a form upload belongs with a client's notes rather than in a shared drive.
Watch out
each file card holds one file only; three attachments mean three cards, and on the Free plan Make handles files up to 5 MB.
Zoho Notebook3

Create an Audio Card

Action

In Make“Creates an audio card with one audio file.”

Voice memos and call recordings become playable cards inside Zoho Notebook, which beats hunting for an audio file in a download folder.

When to use it
when a recording app or a voicemail service produces audio that someone should listen to alongside written notes.
Watch out
one audio file per card, so split a batch of recordings into separate runs, and mind the 5 MB file ceiling on the Free plan.
Zoho Notebook4

Create an Embed Resource

Action

In Make“Creates a resource for embedding in a notecard.”

This action prepares a resource that a notecard can embed, the building block to use when a note should display content rather than only link to it.

When to use it
when you assemble rich notecards automatically and the embedded element has to exist before the note that shows it.
Watch out
run it before the module that creates or updates the notecard, otherwise there is nothing yet to place in the note.
Zoho Notebook5

Create a Notebook

Action

In Make“Creates a new notebook.”

Spin up a fresh notebook the moment a new client, course or project appears in another app, so every related note has a home from day one.

When to use it
when your team keeps one notebook per account and forgets to create it by hand.
Watch out
run List Notebooks first if the same client may already have a notebook, or you will end up with duplicates.
Zoho Notebook6

Create a Notecard

Action

In Make“Creates a new notecard.”

The workhorse of this integration: it writes a new note from data mapped out of the earlier modules, so ideas, requests and summaries land in Zoho Notebook on their own.

When to use it
when text arrives from a form, an email or a chat and should be kept as a readable note.
Watch out
every bundle produces one notecard, so a search returning many items upstream creates many notes.
Zoho Notebook7

Delete an Embed Resource

Action

In Make“Deletes an existing embed resource.”

Removing an embed resource clears content that a notecard no longer needs, keeping the account free of leftovers from automated notes.

When to use it
when a scenario replaces an embedded element and the old version should disappear with it.
Watch out
a deletion from Make cannot be undone from the scenario, so test with Run once on a throwaway note before switching it on.
Zoho Notebook8

Delete a Notebook

Action

In Make“Deletes a chosen notebook.”

Removes a whole notebook, which is handy for cleaning up spaces tied to projects or clients that are closed in your other systems.

When to use it
when an account is archived in your CRM and its notebook should go too.
Watch out
this is the heaviest action in the list; a deletion cannot be undone from the scenario, so put a filter in front and check the target with Get a Notebook first.
Zoho Notebook9

Delete a Notecard

Action

In Make“Deletes an existing notecard.”

Takes a single notecard off the account, a lighter clean-up than deleting a notebook, aimed at drafts or duplicates your automation spotted.

When to use it
when a List Notecards search finds notes you no longer want to keep.
Watch out
a search can return several notecards, and each one reaching this module is deleted, so narrow the search before you connect them.
Zoho Notebook10

Get an Embed Resource Details

Action

In Make“Retrieves embed resource details.”

Reads the details of one embed resource and hands them to the following modules, useful when you need to know what a notecard displays before acting on it.

When to use it
when a scenario checks or copies an embedded element instead of creating a new one.
Watch out
it reads a single resource you point to; to go through many items, start from a search on notecards.
Zoho Notebook11

Get a Notebook

Action

In Make“Retrieves a single notebook.”

Fetches one notebook so its data can be reused further down the scenario, for instance to confirm you are about to write in the right place.

When to use it
when you already know which notebook matters and just need its current state, such as before an update or a deletion.
Watch out
when you do not know the notebook yet, List Notebooks is the right starting point.
Zoho Notebook12

Get a Notecard

Action

In Make“Retrieves a single notecard.”

Pulls one notecard into the scenario so its content can be sent, summarized or copied into another app.

When to use it
after Watch Notecards or a search, when you want the full note before passing it to a CRM, a chat or a document.
Watch out
it returns one note per run; chaining it after a search costs one operation per notecard found.
Zoho Notebook13

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Covers everything the listed modules leave out: it lets the scenario call any endpoint of the Zoho Notebook API, reusing the connection you already created.

When to use it
when an action you need has no module of its own and the Zoho Notebook API documentation describes it.
Watch out
you write the request yourself, so keep the vendor documentation open and test with Run once before going live.
Zoho Notebook14

Update a Checklist

Action

In Make“Updates an existing checklist.”

Edits a checklist that already exists, which keeps a single list alive as a project moves instead of scattering new ones.

When to use it
when a task is closed in your project tool and the matching item in Zoho Notebook should reflect it.
Watch out
the checklist must exist first; if the scenario may meet a project without one, add Create a Checklist on a separate route.
Zoho Notebook15

Update a Notebook

Action

In Make“Updates an existing notebook.”

Changes an existing notebook so it keeps matching the client or project it belongs to, for example after a rename in your CRM.

When to use it
when names drift between tools and you want Zoho Notebook to follow the system of record.
Watch out
avoid pairing it with Watch Notebooks in the same scenario, since each update counts as a change the trigger will see again.
Zoho Notebook16

Update a Notecard

Action

In Make“Updates an existing notecard.”

Rewrites a notecard in place, so a meeting note or a status summary stays current without piling up copies.

When to use it
when fresh data from another app, a new deal stage for instance, should refresh a note you already keep.
Watch out
expect the new content to replace the old, so map every piece you want to keep and check the result with Run once.
Zoho Notebook17

List Notebooks

Search

In Make“Retrieves a list of notebooks.”

Returns your notebooks as separate bundles, zero, one or many, so later modules can work through each of them in turn.

When to use it
before creating a notebook, to check whether one already exists, or when a report must cover every notebook.
Watch out
an empty result stops that route, and a long result multiplies the operations spent by every module that follows.
Zoho Notebook18

List Notecards

Search

In Make“Retrieves a list of notecards.”

Brings back a set of notecards, each as its own bundle, which is how you reach old notes that no trigger would ever surface.

When to use it
when you want to export, tidy or re-file notes that already exist in the account.
Watch out
every notecard found runs the next modules once, so pair it with a filter before a delete or an update.
Need help

Need help automating Zoho Notebook with Make?

A person reads every message.

FAQ

Zoho Notebook and Make: common questions

01Is the Zoho Notebook Make integration free?
Yes, Zoho Notebook is a standard app in Make, so its modules are available on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations per month. Any Zoho Notebook subscription is handled on the Zoho side.
02What do you need to connect Zoho Notebook to Make?
You need an active Zoho account with Zoho Notebook set up. In Make, add a Zoho Notebook module, click Create a connection, optionally name it, then enter the credentials from your Zoho account or follow the on-screen instructions. For a custom client, the Zoho API console provides a Client ID and a Client secret, and the callback URI to enter is the Make address shown in the connection guide above. The connection is then reused by every Zoho Notebook module.
03Does the Zoho Notebook trigger fire instantly?
No. Watch Notebooks and Watch Notecards are both scheduled triggers: Make checks Zoho Notebook on the scenario's schedule and collects what was created or updated since the previous check. A new scenario runs every 15 minutes by default, the shortest interval on the Free plan, and paid plans go down to 1 minute. There is no instant trigger for this app, so a note written now reaches the scenario at the next scheduled run.
04What if a Zoho Notebook module is missing in Make?
It depends on what you need. The Make an API Call module calls any endpoint of the Zoho Notebook API with your existing connection, which covers actions the 20 listed modules do not. You write the request from the vendor documentation. Note that Make's own page for this app warns that it was generated with AI from the Zoho Notebook docs, so check important details with Zoho directly before relying on them.
05Should you use Make or n8n for Zoho Notebook?
It depends on your criteria rather than on a winner. On Make, Zoho Notebook comes with 20 ready modules, two scheduled triggers and a Free plan to test a first scenario without code. The same app often exists as an n8n node too, so check whether that node covers the notebooks, notecards and checklists you plan to automate. Compare the modules available on each side for your case, and pick the tool your team already knows how to maintain.