Actions
Create User
Creates a user.
Basic Parameters
| Parameter | Description |
|---|---|
| Change Password At Next Login | Indicates if the user is forced to change their password at next login. This setting doesn’t apply when the user signs in via a third-party identity provider. |
| Family Name | The user’s last name. Required when creating a user account. |
| First Name | The user’s first name. Required when creating a user account. |
| Password | User’s password. |
| Primary Email | The user’s primary email address. This property is required in a request to create a user account. The primaryEmail must be unique and cannot be an alias of another user. |
Advanced Parameters
| Parameter | Description |
|---|---|
| Custom Fields | A JSON object of Custom fields of the user. The custom fields are grouped by schema in standard JSON format.Single-valued custom fields are set as simple key-value pairs, like “field1”: “value1”.Multi-valued custom fields are set as arrays of objects, like the standard multi-value fields in the API such as organizations and relations.Example: {"schema1": { "field1": "value1", "field2": [ { "value": "value2a" }, { "value": "value2b" }, ... ], ...},"schema2": { "field3": "value3", ...},...} |
| Delegated User Override | Perform the action on behalf of another user, overriding the delegated user defined in the connection.If not specified, the delegated user is the one provided in the connection.Has no effect when using an OAuth connection.NOTE: the connection details are not edited by this input. |
| External IDs | A JSON list of external IDs for the user, such as an employee or network ID. The maximum allowed data size for this field is 2Kb.Example input with detailed fields: [{ "value": "The value of the external ID.", "type": "The type of external ID. If set to custom, customType must also be set. Acceptable values: account, custom, customer, login_id, network, organization.", "customType": "If the external ID type is custom, this property contains the custom value and must be set."}] |
| Organizations | A JSON list of organizations the user belongs to. The maximum allowed data size for this field is 10Kb.Example input:[ { “name”: “The name of the organization.”, “title”: “The user’s title within the organization. For example, member or engineer.”, “primary”: boolean to indicate if this is the primary org of the user, a user can have only one “type”: “work”, “description”: “The description of the organization.”, “department”: “Specifies the department within the organization, such as sales or engineering.” }] |
| Relations | A JSON list of the relationships of the user to other users. The maximum allowed data size for this field is 2Kb.Example input with detailed fields: [{ "value": "The name of the person the user is related to.", "type": "The type of relationship. If set to custom, customType must also be set. Acceptable values: admin_assistant, assistant, brother, child, custom, domestic_partner, dotted_line_manager, exec_assistant, father, friend, manager, mother, parent, partner, referred_by, relative, sister, spouse.", "customType": "If the relationship type is custom, this property contains the custom value and must be set."}] |
| Secondary Email | This is the email address where the new user receives their new account details. Also functions as the user’s recovery email. |
Example Output
Workflow Library Example
Create Temporary User with Google Workspace
Preview this Workflow on desktop
Was this page helpful?