Resources · Make integration

Edusign Make integrationAutomate Edusign with Make.

Tired of typing the same course and student records into Edusign by hand? The Edusign Make integration gives you 16 modules: 3 triggers and 13 actions. This page shows training managers how to connect the account and build a first working flow.

Try the Edusign integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Edusign Make integration do for you?

It links your Edusign account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that each do one job. Edusign brings 16 of those modules, so new courses, professors and students can move to your other tools, and records can come back in, without copy and paste.

Enrollment without retyping. A registration arrives in your form or spreadsheet, and Create a Student adds the learner to Edusign straight away. The same logic works with Create a Professor when a new trainer joins the team.

A course calendar that stays in step. Watch Courses notices each new course and hands it to your planning or messaging tool. If the schedule shifts elsewhere, Update a Course pushes the change back so nobody works from an old version.

Clean records when people leave. Delete a Student and Delete a Professor remove profiles once another system marks them as gone, which keeps your lists short and accurate.

Know the limits before you start. The three triggers are scheduled, so Make checks Edusign on the scenario's schedule rather than hearing about changes the moment they happen. The modules cover courses, professors and students only; for anything else in the Edusign API, Make an API Call is the way in. Edusign may also exist as an n8n node; if you are weighing both tools, read n8n vs Make. For plan costs, see Make pricing, and for a guided start, Make training.

Connect

How do you connect Edusign to Make?

  1. 01

    Copy your API key in Edusign

    You need an active Edusign account first. Inside it, open your account Settings, go to the API section and copy the API key shown there. Keep it at hand, Make asks for it in the next step.

  2. 02

    Add an Edusign module and create the connection

    In your Make scenario, add any Edusign module and click Create a connection. A connection is your Edusign account linked to Make once, then reused by every Edusign module. You can type a label in Connection name if you like.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions Make shows on screen, then confirm. The connection now appears in the module, and Make can list the Edusign data it is allowed to read.

First scenario

Your first scenario: add each new registration to Edusign

GoalWhen a new registration lands in the tool your team already uses, Make creates the matching student in Edusign.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module. This first module is where your registrations come from, for example a form or a spreadsheet app.

  2. 02

    Set up the source of registrations

    Search that app by name, pick the module that watches new entries, connect your account and choose the form or sheet. Each new entry will travel as a bundle, one item passed to the next module.

  3. 03

    Add Create a Student

    Click the + on the right of the first module, search Edusign and pick Create a Student. Select your Edusign connection, then map the learner details from the previous module into the fields Make displays.

  4. 04

    Test with Run once

    Add a test entry in your source, then click Run once. Make runs the scenario one time and shows the bundles each module received. Check in Edusign that the student is there with the right details.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From now on, every new registration becomes an Edusign student without anyone retyping it.

Triggers

Triggers: what starts an Edusign scenario

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

Edusign1Watch Courses

Watch Courses

Scheduled trigger

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

Every course newly created in Edusign starts your scenario, so the rest of your stack learns about it without anyone passing the news along. Each new course arrives as a bundle you can map into later modules.

How it fires
it is a scheduled trigger, so Make checks Edusign on the scenario's schedule, every 15 minutes by default, and picks up the courses created since the last check.
When to use it
announcing a freshly planned session in your team chat or copying it into a shared planning calendar.
Watch out
it reacts to new courses only; a course edited later will not start the scenario again.
Edusign2Watch Professors

Watch Professors

Scheduled trigger

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

This one keeps an eye on your trainer list and hands over each professor added in Edusign. Handy when onboarding a trainer involves several tools and you want the first steps to happen on their own.

How it fires
scheduled. Make queries Edusign at the rhythm you set on the scenario's clock (15 minutes unless you change it), so a new professor shows up at the next check, not the second they are saved.
When to use it
sending a welcome email or creating the trainer's entry in your HR sheet.
Watch out
on the Free plan, the shortest possible gap between two checks is 15 minutes.
Edusign3Watch Students

Watch Students

Scheduled trigger

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

You get one bundle per student newly created in Edusign, ready to feed your CRM, mailing tool or reporting sheet. It is the natural starting point for anything that should follow a learner's arrival.

How it fires
Make polls Edusign on the scenario's schedule, which is every 15 minutes on a new scenario; it is a scheduled trigger, marked with the clock badge in the editor.
When to use it
adding each new learner to a welcome sequence or to the client file of the company paying for the training.
Watch out
each student processed costs operations, one per module run, so a large import counts against your plan.
Modules

Actions: what Make can do in Edusign

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

Edusign1

Create a Course

Action

In Make“Creates a new course.”

Adds a new course to Edusign from data that lives elsewhere, so your training plan exists in one place and Edusign follows it.

When to use it
a session gets confirmed in your planning sheet or booking tool and should appear in Edusign without being typed twice.
Watch out
if the scenario also starts with Watch Courses, keep them in separate scenarios so a created course does not trigger a second pass.
Edusign2

Create a Professor

Action

In Make“Creates a new professor.”

Registers a trainer in Edusign with the details another tool already holds, which saves the admin step when someone joins your teaching team.

When to use it
a freelance trainer signs a contract in your HR or signature tool and needs an Edusign profile before their first session.
Watch out
run a Run once test with a dummy trainer first, then delete that profile, so your real list stays clean.
Edusign3

Create a Student

Action

In Make“Creates a new student.”

Puts a learner into Edusign the moment their registration exists elsewhere, which is usually the biggest time saver of the whole integration.

When to use it
after a registration form, a paid order in your shop or a row added to the enrollment spreadsheet.
Watch out
if the same person can register twice in your source tool, check upstream with a filter, otherwise Edusign will receive two students.
Edusign4

