Resources · Make integration

Kintone Make integrationAutomate Kintone with Make.

Can your Kintone records move on their own once they change? The Kintone Make integration gives you 12 modules: one trigger, nine actions and two searches. This page is for ops teams who know Kintone and are new to Make, and it walks you from connection to a first working scenario.

Try the Kintone integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Kintone Make integration do for you?

The Kintone Make integration links your Kintone account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger, an action or a search. Kintone can start a scenario when a new record appears, and it can receive records, comments and files sent from other tools.

Intake that files itself. A form or a spreadsheet in another app feeds Create a Record, so each request lands in Kintone as a proper record instead of an email someone has to retype. Upload a File can then attach the document that came with it.

A process that advances without clicks. When a payment is confirmed elsewhere, Search Records finds the matching entry and Update a Record Status moves it to the next step. Create a Comment leaves a short note so colleagues see why it moved.

New records announced to the right people. Watch Records picks up each record created in Kintone and passes it on, for example to a chat channel or a task list, while Get a Record fetches the full details when you only have an ID.

Know the limits before you start. The trigger only reacts to new records, not to edits, and it is scheduled, so Make checks Kintone on the scenario's timing rather than the moment a record appears. The Make documentation for this app is marked as AI-generated and asks you to verify important details with Kintone. The same app often has an n8n node too; the n8n vs Make comparison helps you choose, and the Make review covers the tool itself. If you would rather hand the build over, see our Make agency.

Connect

How do you connect your Kintone account to Make?

  1. 01

    Add a Kintone module

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

  2. 02

    Name the connection

    The Connection name field is optional, yet worth filling. A clear label such as the team or environment it belongs to saves you guessing later when several accounts are linked.

  3. 03

    Enter your credentials

    Paste the credentials copied from Kintone, either an API token or valid user credentials, or follow the on-screen instructions. For OAuth, create a client under OAuth in System Administration with the callback URI https://www.make.com/oauth/cb/kintone-v12.

First scenario

Your first scenario: comment on every new Kintone record

GoalWhen a new record is created in Kintone, Make adds a comment to it so the owner knows it was picked up.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Search for Kintone and pick Watch Records as the first module.

  2. 02

    Link your account

    Click Create a connection and enter your Kintone credentials. Once the connection exists, Make can list what it is allowed to read, so you pick instead of typing.

  3. 03

    Add the comment

    Click the + to the right of the trigger and choose Create a Comment. Map the record from the trigger so the comment lands on the right entry, then write a short message.

  4. 04

    Test with Run once

    Create a sample record in Kintone, then click Run once. Open the bubbles above each module to read the bundles, the items passed along, and check the comment appeared.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, and turn the scenario on. From then on each new record gets its comment without you.

Triggers

What can start a Kintone scenario?

1 module starts a scenario when something happens in Kintone. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Kintone as soon as it happens.

Kintone1Watch Records

Watch Records

Scheduled trigger

In Make“Triggers when a new record is created.”

You get each freshly created Kintone record handed to your scenario as its own bundle, ready to be sent to another tool, copied or commented on. It is the only way this app can start a scenario by itself.

How it fires
scheduled. Make checks Kintone on the scenario's schedule, every 15 minutes by default, and 15 minutes is also the shortest gap on the Free plan.
When to use it
whenever a new entry should set off follow-up work, such as a notification or a copy in another system.
Watch out
edits to existing records do not fire it; only new records do.
Modules

What can Make do in Kintone?

Kintone gives you 11 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Kintone1

Create a Comment

Action

In Make“Creates a new comment.”

Your team sees a note right on the Kintone record, written by the scenario, so the context of an automated change stays next to the data. Each run adds one comment, which counts as one operation, the unit Make bills on your plan.

When to use it
after an update, to explain what changed and why, or to flag a record for someone.
Kintone2

Create a Record

Action

In Make“Creates a new record.”

A new Kintone record appears from data arriving elsewhere, like a form entry or a row in a sheet, with no manual retyping. This is the entry point for most intake flows built around Kintone.

When to use it
when the source is outside Kintone and the item does not exist yet.
Watch out
run a search first if duplicates are possible, since this module always adds a new record.
Kintone3

Delete a Comment

Action

In Make“Deletes an existing comment.”

Removes a comment from a record, which keeps threads clean when a scenario posted something that no longer applies. Pair it with Search Comments to find the right one before removing it.

When to use it
once the issue behind an automated reminder is settled and the note would only confuse readers.
Watch out
try it on a sample record first, and check with Search Comments that you target the right note.
Kintone4

Delete a Record

Action

In Make“Deletes an existing record.”

Takes a record out of Kintone entirely, so test data or cancelled entries stop cluttering views and reports. It acts on one record per bundle, which makes it safe to control record by record.

