Skip to content
Edusign logo

Connectors / Operations · HTTP Connector

Automate Edusign with Tray.ai

Create a course, create a student and create a professor in Edusign, and start a workflow when Edusign sends “Course created”.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.

See all connectors

What can you do with Edusign on Tray.ai?

Edusign is a digital attendance tool for schools and training providers, where students sign in to courses electronically and staff track absences and send documents for signature. Tray.ai connects to Edusign through the HTTP Connector, so your workflows can call the Edusign API alongside the rest of your stack.

  • When Edusign sends “Student signed”, mark attendance on the student's record in your student information system.
  • When Edusign sends “Absence justified”, update the learner's record in your training management system.
  • Create a student for each enrollment your CRM records.
  • Create a course whenever your scheduling system publishes a new session.
Connects through
HTTP Connector
Authentication
A bearer token
Base URL
https://ext.edusign.fr

Set it up

Connect Edusign to Tray.ai

Each step uses Edusign's own API details, from its documentation.

Step 1

Save Edusign's API token

Save the token Edusign issues as a Tray.ai authentication. The HTTP Client sends it as a bearer token on every call. The token stays out of the workflow and out of the logs.

Step 2

Point the HTTP Client at the API

Add an HTTP Client step and use https://ext.edusign.fr as the base URL. Or paste a cURL example from Edusign's API docs, and Tray.ai fills in the method, URL, and headers.

Step 3

Start with “List courses”

It's one of 21 documented actions, under Courses. The response comes back as data the next step can map into your other apps.

Step 4

Start workflows from Edusign events

Give Edusign the URL of a Tray.ai webhook trigger. “Course created” can then start a workflow, and so can 6 other events.

What the Edusign API covers

5 resources and 21 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Connecting it takes a few clicks: here's how.

Courses

  • Create a course
  • List courses
  • Update a course
  • Delete a course
  • Add a student to a course

Students

  • Create a student
  • List students
  • Update a student
  • Archive a student

Professors

  • Create a professor
  • List professors
  • Update a professor
  • Archive a professor

Groups

  • Create a group
  • List groups
  • Update a group
  • Archive a group

Justified absences

  • Create a justified absence
  • List justified absences
  • Update a justified absence
  • Delete a justified absence

Events Edusign can send to a Tray.ai webhook trigger

  • Course created
  • Course edited
  • Course deleted
  • Course locked
  • Student signed
  • Student created
  • Absence justified

Checked against Edusign's own documentation on 2026-10-22

developers.edusign.com/docs/api-reference

Frequently asked questions

What can a Tray.ai workflow do in Edusign?

+

The Edusign API documents 21 actions across 5 resources (Courses, Students, Professors, Groups, Justified absences). For example: Create a course; Create a student; Create a professor. A workflow can make any documented call through the HTTP Connector.

How does Tray.ai authenticate with Edusign?

+

The Edusign API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

Which Edusign events can start a Tray.ai workflow?

+

Edusign sends 7 events to a webhook URL, for example: Course created; Course edited; Course deleted; Course locked; Student signed; Student created; Absence justified. A Tray.ai webhook trigger receives them and starts a workflow.

See Edusign working against your stack.

We'll walk through a tailored demo with your systems plugged in.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.