Edusign
Education & LMSConnect AI agents to Edusign, a digital attendance and signature platform for schools and training organizations. Agents manage students, courses, and groups, send signature requests, and mark attendance states so attendance records complete themselves without paper sheets.
What This Integration Enables
Edusign is not a learning platform, and reading it as one leads you to the wrong flows. It is an evidence platform. Every operation in this connector exists to produce a single artifact, the signed attendance sheet for a session, and the record of who was in the room that a school or training organization keeps afterward. Students, courses, groups, and professors are here because the sheet needs them. Signature links, QR codes, email requests, present, absent, and late states, and the lock that generates the PDF are the actual product.
The connector spans both API generations Edusign exposes: the v3 endpoints for records and the v1 endpoints for attendance and signatures. Two limits are worth stating plainly. The connector requests and records signatures, it does not verify identity, so your own rules about who may sign for whom still govern what the sheet means. And signature links are bearer links, which means anyone holding one can open the signing surface for that student, so treat them like credentials rather than like reminders. Because the learners in these records are frequently students and sometimes minors, the sound default is to keep profiles inside Edusign and pass identifiers between systems, rather than copying rosters into every tool that touches the schedule.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Sessions provisioned from the timetable
The timetable is the source of truth and nobody wants to maintain it twice. Each week the agent reads the coming sessions from the institution's schedule in Google Calendar and runs Create Course for each one, passing ISO 8601 start and end times with a timezone and assigning the professor. It resolves cohorts through Get Groups and calls Assign Students To Course with the group IDs, which sets the expected roster in one call rather than per student. When a session moves, Update Course reschedules it. The attendance surface exists for every class before the class does.
Remote and hybrid cohorts signing on time
A hybrid session has ten students in the room and eight joining remotely. At the start of the session the agent runs Get Signature QR Code and posts it to the professor, who displays it in class. For the remote group it runs Send Signature Emails targeted at only those student IDs. Fifteen minutes before the end it runs Get Course Attendance, and if anyone remote is still unsigned it sends a single follow-up rather than a stream of them. Signature links from Get Signature Links go to the student's own address and nowhere else, because a link that opens a signing surface for a named person should not sit in a shared channel.
Attendance patterns that reach a tutor, not a report
Attendance data is most useful before it becomes a statistic. Weekly, the agent runs Get Course Attendance across a cohort's sessions and looks for patterns a single class cannot show, such as a student absent from the same slot three weeks running. It posts that pattern to the cohort tutor in Slack with the sessions and dates, and asks nothing else of the system. The tutor decides whether this is a timetable clash, a transport problem, or something that needs a conversation with the student or their guardian. The agent does not contact the student, and it does not decide what the pattern means.
Human-in-Loop Highlight
Lock Course is the commit point of this entire connector. It stops further signatures and generates the final attendance sheet, the document the institution keeps and produces when someone asks who was there. Everything before it is editable. The sheet is what remains. The hard part is never the lock itself, it is the handful of students who did not sign, because the connector offers exactly two ways to resolve them and one of them means asserting something the agent cannot know. Mark Student Absent records what the system observed. Mark Student Present records that a named person was physically in a room, on evidence that consists of somebody saying so.
So the agent chases signatures freely and never resolves the gap itself. It posts to the session owner: "Session INFO-204, Tuesday 09:00 to 11:00, Prof. Lemaire. 22 of 25 signed. Unsigned: Camille R (no email on record), Yanis B (email sent 11:02, not opened), Théo M (marked late by the professor at 09:20, never signed). Mark any of these present, mark them absent, or leave the session unlocked and chase again tomorrow?" Chasing a signature costs nothing and needs no approval. Writing presence into the record is a claim the institution will stand behind later, and that belongs to a person who was close enough to the room to make it.
Agent Capabilities
26 actionsStudents
6- Create Student Creates a student with first and last name required, and optionally an email for login credentials, a phone number, tags, and an external reference ID for syncing with your own system. That external reference is what keeps the two systems joined without duplicating profiles.
- Get Students Returns a paginated list of students, up to 100 per page, with pagination metadata. Used for reconciliation sweeps.
- Get Student Returns a single student by Edusign ID with contact details, tags, and external reference identifiers. Used once an ID is known.
- Update Student Updates only the fields you supply and leaves the rest untouched. Used to correct contact details or refresh the external reference after a change in the source system.
- Archive Student Soft-deletes a student, removing them from active lists while preserving their historical attendance records, and archived students can be restored from the Edusign interface. The correct move when a student leaves, precisely because the attendance history survives.
- Search Students Looks up students by email, external reference ID, or username. The reconciliation key when your system holds an identifier and not an Edusign ID.
Courses
6- Create Course Creates a course session with a start and end time in ISO 8601 with a timezone, assigning at least one professor, and optionally attaching students, a classroom, and a description. The provisioning call behind any timetable sync.
- Get Courses Returns a paginated list of sessions filterable by date range, name, professor, group, or student, optionally embedding attendee and staff details. Used to find the sessions a flow should act on today.
- Get Course Returns a single session with its schedule, classroom, assigned teachers, and enrolled students. Used to verify a session before touching its attendance.
- Update Course Updates only the fields you supply, so a session can be renamed, rescheduled with new ISO 8601 times, moved to another classroom, or re-described without rebuilding it.
- Delete Course Permanently deletes a session and cannot be undone, which takes the attendance record for that session with it. Where the goal is to keep history, archive or lock rather than delete.
- Assign Students To Course Sets who is expected to attend and sign, accepting student IDs, group IDs, or both. This replaces the roster rather than adding to it, so send the complete intended set.
Groups
3- Create Group Creates a student group, a class or cohort, so many students can be attached to a session at once. Returns the group ID used by the course roster call.
- Get Groups Returns a paginated list of groups with pagination metadata. Used to resolve a cohort name into an ID.
- Set Group Members Replaces a group's entire membership with the supplied set, removing any student not in the list. A full replace, so build the complete roster before calling it rather than sending a delta.
Professors
2- Create Professor Creates an instructor with first and last name required, and an email so Edusign can send them signing invitations. Returns the professor ID needed when creating sessions.
- Get Professors Returns a paginated list of professors with pagination metadata. Used to resolve staff assignments during timetable provisioning.
Attendance and Signatures
9- Get Course Attendance Returns the detailed attendance and signature state of a session, including each student's presence state and signature timestamp, professor signatures, and the generated sheet URL once the session is locked. The read that every attendance decision starts from.
- Get Signature Links Returns per-student signature links for online signing. Bearer links by nature, so route each one to its own student and keep them out of shared channels.
- Get Signature QR Code Returns the code a professor displays in class for in-person signing, requiring both the course ID and that session's professor ID. The in-room half of a hybrid signing flow.
- Send Signature Emails Emails the session's students to request their signature, optionally targeting a subset by ID. Safe to run on a schedule, which is why the workflow above lets the agent chase without asking.
- Lock Course Locks a session so no further signatures can be added and generates the final attendance sheet. The commit point, and the step this page puts behind a named person.
- Unlock Course Unlocks a previously locked session so signatures and changes can be made again. Used when a genuine correction is needed after the fact, which should leave a trail of its own in whatever system requested it.
- Mark Student Present Marks a student present when they cannot sign digitally. An assertion about a person's physical presence, so it belongs to a human decision rather than a rule.
- Mark Student Absent Marks a student absent for the sheet and downstream reporting. The default resolution when a signature never arrives and nobody vouches otherwise.
- Mark Student Late Marks a student as arriving late, optionally recording the delay in minutes. Used where the professor has observed the arrival and wants it on the record.
Frequently Asked Questions
What can FlowRunner do with Edusign?
FlowRunner agents can run Create Student, Get Students, and Get Student in Edusign, plus 23 more actions.
Does connecting Edusign to FlowRunner require OAuth?
No. Edusign connects to FlowRunner with an API key, no OAuth flow required.
Can Edusign trigger a FlowRunner workflow automatically?
Edusign doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Edusign
$100 in credits. No card required. Connect in minutes.