Resources · Zapier integration

Edusign Zapier integrationAutomate Edusign with Zapier.

The Edusign Zapier integration gives you 7 triggers, 11 actions and 7 searches. It covers the people of your school (students, professors, admins), the groups and courses they belong to, and the documents they sign. All of it runs on the free plan.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Edusign Zapier integration actually does

Edusign handles digital attendance sheets and signed documents for schools and training providers. Hooked to Zapier, it can start an automation when a student, professor, group or course appears, and it can create or update those same records from another step. No code, no export, no copy-paste between tabs.

Three outcomes are worth building first. A roster that fills itself: Create Student and Create Professor add people to Edusign, and Create Group puts students into a cohort. Courses that exist before day one: Create Course (Group) and Create Course (Students) build the session with its dates and its professor. Paperwork that goes out on its own: Create Document (From Template) produces a document from one of your school templates and can send it out for signature by email.

Now the honest part. None of the 7 triggers is instant: Zapier checks Edusign on a timer, so nothing lands the second it happens. Updating a professor or a student by changing their email takes their Edusign ID, not just the old address. And Create Group and Create Course (Students) expect the people they list to exist already.

If you are weighing tools, the same app has an Edusign Make integration page, and the Make vs Zapier comparison sets the two side by side.

Vocabulary

Zapier vocabulary in one minute

Eight words carry the rest of this page. Each one is explained once, here, then used as is.

Zap
The automation you build on Zapier: one starting event, then one or more steps that run each time that event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, here a new student, course or group in Edusign.
Action
What the Zap does once it has started: the step that creates, updates or sends something for you in an app.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts those, nothing else.
Polling vs instant
A polling trigger is checked on a timer, keeping only what is new. An instant one is pushed by the app the moment it happens. Edusign is all polling.
Filter
A step that lets the Zap carry on only when what arrived meets a condition you set, and stops it quietly otherwise.
Search step
A step that looks up a record already in an app, like a professor by email, so the next steps can reuse what it found.
Connection
Your Edusign account linked to Zapier once, then reused by every step of every Zap that touches Edusign.
Cost

What it really costs

Edusign is not a premium app, so it works on the free plan. The bill is counted in tasks, and only successful actions count.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan steps1 trigger + 1 action
  • Edusign on freeYes, not a premium app
  • Costs a taskEach successful action

The trigger never costs a task, and neither does Zapier checking Edusign for new items, however often it looks. Each action that succeeds is one task; one that fails is not counted. A Zap with three actions eats three times what a one-action Zap does. The catch: the free plan stops at two steps, one trigger and one action. Add a filter or a search and the Zap becomes multi-step, which means a paid plan.

Connect

Connect Edusign to Zapier in 3 steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. Type Edusign in the dialog and pick it from the results. You need an Edusign account first, and access to whatever you want the Zap to touch.

  2. 02

    Sign in to Edusign

    Click Add connection. A tab opens on the Edusign side: sign in with the school account the Zaps should act on, not a personal test account you will delete later.

  3. 03

    Grant access

    Allow Zapier into the account. That connection is now shared by every Edusign step you build, whether it watches new courses or creates documents, so you do this once.

First Zap

Your first Zap: a document from every new template

GoalWhen an admin adds a document template in Edusign, generate a first document from it, sent for signature, so the template is checked in real use.

  1. 01

    Build: pick the trigger

    In the editor, under Build, choose Edusign as the app and the event New Documents Templates, then pick the Edusign connection you just set up.

  2. 02

    Test the trigger

    Click Test. Zapier brings back the three most recent templates of the account, so you map the next steps on a real one instead of a guess.

  3. 03

    Find the admin

    Add the search Find Admin and give it the admin's email. The document action needs that admin, and the search hands it over.

  4. 04

    Create the document

    Add Create Document (From Template). Map the template the trigger brought back and the admin email from the search. Decide whether it goes out for signature by email.

  5. 05

    Test, then Publish

    Test each step once and read what came back. Then click Publish. With a search between trigger and action, this Zap is multi-step, so it needs a paid plan.

Triggers

The 7 Edusign triggers

7 events start a Zap when something happens in Edusign. Zapier checks for them at the interval your plan allows.

1

New Admin

Polling trigger