Delete a Course

Action

In Make“Deletes a course.”

Removes a course from Edusign when it is cancelled in the tool your team actually plans with, so learners and trainers do not see a session that will never happen.

When to use it
a session is marked as cancelled in your planning sheet or calendar.
Watch out
treat a deletion as final; test it on a dummy course before pointing it at real ones.
Edusign5

Delete a Professor

Action

In Make“Deletes a professor.”

Takes a trainer out of Edusign once your other systems say they no longer work with you, which keeps the professor list honest.

When to use it
an end date is reached in your HR tool, or a contract is closed in your CRM.
Watch out
place a filter before this module so only the right professor reaches it, because there is no confirmation step in a running scenario.
Edusign6

Delete a Student

Action

In Make“Deletes a student.”

Cleans a learner's profile out of Edusign when they drop out or ask for removal, so your student base matches reality.

When to use it
a withdrawal is recorded in your enrollment sheet or a refund goes through in your shop.
Watch out
map the student carefully and try it on a test profile with Run once; a wrong mapping would remove someone you meant to keep.
Edusign7

Get a Course

Action

In Make“Retrieves a course.”

Reads one course from Edusign so its details can feed the rest of the scenario, for example a reminder or a report line.

When to use it
your scenario knows which course it is about, but needs its current details before writing a message or updating another tool.
Watch out
it returns a single course, not a list, so point it at a course the scenario already identified.
Edusign8

Get a Professor

Action

In Make“Retrieves a professor.”

Fetches one trainer's record from Edusign, handy when a later module needs their details and the scenario only knows who they are.

When to use it
preparing a message to the trainer of a course, or copying their profile into a planning tool.
Watch out
each call counts as an operation, so fetch the professor once and reuse the result in the following modules.
Edusign9

Get a Student

Action

In Make“Retrieves a student.”

Pulls the full record of one learner from Edusign, which gives later modules everything they need about that person.

When to use it
right after Watch Students, or when another tool sends you a learner and you want the Edusign version before acting.
Watch out
run the scenario once and open the bundle to see what comes back before you map anything.
Edusign10

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Edusign API to your scenario, with the same connection, for anything the 13 ready-made actions do not cover.

When to use it
you need an Edusign feature that has no dedicated module and you are comfortable reading the Edusign API documentation.
Watch out
you write the request yourself, so test it with Run once and read the response bundle before relying on it.
Edusign11

Update a Course

Action

In Make“Updates a course.”

Changes an existing course in Edusign so it matches what was decided elsewhere, without anyone reopening Edusign to edit it.

When to use it
a session is rescheduled in your planning tool, and Edusign should show the new version.
Watch out
try it on a dummy course with Run once and check in Edusign what changed before you point it at real sessions.
Edusign12

Update a Professor

Action

In Make“Updates a professor.”

Keeps a trainer's Edusign profile aligned with your HR records, so a correction made there reaches Edusign on its own.

When to use it
a trainer's contact details are corrected in your staff directory or CRM.
Watch out
identify the professor with the same reference in both tools; otherwise the update lands on the wrong profile or fails.
Edusign13

Update a Student

Action

In Make“Updates a student.”

Edits a learner already in Edusign with fresher information from another tool, which avoids the slow drift between two lists.

When to use it
a learner's details are corrected in your CRM and Edusign needs the same version.
Watch out
do not pair it with Watch Students expecting edits to trigger anything; that trigger only sees new students.
Need help

Need help automating Edusign with Make?

A person reads every message.

FAQ

Edusign and Make: frequent questions

01Is the Edusign Make integration free?
Yes, on the Make side. Edusign is a standard app, available from the Free plan. That plan lets you keep 2 active scenarios, runs scheduled scenarios at most every 15 minutes, and caps each run at 5 minutes. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in operations per month. You still need your own Edusign subscription, which is billed by Edusign, not by Make. Check the Edusign pricing page for that part, since this page does not cover it.
02What do you need to connect Edusign to Make?
An active Edusign account and its API key. In Edusign, open your account Settings, go to the API section and copy the key displayed there. Then, in Make, add any Edusign module to your scenario, click Create a connection, optionally give it a name, and paste the key. The connection is saved once and reused by all 16 Edusign modules, so you will not repeat the step for each module. If you do not have an Edusign account yet, you need to create one first, as the Make app cannot work without it.
03Do the Edusign triggers in Make react instantly?
No. Watch Courses, Watch Professors and Watch Students are all scheduled triggers: Make checks Edusign at the interval set on the scenario, every 15 minutes on a new scenario. On the Free plan, 15 minutes is also the shortest interval possible; paid plans can go down to 1 minute. Edusign has no instant trigger in Make, so nothing is pushed by webhook the second a record is created. If a delay of a few minutes is acceptable, which is common for enrollment and planning tasks, the scheduled triggers do the job well.
04What if an Edusign module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Edusign API from your scenario, with the connection you already set up, so you are not limited to the 13 ready-made actions. You write the request yourself, based on the Edusign API documentation, then test it with Run once. Keep in mind that the Make documentation for this app is marked as AI-generated from Edusign's own docs, so verify important details directly with Edusign before building on them.
05Should you use Make or n8n for Edusign?
It depends on the tool your team already knows. This page covers Make, where Edusign has 16 native modules on courses, professors and students, plus Make an API Call for the rest. Many apps also exist as an n8n node, so check whether Edusign does before choosing. The deciding criteria are practical: which editor your team is comfortable with, which other apps your scenarios need, and how your plan counts usage. Neither choice is wrong. The n8n vs Make comparison on this site lays out those criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations