Actions178
- Drive Actions
- Drive > Activity Actions
- Drive > Activity > Report Actions
- Drive > Files Actions
- Drive > Files > Action Actions
- Drive > Files > Archive Actions
- Drive > Files > Category Actions
- Drive > Files > Category > Right Actions
- Drive > Files > Dropbox Actions
- Drive > Files > External Import Actions
- Drive > Files > Favorite Actions
- Drive > Files > File/Directory Actions
- Drive > Files > File/Directory > Access Actions
- Drive > Files > File/Directory > Access > Invitation Actions
- Drive > Files > File/Directory > Access > Request Actions
- Drive > Files > File/Directory > Access > Teams Actions
- Drive > Files > File/Directory > Access > Users Actions
- Drive > Files > File/Directory > Comment Actions
- Drive > Files > File/Directory > Upload Actions
- Drive > Files > File/Directory > Upload > Session Actions
- Drive > Files > File/Directory > Version Actions
- Drive > Files > Search Actions
- Drive > Files > Share Link > Archive Actions
- Drive > Files > Share Link > Manage Actions
- Drive > Files > Trash Actions
- Drive > Invitations Actions
- Drive > Settings Actions
- Drive > Statistics Actions
- Drive > Users Actions
- Others Actions
- Users Actions
Drive > Users → Create User
AI-generatedSummary
Create user in Infomaniak Kdrive with role, access level, and optional invitation settings.
Inputs
- authentication — Authentication method for the Infomaniak API request. Default is OAuth2; API Key is an alternative if configured.
- path_drive_id (required) — Drive identifier. Must be provided to specify which drive the user is created in.
- queryParameters — Optional query parameters collection. Allows loading additional data about a resource, which may include related resources via the 'query_with' parameter.
- body_role (required) — Administration level of the user. Options: admin (full drive management), external (access only to files given by other roles), user (internal user managing own private and other directories' file access).
- bodyParameters — Optional body fields collection for fine-grained user configuration. Supported sub-fields: body_emails (json), body_file_id (number, associates a shared file), body_lang (options: de, en, es, fr, it - invitation language fallback), body_message (string), body_name (string, resource name), body_right (options: manage, none, read, write - access level of {name}), body_send_email (boolean), body_team_ids (json), body_type (options: main, shared - note: no longer used, replaced by external), body_user_ids (json).
- returnFullResponse — If true, the full API response is returned as workflow data. Defaults to false, returning only the created user item.
Output shape
Depends on returnFullResponse setting. When false, returns the n8n item representing the created user. When true, returns the complete Infomaniak API response payload.
User is created in the specified Infomaniak Kdrive with the given role and optional invitation email/file association. Side effect: invitation email may be sent if body_send_email is true and valid email/contact info is provided via body_emails or body_user_ids.
Examples
Example 1: Create a standard internal user in drive ID 123 with invitation email.
path_drive_id: 123; body_role: user; body_send_email: true; body_emails: {email: 'user@example.com'}; body_name: 'John Doe'