When to use it
when an item was cancelled at its source and should vanish from Kintone too.
Watch out
deleting is the whole job of this module, so add a filter before this module so only intended records reach it.
Kintone5

Get a Record

Action

In Make“Retrieves an existing record.”

Brings back the full content of one record you already know, so later modules can map any of its values. Think of it as opening a record you can already point to, rather than searching for it.

When to use it
when an earlier module only points to a record and the next step needs everything inside it.
Watch out
if you cannot point to the exact record, there is nothing to fetch; use Search Records when you only know a value.
Kintone6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Covers anything the listed modules leave out: you call any endpoint of the Kintone API from the scenario, reusing the same connection, so there is no separate login to manage.

When to use it
when you need a Kintone action that has no dedicated module here.
Watch out
you describe the request yourself, so keep the Kintone API reference open and test with Run once before going live.
Kintone7

Update a Record

Action

In Make“Updates an existing record.”

Keeps an existing record in step with the rest of your tools by changing its values in place, instead of creating a second copy next to it. History and comments stay attached to the same entry.

When to use it
when a customer, an order or a request changes in another system and Kintone should reflect it.
Watch out
Make must know which record to change, so place Search Records just before when you only know a value.
Kintone8

Update a Record Status

Action

In Make“Updates the status of the existing record.”

Moves a record to its next status, so a Kintone process advances as soon as the outside event that justifies it happens. It is distinct from Update a Record, which edits values but leaves the status alone.

When to use it
when an approval, a payment or a delivery elsewhere should push the record forward.
Watch out
map the exact record, or the wrong entry moves on.
Kintone9

Upload a File

Action

In Make“Uploads a new file.”

Sends a file into Kintone so it can live alongside the record it belongs to, for example a signed contract or a scanned receipt coming from mail or storage. The file travels as a bundle from the module before it.

When to use it
when documents arrive outside Kintone and should end up next to the matching entry.
Watch out
on the Free plan, files over 5 MB are refused by Make.
Kintone10

Search Comments

Search

In Make“Searches for comments or lists them all.”

Lists the comments on a record, or only those that match, so a scenario can read the discussion before acting on it. Each comment comes out as a separate bundle.

When to use it
to check whether a reminder was already posted, or to find the comment you plan to delete.
Watch out
it can return zero, one or many results, and every module after it runs once per comment.
Kintone11

Search Records

Search

In Make“Searches for records or lists them all.”

Finds the Kintone records that match what you know, a value you already have, or lists them all, and hands each one on as a bundle. It is how later modules learn which record to act on.

When to use it
before Update a Record or Delete a Record, or to avoid creating a duplicate.
Watch out
zero results means following modules simply do not run; many results means they run many times.
Need help

Need help automating Kintone with Make?

A person reads every message.

FAQ

Kintone and Make: common questions

01Is the Kintone Make integration free?
Yes, on the Make side. Kintone is a standard app, available from the Free plan. That plan allows 2 active scenarios, a 15 minute minimum gap between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. You still need an active Kintone subscription, which Make does not cover and which is priced by Kintone.
02What is needed to connect Kintone to Make?
An active Kintone account plus either an API token or valid user credentials. In Make, add a Kintone module, click Create a connection, optionally name it, then enter what you copied from Kintone. If you prefer OAuth, an administrator registers a client in the OAuth section of System Administration, sets the callback URI given by the Make documentation, and copies the Client ID, Client secret, Authorization endpoint and Token endpoint.
03Does the Kintone trigger in Make react in real time?
No. Watch Records is a scheduled trigger: Make asks Kintone for new records on the scenario's schedule, every 15 minutes by default. On a paid plan you can shorten the gap to 1 minute, while the Free plan keeps it at 15 minutes. It also only reacts to newly created records, so changes to existing ones need another approach, such as a search run on a schedule. To test without waiting, click Run once in the editor after creating a sample record.
04What if a Kintone module is missing in Make?
Use Make an API Call. It lets the scenario call any endpoint of the Kintone API with the connection you already set up, which covers actions outside the 12 listed modules. Keep in mind that the Make documentation for this app is flagged as AI-generated, so confirm important behavior in the Kintone reference before relying on it, and run the scenario once as a test before switching it on. Each call counts as an operation, like any other module.
05Should Kintone be automated with Make or n8n?
It depends on the tool your team already uses. Make gives Kintone 12 ready modules, one scheduled trigger and an API call module, all built visually in the scenario editor, which suits someone who wants a first automation without code. The same app often has an n8n node as well, so if your other workflows already run in n8n, staying there keeps everything in one place. Compare which modules each side offers for your exact case.
Same platform

Other docs you might need on this stack.

Browse all integrations