In Zapier“Triggers when you want to get all Admins in your school from the API.”

Fires when an administrator account shows up in your Edusign school. You get the new admin as the starting point of the Zap, ready to pass to the next step.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a university IT team wants every new Edusign admin logged in its access review, so nobody keeps rights they should not have.
2

New Course

Polling trigger

In Zapier“Triggers when a user needs to get all courses from the API.”

Starts the Zap when a course appears in Edusign. It is the natural entry point for anything that should happen once a session is on the calendar.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a coding bootcamp wants each new course to produce its document for signature, without the program manager doing it by hand.
Watch out
if courses are created through Zapier too, do not write a course back into Edusign from this Zap: it would catch its own work and loop.
3

New Documents

Polling trigger

In Zapier“Triggers when you want to get all Documents in your school from the API.”

Picks up documents as they appear in your Edusign school. Each new one starts the Zap once, so you can react to paperwork as soon as Zapier sees it.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a corporate training team wants every new document noted in its own tracking, so compliance can see what has been issued.
4

New Documents Templates

Polling trigger

In Zapier“Triggers when you want to get all Documents Templates in your school from the API.”

Reacts to a new document template in your school. Useful when templates are the source of everything you send, and a new one should set something in motion.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a language school adds templates per program and wants a first document generated from each one, to check it before students see it.
5

New Professor

Polling trigger

In Zapier“Triggers when you want to get all professors from the API.”

Fires when a professor is added to Edusign. The Zap starts with that professor, whom you can then put on a course or tell someone about.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a university department wants each new lecturer to get a first course built with a placeholder date, so planning can start.
6

New Student

Polling trigger

In Zapier“Triggers when you want to get all Students in your school from the API.”

Each student who lands in Edusign kicks off the Zap. Each student is picked up once; Zapier keeps track of who it has already seen.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
an online academy wants every new learner sent their Edusign credentials again from a single place, once the account exists.
Watch out
a bulk import of a whole intake can return a large batch at once, and Zapier may hold it back as a flood.
7

New Group

Polling trigger

In Zapier“Triggers when a new group is created”

Picks up every group created in Edusign. Groups are how cohorts are organized, so this is the hook for anything tied to a class as a whole.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a business school wants every new cohort to get its first course created at once, with the program director as professor.
Actions

The 11 Edusign actions

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

1

Create Course (Group)

Action

In Zapier“Create a Course with groups Ids.”

Creates a course with a name, start, end, professor email and one or more group names. A group that does not exist yet is created along with the course.

When to use it
you plan by cohort and want each session to arrive with its whole class attached.
2

Create Course (Students)

Action

In Zapier“Creates a Course with Students”

Same idea, but you list students by email instead of groups. Name, start, end and professor email are required too.

When to use it
a workshop mixes learners from several cohorts and has no group of its own.
Watch out
the professor and every student must be created in Edusign before this step runs.
3

Create Document (From Template)

Action

In Zapier“Create a document using a school template”

Generates a document from one of your school templates, given its name and an admin email. By default it goes out for signature by email and is sent again once fully signed.

When to use it
a certificate or agreement should leave as soon as something upstream says so.
Watch out
turn on Sign with order if each recipient must wait for the previous one to sign.
4

Create Group

Action

In Zapier“Creates a Group”

Builds a group with a name and the emails of its students, separated by commas. It is how you set up a cohort in one go.

When to use it
an intake list is ready and the class should exist as a group before the timetable is drawn.
Watch out
each student must already exist in Edusign, or the step fails.
5

Create Professor

Action

In Zapier“Creates a Professor”

Creates a professor from a first name, last name and email. That email is then what the course actions use to attach them.

When to use it
a new trainer is hired and should be available for courses without anyone typing them in twice.
6

Create Student

Action

In Zapier“Creates a Student”

Adds a student to Edusign with a first name, last name and email. You can also ask Edusign to email them their credentials from the same step.

When to use it
your sign-up form or CRM holds new learners, and you want them in Edusign before the first class.
7

Delete Document

Action

In Zapier“Delete a document.”

Removes a document from Edusign, identified by its name. One of the few destructive steps here, so test it on a throwaway document first.

When to use it
a request is cancelled upstream and the matching document should not stay waiting for signatures.
8

Update Group

Action

