Cativa

Consume Cativa API

Actions15

Overview

This node interacts with the Cativa API to manage group memberships within courses. Specifically, for the "Group" resource and the "Remove from Course" operation, it removes a user (identified by their email) from a specified course group. This is useful in scenarios where you need to automate the unenrollment of users from courses, such as when managing access control or cleaning up inactive users.

Practical examples:

Automatically remove students from a course after they complete it.
Revoke access for users who no longer meet certain criteria.
Integrate with HR or CRM systems to keep course enrollments up-to-date.

Properties

Name	Meaning
Email	The email address of the user to be removed from the course. Example: `[email protected]`
Course ID	The unique identifier of the course from which the user will be removed.

Output

The output is a JSON object (or array of objects) representing the result of the removal operation. If an error occurs and "Continue On Fail" is enabled, the output will include an error field with the error message.

Example output:

[
  {
    "success": true,
    "message": "User removed from course"
  }
]

Or, on error (with continue on fail):

[
  {
    "error": "User not found in course"
  }
]

Dependencies

External Service: Requires access to the Cativa API.
API Key: You must configure valid Cativa API credentials in n8n under the name cativaApi.

Troubleshooting

Common issues:

Invalid Email or Course ID: If the provided email or course ID does not exist, the node may return an error message such as "User not found in course" or "Course not found".
Authentication Errors: If the API credentials are incorrect or missing, you may see errors like "Authentication failed" or "401 Unauthorized". Ensure your credentials are set up correctly in n8n.
Network Issues: Connectivity problems can cause timeouts or network-related error messages.

How to resolve:

Double-check the email and course ID values.
Verify that your Cativa API credentials are correct and active.
Ensure the Cativa API service is reachable from your n8n instance.