Resources · Make integration

Kinderpedia Make integrationAutomate Kinderpedia with Make.

Your school records can update themselves while staff stay with the children. The Kinderpedia Make integration gives you 19 modules: 1 trigger, 13 actions and 5 searches. This guide shows how to link your account and build a first working scenario.

Try the Kinderpedia integration on MakeSee the 19 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Kinderpedia Make integration do?

The Kinderpedia Make integration links your Kinderpedia account to Make, a visual tool where you build a scenario: an automation made of modules, each module being one brick that watches, reads or writes data. You connect once with an API key, then Kinderpedia students, parents, families and custom fields can feed other apps or be updated from them.

Admissions without retyping. An application arrives through a form app. Search Parents checks whether the guardian already exists, Add a Parent creates the record if not, and Add a Student adds the child. Nobody copies names from one screen to another.

A welcome routine for every new child. Watch New Students picks up each new record, and the next modules act on it: Add a Custom Field Value can stamp an intake status, and another app can send the welcome pack or notify the teacher.

Clean family data for reporting. Search Families and Get all Custom Fields Value pull what you need into a spreadsheet or dashboard, so the office stops exporting by hand.

Know the limits before you start. The Make documentation for Kinderpedia lists the modules but does not describe them, and it carries a warning that it was generated with AI from vendor documentation and may contain mistakes. Test each module with one record before trusting it. When something breaks, the Make troubleshooting guide walks through common errors, and n8n vs Make helps if you are still choosing a tool. For a guided start, see our Make training.

Connect

How do you connect Kinderpedia to Make?

  1. 01

    Generate your API key

    Log in to Kinderpedia and open your account settings. Choose the option that generates a new API key, then copy the key shown on screen. Keep it somewhere safe: this key is what lets Make act on your account.

  2. 02

    Add a Kinderpedia module

    In Make, open your scenario, click the +, search for Kinderpedia and pick any module. Then click Create a connection. A connection is your Kinderpedia account linked to Make once and reused by every Kinderpedia module.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like; the field is optional. Paste the API key you copied from Kinderpedia, or follow the on-screen instructions, and save. The module can now read your account.

First scenario

Build your first scenario with Kinderpedia

GoalWhen a new student appears in Kinderpedia, Make writes a custom field value on that student's record.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big + to add the first module. Search for Kinderpedia and choose Watch New Students.

  2. 02

    Link your account

    Click Create a connection, paste your Kinderpedia API key and save. Make can now read the students of your account and hand each new one to the next module.

  3. 03

    Add the action

    Click the + on the right of the trigger and pick Add a Custom Field Value. Choose the field Make lists from your account, then map the student from the trigger into it.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received. A bundle is one item passed along, here one student. Check that the value landed on the right record.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan does not go lower. Save, then switch the scenario on so it runs without you.

Triggers

What starts a Kinderpedia scenario?

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

Kinderpedia1Watch New Students

Watch New Students

triggerIn the docs only

Hands your scenario each student newly added in Kinderpedia as one bundle, so the rest of the chain acts on fresh enrollments without anyone checking the list. The doc gives this module no description; its behavior is read from its name, so check it with one test record.

How it fires
scheduled, going by the module listing. Make checks the app on the scenario's schedule, every 15 minutes by default, not the moment Kinderpedia creates a student.
When to use it
the admissions office creates records in Kinderpedia and other tools must follow, such as a welcome message or a class roster.
Watch out
every student it returns is a bundle, and each module placed after it spends one operation per bundle, the unit Make counts on your plan.
Modules

What can Make do in Kinderpedia?

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

Kinderpedia1

Add a Custom Field Value

ActionIn the docs only

Stores one piece of information in a custom field of your Kinderpedia account, so an answer collected in another tool ends up next to the child's record where staff already look.

When to use it
an intake form outside Kinderpedia asks something the standard record does not hold, like a transport preference.
Watch out
the doc does not describe this module, so check which fields exist with Get all Custom Fields first.
Kinderpedia2

Add a Parent

ActionIn the docs only