In Zapier“Updates a Group by finding the group you want to update with the name you enter. Disclaimer: if you're trying to change the name of the group, you have to enter his ID at the end of the form or the group won't be find. If you aren't changing the name, you can just enter his name to find the group and not the ID.”

Edits a group, found by the name you enter. You also choose whether the students already in it stay there.

When to use it
a cohort is restructured mid-year and the group in Edusign has to match.
Watch out
renaming a group takes its ID at the end of the form; the name alone will not find it.
9

Update Professor

Action

In Zapier“Updates a Professor Disclaimer: if you're trying to change the mail of the professor, you have to enter his ID at the end of the form or the professor won't be find. If you aren't changing the mail you can just enter his mail and not the ID.”

Edits a professor already in Edusign, looked up by email. Keeps your teaching staff records aligned with wherever HR keeps them.

When to use it
a trainer's name was misspelled at creation and the fix should come from your main records.
Watch out
changing the professor's email itself needs their ID at the end of the form.
10

Update Student

Action

In Zapier“Updates a Student. Disclaimer: if you're trying to change the mail of the student, you have to enter his ID at the end of the form or the student won't be find. If you aren't changing the mail you can just enter his mail and not the ID.”

Changes an existing student, found by their email. It can also resend their credentials if you ask it to.

When to use it
a learner's details changed in your source system and Edusign should follow.
Watch out
to change the student's email itself, enter their Edusign ID at the end of the form, or the student will not be found.
11

File URL to Base64

Action

In Zapier“BETA - This Action only permit to transform a file URL to a base64 string, used to send a document to sign from a file URL.”

A helper rather than a business action: it turns a file link into a Base64 string, the format Edusign uses to send a file for signature from a link.

When to use it
a file sits behind a URL and a later step needs it converted.
Watch out
Edusign marks it BETA.
Searches

The 7 Edusign searches

7 search steps look for data that already exists in Edusign, so a later step can use it.

In the editor, searches sit at the bottom of the Action event list, under SEARCH. Some fields also offer + Add search step, which inserts the lookup just before and wires its result in. Three settings decide what happens when the lookup does not go to plan.

1

Find Admin

Search

In Zapier“Finds an Administrator in Edusign API”

Looks up an administrator by email and returns the admin record for later steps. The email is the only thing it asks for.

When to use it
a document action needs an admin and only the email travels in your Zap.
Watch out
whether it wants the exact address or something close is decided by Edusign, not Zapier, so map the email as stored.
2

Find Document

Search

In Zapier“Finds a Document in Edusign API”

Finds a document by its name, so a later step can act on that exact one rather than a guess.

When to use it
you need to confirm a document exists before deleting or reporting on it.
Watch out
if two documents share a name, the multiple-results setting decides which one moves on.
3

Find Document Template

Search

In Zapier“Finds a document template in Edusign API”

Retrieves a template by name. Handy to check the name you are about to use is the one Edusign knows.

When to use it
template names come from another tool and a typo would make the document step fail.
Watch out
if nothing matches, the Zap stops here unless you switch on the empty-result setting.
4

Find External

Search

In Zapier“Finds an external user in Edusign API”

Searches the external users of your Edusign account by email and hands back the one it matches.

When to use it
a guest speaker or outside signer has to be identified before the next step.
Watch out
there is no find-or-create version of this one, so a missing external user simply stops the Zap.
5

Find Group

SearchFind or create

In Zapier“Finds a Group in Edusign.”

Finds a group by name. Its find-or-create twin, Find or Create a Group, is the same search with the creation box ticked, not an extra operation.

When to use it
a course step needs a cohort that may or may not be set up yet.
6

Find Professor

SearchFind or create

In Zapier“Finds a Professor.”

Looks up a professor by email. Find or Create Professor is this same search with creation switched on, for when the trainer may be new.

When to use it
you want to attach a professor to a course without risking an unknown email.
7

Find Student

SearchFind or create

In Zapier“Finds a Student.”

Finds a student from their email. Tick creation and it becomes Find or Create Student, still one search, which adds the learner if missing.

When to use it
a group update should never break on a learner nobody created.
Watch out
once creation is ticked, the step asks for the fields needed to create the student, so have them ready in the Zap.

