Short answer: Drop the "EzyCourse → Enroll Student" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Student Email email | Required | Email of the student to enroll | |
Course ID course_id | string | Required | The course ID to enroll the student in |
Full Name full_name | string | Optional | Student's full name (required if new student) |
{"email": "e.g. user@example.com","course_id": "e.g. 1001","full_name": "{{trigger.full_name}}"}
{"message": "Student enrolled successfully","success": true,"enrollment": {"course_id": 1001,"student_id": 5001,"enrolled_at": "2025-03-15T12:00:00Z"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.