Creates a parent in Kinderpedia from data you map out of an earlier module, which spares the office from typing guardians in twice.

When to use it
a registration comes in through a form or a CRM and the guardian is not in Kinderpedia yet.
Watch out
nothing in the doc says this action checks for an existing parent, so place Search Parents before it and add the parent only when the search returns nothing.
Kinderpedia3

Add a Student

ActionIn the docs only

Opens a new student record in Kinderpedia, which means an admission decided in another app lands in the school system without manual entry.

When to use it
an application is accepted in your forms tool or pipeline and the child should appear in Kinderpedia right after.
Watch out
if another scenario runs Watch New Students, the child you add will likely show up there as well; make sure the two scenarios do not feed each other.
Kinderpedia4

Clean Custom Fields Value

ActionIn the docs only

Gives you a way to reset what a custom field holds, going by the module's name, so outdated information stops showing on a record. The doc says nothing more about it.

When to use it
a status kept in a custom field no longer applies after a child changes situation.
Watch out
the doc does not say what exactly gets cleared or whether it can be undone, so try it with Run once on a test record before a real one.
Kinderpedia5

Get a Family

ActionIn the docs only

Brings one family record from Kinderpedia into your scenario, so later modules can use its data in a message, a sheet or another app.

When to use it
an earlier module already tells you which family is concerned and you need its full record before writing somewhere else.
Watch out
a Get module targets a record you can point to; when all you have is a name, start with Search Families and pass its result along.
Kinderpedia6

Get a Group

ActionIn the docs only

Fetches the details of a single group from your Kinderpedia account, which is handy when a message or report needs the group's information and not just its name.

When to use it
a new student has been placed and the next step, say a note to the teacher, needs details of that group.
Watch out
Make needs to know which group to read; List Groups is the easy way to find it when you do not have it at hand.
Kinderpedia7

Get a Parent

ActionIn the docs only

Reads one parent's record in Kinderpedia and passes it on, so a reminder or a sync in another tool uses the data the school actually holds.

When to use it
a scenario already knows the parent, for example from Search Parents, and must hand the full record to an email or CRM module.
Watch out
this action works on one parent at a time; for several, let a search produce one bundle per parent first.
Kinderpedia8

Get a Student

ActionIn the docs only

Returns a single student's record from Kinderpedia, giving the next modules up-to-date data instead of a copy that may have drifted in a spreadsheet.

When to use it
Watch New Students has spotted a child and you want the complete record before sending it to another app.
Watch out
the module needs to know which student to fetch; map it from the trigger or from Search Students rather than typing it by hand.
Kinderpedia9

Get all Custom Fields

ActionIn the docs only

Shows you, judging by its name, the custom fields your Kinderpedia account defines, which is the map you need before writing into any of them.

When to use it
you are setting up Add a Custom Field Value or Update Custom Fields Values and want to see what fields exist.
Watch out
the doc does not describe the output, so run it once and read the bundle Make shows before relying on it in a longer scenario.
Kinderpedia10

Get all Custom Fields Value

ActionIn the docs only

Pulls the values stored in custom fields, going by the module's name, so the extra information your school tracks can leave Kinderpedia for a report or another tool.

When to use it
a dashboard or spreadsheet needs the custom data, not only the standard record.
Watch out
the doc does not say whether values come per record or for the whole account; test with Run once and read what arrives before mapping it.
Kinderpedia11

List Groups

SearchIn the docs only

Returns the groups of your Kinderpedia account as separate bundles, one per group, so you can loop over them or pick the one you need.

When to use it
a scenario must act on every group, such as building a sheet per group, or find a group before Get a Group.
Watch out
each group becomes a bundle, and every module after it runs once per bundle, so operations add up fast.
Kinderpedia12

Make an API Call

ActionIn the docs only

Reaches any endpoint of the Kinderpedia API from your scenario, using the same connection, which covers what the named modules leave out.

When to use it
you need an operation Kinderpedia supports but none of the other modules on this page offers.
Watch out
this is the technical module of the list; you write the request yourself, so keep the vendor's API documentation open and test with Run once before switching on.
Kinderpedia13