The three settings every search exposes

  1. Successful if no search results are found?
    Left as is, a search that finds nothing stops the Zap there and the steps that needed it are skipped. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Turns the search into a find-or-create: the setting above disappears and the step asks for what it needs to create the missing record.
  3. If multiple search results are found?
    Several matches: keep the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks

When an Edusign Zap breaks

Zapier attaches no help article to Edusign, and no app-specific rate limit is documented. What breaks comes from the way Edusign's actions expect data, and from Zapier's own rules.

Six cases worth knowing before you publish. If something still fails, the Zapier troubleshooting page is the next stop.

  • Students or professor missing

    Create Group and Create Course (Students) expect every person they list to exist in Edusign already. Create them earlier in the Zap or use a find-or-create search.
  • Email change without the ID

    Update Student and Update Professor find people by email. Changing that email itself needs the Edusign ID at the end of the form, otherwise nobody is found.
  • Renaming a group

    Update Group looks the group up by name. To rename it, give its ID at the end of the form, or the old name will not match anything.
  • Nothing from before

    A Zap only reacts to what happens after it is switched on. Students or courses already in Edusign are not picked up; moving that backlog is a separate job.
  • The Zap that feeds itself

    Watch New Course and create courses in the same Zap, and each new course sets it off again. The loop burns through your task count fast.
  • A whole intake at once

    After a bulk import, a trigger can return a huge batch in one go, and Zapier's flood protection may hold it back. Zapier still never runs the same item twice.
Need help

Need help automating Edusign with Zapier?

A person reads every message.

FAQ

Edusign and Zapier: the usual questions

01Is the Edusign Zapier integration free?
Yes, as far as Zapier is concerned. Edusign is not a premium app, so it works on the free plan, which gives you 100 tasks a month and unlimited Zaps, and none of the 7 triggers or 11 actions is locked behind a higher tier. The limit is in the shape of the Zap: on free, you get one trigger and one action. Add a filter, a search or a second action and the Zap needs a paid plan.
02How many tasks does an Edusign Zap use?
One per action that succeeds, and nothing else. The trigger is free, and so is every check Zapier makes on Edusign while it waits for a new student or course. An action that fails is not counted. So a Zap that creates a student then adds them to a group uses two tasks per new learner, while a single Create Student step uses one. Count your actions, multiply by your expected volume, and compare with the 100 tasks of the free plan.
03Does Edusign work in real time with Zapier?
No. All 7 Edusign triggers are polling triggers: Zapier asks Edusign for new items at a fixed interval, and that interval depends on your plan. It is 15 minutes on Free, 2 on Professional and 1 on Team and Enterprise. None of them is instant, so there is no way to make a new student or course show up the moment it is created. On paid plans you can also run a check by hand from the editor when testing.
04What does it take to connect an Edusign account?
An Edusign account, and access to the records you want Zapier to read or change. Then it takes three moves: open Apps in Zapier, click + Add connection and choose Edusign, sign in on the Edusign tab that opens and grant access. The connection is saved once and reused by every Edusign step afterwards. Use the school account the Zaps should act on, not a personal one, because every Zap will read and write with it.
05Why does Create Group fail on some students?
Because each student has to exist in Edusign before the group can include them. Create Group takes a comma-separated list of student emails, and an email Edusign does not know breaks the step. The same rule applies to Create Course (Students), for both students and professor. The fix is to put Create Student earlier, or run Find Student with creation switched on so a missing learner is added first. Tick that box and the step asks for the student's details.
06What if the Edusign action you need does not exist?
Check the searches first: with 7 of them, a lookup plus an update often covers what looks missing. If nothing fits, the 11 actions are the whole list Zapier offers today for Edusign, so no setting will reveal another one. At that point the options are a different automation platform, or asking Edusign directly. The team at Hack'celeration can look at the case with you if the workflow matters to your school.
07Zapier, Make or n8n for Edusign?
It depends on what matters most to you. Zapier wins on setup: the connection takes three steps and the free plan already runs Edusign. Every Edusign trigger is polling, and any Zap beyond two steps needs a paid plan, so those two facts weigh on the choice. For Make and n8n, check whether each one connects to Edusign and at what cost for your volume. Then compare the number of steps per run, how fresh the data has to be, and who on your team will maintain it.