Short answer: You can get ezycourse student in EzyCourse by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the EzyCourse Get EzyCourse Student action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Student ID studentId | string | Required | The student ID to retrieve |
{"studentId": "e.g. 5001"}
{"id": 5001,"email": "jane@example.com","phone": "+1234567890","status": "active","full_name": "Jane Smith","created_at": "2025-02-10T08:30:00Z","enrolled_courses": 3}
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.