Search Families

SearchIn the docs only

Looks through your Kinderpedia families and returns the matches, which is how a scenario finds the right household from partial information.

When to use it
another app sends a family name and you need the Kinderpedia record before Get a Family or an update.
Watch out
a search can return zero, one or several bundles; with zero, the next modules have nothing to work on, so plan what should happen then.
Kinderpedia14

Search Parents

SearchIn the docs only

Finds parents already recorded in Kinderpedia, so you avoid creating the same guardian twice when a new registration comes in.

When to use it
right before Add a Parent, to check whether the person exists and branch the scenario accordingly.
Watch out
several parents may match loose criteria, and each match becomes a bundle, so later modules run once per result.
Kinderpedia15

Search Records

SearchIn the docs only

Runs a broader search in Kinderpedia than the student, parent or family searches, going by its name. The doc does not say which record types it covers.

When to use it
the specific searches do not reach the data you need and you want to see what this one returns.
Watch out
start with Run once on a narrow query and read the bundles, since nothing in the doc confirms its scope.
Kinderpedia16

Search Students

SearchIn the docs only

Brings back the students that match what you look for, so a scenario can find a child's record from data held in another app.

When to use it
a message or form refers to a student and you need the Kinderpedia record before Update Student Details.
Watch out
if the search finds nothing, no bundle comes out and the update never runs; test with a name you know exists.
Kinderpedia17

Update Custom Fields Values

ActionIn the docs only

Changes values already held in custom fields, going by the module's name, so a record keeps up with what happens in your other tools.

When to use it
a status tracked in a custom field moves on, for instance after a payment is confirmed in your billing app.
Watch out
an update most likely replaces the current value; read it first with Get all Custom Fields Value if you need to keep a trace.
Kinderpedia18

Update Student Details

ActionIn the docs only

Edits an existing student in Kinderpedia, so corrections made in another system reach the school record without a second round of typing.

When to use it
the office corrects a child's information in a form or CRM and Kinderpedia should follow.
Watch out
the module needs the right student; place Search Students before it and test with Run once so the change does not land on another child.
Need help

Need help automating Kinderpedia with Make?

A person reads every message.

FAQ

Kinderpedia and Make: common questions

01Is the Kinderpedia Make integration free?
Yes, on the Make side. Kinderpedia is a standard app, available from the Free plan along with more than 3,000 others. The Free plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes of execution, 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. You still need an active Kinderpedia account, which follows its own pricing.
02What does connecting Kinderpedia to Make require?
An active Kinderpedia account and an API key. Log in to Kinderpedia, open your account settings, generate a new API key and copy it. In Make, add any Kinderpedia module, click Create a connection, optionally name it, then paste the key. The connection is saved once and every Kinderpedia module in your scenarios reuses it, so you do not repeat this step for each module. If you later generate a new key, update the connection so your scenarios keep working.
03Does the Kinderpedia trigger in Make fire in real time?
No. Watch New Students is a scheduled trigger: Make checks Kinderpedia on the scenario's schedule instead of being told the moment a student is created. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans go down to 1 minute. Note that the Make documentation gives no description of this module, so its type comes from the module listing; run it once with a test record to see what it returns.
04What if a Kinderpedia module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Kinderpedia API with the same connection, so it covers actions the 19 listed modules do not. You write the request yourself, which asks for the vendor's API documentation. Keep in mind that the Make documentation for Kinderpedia is marked as AI-generated from vendor sources and may contain mistakes, so test each module and each request with Run once, and contact Kinderpedia directly when their documentation leaves a doubt.
05Should you use Make or n8n for Kinderpedia?
It depends on what your scenarios need. On Make, Kinderpedia has 19 modules covering students, parents, families, groups and custom fields, plus Make an API Call for the rest. Before choosing n8n, check whether it offers a Kinderpedia node and which operations that node covers, since this page documents Make only. Compare the two on the modules your process actually uses and on the plan limits that matter to you. The comparison page linked above sets out the differences between the two tools in more detail.
Same platform

Other docs you might need on this stack.

Browse all integrations