Short answer: Drop the "Acadle → Enroll Student in Course" 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 |
|---|---|---|---|
Course ID course_id | string | Required | The Course ID assigned by Acadle. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Email email | string | Required | The email address. Used as the recipient or identifier depending on context. |
Name name | string | Optional | Used when creating the account if user doesn't exist. |
{"course_id": "{{trigger.course_id}}","email": "learner@example.com","name": "{{trigger.name}}"}
{"status": "enrolled","user_id": "usr_xyz","course_id": "course_abc","enrollment_id": "enr_abc"}
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.