The Digiforma × Edusign integration eliminates the need to re-enter your training sessions and attendance data in two separate tools. Digiforma remains the industry standard for scheduling; Edusign remains the industry standard for attendance tracking.
What Integration Does
It imports scheduled or completed sessions, their time slots, enrolled learners, and instructors from Digiforma into Edusign.
It automatically creates the missing students and instructors in Edusign when they can be unambiguously identified.
It sends the attendance records and signatures collected in Edusign to Digiforma.
It prevents duplicates and protects courses that have already been signed, locked, or completed.
Before starting
You must be an administrator of your Edusign organization and have a Digiforma subscription that includes access to the GraphQL API.
To generate your Digiforma token:
Log in to Digiforma.
In the advanced options, make sure the GraphQL API is available.
Open the API configuration page.
Click Generate a token.
Copy the token immediately and store it in a secure location.
Digiforma Documentation: GraphQL: The Digiforma API.
Connect Digiforma to Edusign
Install the Digiforma app from the Edusign Marketplace.
Open the app settings in Edusign.
Click Connect Digiforma.
Paste your Digiforma API token without adding the "Bearer" prefix.
Confirm the connection.
Edusign automatically sends the authorizations specific to your organization to the connector. You don't need to copy an Edusign API key. The Digiforma token is tested before being registered; once the connection is validated, the first synchronization starts automatically.
What data is synced?
Which Digiforma sessions are imported?
Only scheduled and approved sessions, as well as completed sessions, are imported into Edusign.
Project, draft, or in progress: No training sessions or courses have been created in Edusign.
Scheduled and confirmed session: It is imported during the next synchronization, which occurs automatically every 15 minutes by default or after a manual synchronization.
Session ended: It remains recognized by the connector, in accordance with the rules for protecting past courses.
Session already imported and then rescheduled: Existing items in Edusign are not automatically deleted. This protection prevents an accidental status change from deleting an operational schedule.
To make a session importable, open it in Digiforma, complete its scheduling, and then use the action to approve it and set it to "scheduled" status. It will then appear in Edusign during the next synchronization.
From Digiforma to Edusign
A Digiforma training session becomes an Edusign training session.
A Digiforma workshop becomes an Edusign course.
Registered learners become Edusign students.
The presenters become Edusign teachers.
The name, dates, times, location, participants, and presenters for the session are listed in Edusign.
The specific audiences for time slots and sub-sessions are honored when they are defined in Digiforma.
From Edusign to Digiforma
Only attendance data is sent:
a student's attendance or signature;
absence or lack of a signature, depending on the final status of the course;
a speaker's signature.
Changes to the name, schedule, room, participants, description, questionnaire, or any other field made in Edusign never affect Digiforma.
When does synchronization take place?
Digiforma to Edusign Schedule
Digiforma does not currently provide a webhook for session changes. By default, the connector checks Digiforma every 15 minutes. A new session or change will normally appear in Edusign during the next synchronization.
Edusign Sign-off to Digiforma
Edusign webhooks quickly notify you of signatures and course lockouts. A periodic check remains active as a backup in case an event is delayed or missed.
What happens when a course is modified in Digiforma?
Future course, unlocked, with no attendance or signature requirements: Eligible changes are applied in Edusign.
Future course with a presence, signature, lock, or sign-off already submitted: The Edusign course is protected and remains unchanged.
A class that started today before noon, is not locked, and has no attendance records: it can still be updated with the default settings.
A class that started today at 12:00 p.m.: It remains unchanged.
A course prior to today: It remains unchanged.
Courses for which the new Digiforma date has been moved to a past date: the existing Edusign course is not rewritten.
Historical class moved to a future date: It can be updated if it is unlocked and has not been signed off.
Invalid date, time, or time zone: The synchronization in question fails without sending an invalid course to Edusign.
The 12-hour limit is the default setting and can be adjusted. These safeguards prevent a last-minute change from invalidating signatures that have already been collected.
What if both Digiforma and Edusign have been modified?
By default, only the fields that have actually been modified in Digiforma since the last synchronization are applied in Edusign. Unrelated Edusign changes are retained.
Example: If the room is changed in Edusign and the schedule is then changed in Digiforma, the new schedule is applied, but the room entered in Edusign is retained. If the same field has been modified in both tools, Digiforma takes precedence for that field as long as the course is still editable.
An optional mode allows you to set Digiforma as the default for all managed fields: name, schedule, room, parent course, learners, and instructors.
What happens when a class is modified in Edusign?
A proof or a new signature can be sent to Digiforma.
The other changes are limited to Edusign.
Course schedules, locations, participants, and course information are never sent to Digiforma.
When are attendance records sent to Digiforma?
Final submission — default mode
Attendance records are sent when the Edusign course is locked. This mode is recommended when attendance should not appear in Digiforma until the course has been completed and verified.
Live streaming — optional
While a class is in session and not locked, any attendance updates can be quickly sent to Digiforma. When the course is then locked, the connector performs a final check. A status that has already been sent and remains unchanged is not sent a second time.
If a new signature is received while a shipment is already in progress, an additional verification is automatically scheduled to send the most recent status update.
Where can I view attendance records in Digiforma?
Open the relevant training session.
Go to " Tracking," then to the attendance log or attendance tracking.
Unfold the module, then the relevant section.
Registered learners and instructors must be listed along with their attendance records.
Why isn't a student showing up?
Check to see if it's in the " Pending Prospects " section of Digiforma. A pending prospect is not yet a learner enrolled in the session: Digiforma therefore does not assign them a sign-in record that the connector could update.
First, accept or convert the prospect into a registered student, verify their assignment to the session or time slot, and then wait for the next synchronization.
How are people identified?
The connector first checks for a known match—the Digiforma ID associated with the person in Edusign—and then for an identical email address. If no matching person exists, one is automatically created in Edusign.
A valid email address is required to create an account. If the same address already belongs to a person managed by another integration or is associated with another identifier, the match is blocked to prevent attendance from being attributed to the wrong person.
Can a presence be sent twice?
The connector stores a technical snapshot of the status that has already been sent. If neither the participants nor the attendance status has changed, it does not send the same information back to Digiforma. In the event of a new signature or a change in status, the new version is sent.
What happens if a synchronization fails?
Temporary errors, such as network unavailability or API rate limits, are automatically retried. If the error persists, the operation is retained for diagnostic purposes and can be restarted after the issue has been resolved.
Before sending, the connector verifies that all learners and facilitators for the session match across both tools. If a match is missing, the entire batch is put on hold to prevent a partial record or one assigned to the wrong people.
What happens if a time slot is deleted in Digiforma?
By default, the corresponding course is not automatically deleted from Edusign.
A controlled deletion option can be enabled. It applies only to a course created through integration, scheduled for the future, unlocked, with no signature or attendance requirement, and whose deletion has been confirmed directly in Digiforma. Learners, instructors, historical training sessions, and courses that have already begun are never automatically deleted.
Can we import past courses?
Not by default. A historical restore can be enabled for a specified period. However, historical training sessions that have already been synchronized remain protected from automatic changes.
What options can be adapted?
The synchronization frequency.
Submitting attendance records in a single batch or in real time.
The possible import of a past period.
The deadline for same-day updates.
Digiforma's partial or full priority on managed fields.
The controlled removal of future courses that have been discontinued in Digiforma.
Independent activation of schedule import and attendance submission.
The default settings prioritize signature protection, the retention of unrelated Edusign changes, and no automatic deletion.
What data isn't synced?
Companies, customers, and investors.
Programs, modules, objectives, and fees.
Invoices.
Documents, certificates, evaluations, and questionnaires.
The Edusign Groups.
Profile changes made after a person has been created.
Schedule changes from Edusign to Digiforma.
Attendance records from Digiforma to Edusign.
Deletion of individuals or training programs.
How are login credentials and data protected?
Edusign keys and Digiforma tokens are encrypted before being stored and are never displayed in the user interface. The connector does not store the signatures themselves, the full bodies of the webhooks, phone numbers, or the participants' full profiles. It retains only the mappings and technical information necessary for synchronization, duplicate prevention, and diagnostics.
How do I replace a Digiforma token?
Open the Digiforma app settings in Edusign again, click " Connect Digiforma," and then enter the new token. It is checked before replacing the old one.
What happens if the app is uninstalled?
Uninstalling the connector stops synchronization and deletes the credentials, mappings, and technical history stored by the connector for your organization. It does not automatically delete training programs, courses, learners, instructors, or attendance records already in Edusign or Digiforma.
What should you check if nothing seems to be syncing?
The Digiforma session has been scheduled and approved: a session that is still in the planning stage, a draft, or currently being planned will not be imported.
The Digiforma token is still valid, and the GraphQL API option is included in your subscription.
The student is enrolled in the session, not just listed as a prospective student on the waiting list.
The time slot includes at least one identifiable participant.
The class has not been scheduled, is locked, or has already been signed up for while you are waiting for a schedule update.
In final submission mode, the Edusign course has indeed been locked.
You waited up to 15 minutes for a change from Digiforma.
If the problem persists, contact Edusign Support and provide the name of the organization, the Digiforma session, the time slot, and the Edusign course in question. Never share your API token in an unsecured support conversation.