- Home
- Resources
- Integrations
- Edusign
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
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.
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.
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 Edusign to Zapier in 3 steps
- 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.
- 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.
- 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.
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.
- 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.
- 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.
- 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.
- 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.
- 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.
The 7 Edusign triggers
7 events start a Zap when something happens in Edusign. Zapier checks for them at the interval your plan allows.
New Admin
Polling triggerIn 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.
New Course
Polling triggerIn 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.
New Documents
Polling triggerIn 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.
New Documents Templates
Polling triggerIn 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.
New Professor
Polling triggerIn 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.
New Student
Polling triggerIn 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.
New Group
Polling triggerIn 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.
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.
Operations index
Create Course (Group)
ActionIn 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.
Create Course (Students)
ActionIn 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.
Create Document (From Template)
ActionIn 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.
Create Group
ActionIn 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.
Create Professor
ActionIn 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.
Create Student
ActionIn 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.
Delete Document
ActionIn 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.
Update Group
ActionIn 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.
Update Professor
ActionIn 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.
Update Student
ActionIn 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.
File URL to Base64
ActionIn 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.
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.
Find Admin
SearchIn 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.
Find Document
SearchIn 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.
Find Document Template
SearchIn 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.
Find External
SearchIn 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.
Find Group
SearchFind or createIn 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.
Find Professor
SearchFind or createIn 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.
Find Student
SearchFind or createIn 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.
The three settings every search exposes
- 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.
- 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.
- 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 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 automating Edusign with Zapier?
A person reads every message.



