Actions57
- Course Actions
- User Actions
- Assignment Actions
- Module Actions
- Page Actions
- Discussion Actions
- File Actions
- Announcement Actions
- Quiz Actions
- Submission Actions
- Enrollment Actions
- Group Actions
- Rubric Actions
Overview
This node integrates with the Canvas LMS API to manage courses and other related resources. Specifically, for the Course - Delete operation, it allows users to delete a course by specifying its unique Course ID. This is useful in scenarios where courses are no longer needed or were created in error and need to be removed from the Canvas system.
Practical examples:
- Automatically deleting outdated or test courses as part of a cleanup workflow.
- Removing courses that have been completed or canceled without manual intervention.
- Integrating course deletion into larger automation pipelines involving course lifecycle management.
Properties
| Name | Meaning |
|---|---|
| Course ID | The unique identifier of the course to delete. Required for delete, get, and update operations on courses. |
| Trigger | Options to trigger workflows based on course events: "New Course" (when a new course is created) or "Course Updated" (when a course is updated). Not directly related to delete but available for course resource triggers. |
| Polling Interval | How often to poll the Canvas API for changes/events. Options: Every 5, 10, 15, 30 minutes, or every hour. |
Output
The output JSON contains a data field which holds the response from the Canvas API after performing the delete operation. Typically, for a delete operation, this may be an empty object or confirmation message depending on the API's response.
Example output structure:
{
"data": {
// Response details from Canvas API about the deletion
}
}
No binary data output is involved in the delete operation.
Dependencies
- Requires an API key credential for authenticating with the Canvas LMS API.
- The node uses the Canvas API base URL and access token configured in the credentials.
- Network connectivity to the Canvas LMS instance is necessary.
- No additional external dependencies beyond the Canvas API and n8n's HTTP request helpers.
Troubleshooting
Common issues:
- Invalid or missing Course ID will cause the API call to fail.
- Insufficient permissions or invalid API token can result in authorization errors.
- Network issues or incorrect Canvas API URL configuration can cause connection failures.
Error messages:
"Error in "course" operation "delete": <message>"indicates a failure during the delete API call. Check the Course ID and API credentials.- API errors returned by Canvas (e.g., 404 Not Found if the course does not exist, 403 Forbidden if unauthorized).
Resolutions:
- Verify the Course ID is correct and exists in Canvas.
- Ensure the API key has sufficient permissions to delete courses.
- Confirm the Canvas API URL and network access.
- Use the node's "Continue On Fail" option to handle errors gracefully in workflows.