Actions7
- GDAP Actions
- Tenant Actions
- User Actions
Overview
This node integrates with the CIPP API to create a new user within a specified tenant environment. It is designed for scenarios where automated user provisioning is needed, such as onboarding new employees or managing user accounts across multiple tenants programmatically. By specifying user details and attributes, administrators can streamline user creation workflows without manual intervention.
Practical examples include:
- Automatically creating users in a multi-tenant system when new hires are added in an HR system.
- Bulk provisioning users with specific licenses and domain assignments.
- Setting up user profiles with detailed attributes like job title, department, and manager information.
Properties
| Name | Meaning |
|---|---|
| Tenant Name or ID | Select the tenant where the user will be created. Can choose from a list or specify an ID via expression. |
| Display Name | The full display name of the user. |
| First Name | User's given (first) name. |
| Last Name | User's surname (last name). |
| User Name | The username for the new user account. |
| Primary Domain | The primary domain associated with the user. Options depend on the selected tenant. |
| Usage Location | The usage location code for the user, defaulting to "US". |
| Licenses Names or IDs | One or more license identifiers to assign to the user. Options depend on the selected tenant. |
| Automatic Password | Boolean flag indicating whether to automatically generate a password for the user. Defaults to true. |
| Must Change Password | Boolean flag indicating if the user must change their password upon first login. Defaults to true. |
| Copy From | Username or identifier of an existing user whose settings should be copied to the new user. |
| Additional Attributes | A collection of optional user attributes including: Business Phone, City, Company Name, Country, Department, Job Title, Mobile Phone, Postal Code, Street Address, and Manager (specified by user principal name). |
Output
The node outputs JSON data representing the newly created user object as returned by the CIPP API. This typically includes all user properties set during creation along with any additional metadata assigned by the system.
If the node supports binary data output (not indicated here), it would represent related files or attachments linked to the user profile, but this node primarily deals with JSON user data.
Dependencies
- Requires an API key credential configured for authenticating with the CIPP API.
- Needs access to the CIPP API base URL, which is set in the node credentials.
- Dependent on dynamic loading methods to populate options for tenants, domains, licenses, and roles based on the current tenant context.
Troubleshooting
- Common issues:
- Invalid tenant or domain selection may cause API errors; ensure correct tenant and domain IDs are used.
- Missing required fields like username or display name can result in validation errors.
- License assignment failures if licenses do not exist or are incompatible with the tenant.
- Error messages:
- Authentication errors indicate missing or invalid API credentials.
- Validation errors from the API usually specify which field is incorrect or missing.
- Network or timeout errors suggest connectivity issues with the CIPP API endpoint.
- Resolutions:
- Verify API credentials and permissions.
- Double-check input property values, especially tenant, domain, and license selections.
- Ensure network connectivity and correct API base URL configuration.
Links and References
- n8n Expressions Documentation
- CIPP API documentation (refer to your organization's internal API docs or portal for detailed endpoints and payloads)