Here’s a sample workflow to demonstrate the use of the GSuite Orchestration app to automate employee onboarding use case in an organization.
Create an event when a Service request is raised.
Followed by the condition to ensure the Service request is Employee Onboarding for Gsuite.
You can then pull in the App Node which will have the following configurations:
App Name: GSuite - Orch
App Action: Get User
Notes when Configuring Inputs:
user_key: The value can be the user's primary email address, alias email address, or unique user ID.
view_type: Gsuite account view type to fetch the administrator-only or domain-wide public view of the user. Acceptable values are:
admin_view: Results include both administrator-only and domain-public fields for the user.
domain_public: Results only include fields for the user that are publicly visible to other users in the domain.
To validate whether the user exists or not a condition node is added with system_message Not Found or status code is 404.
If the user is not found you can then pull in the App Node which will have the following configurations:
App Name: GSuite - Orch
App Action: Create User
If the user creation is successful you can then pull in the App Node which will have the following configurations:
App Name: GSuite - Orch
App Action: Get Group Details
To validate whether the group exists or not a condition node is added with the status code as 200.
If the group is found you can then pull in the App Node which will have the following configurations:
App Name: GSuite - Orch
App Action: Assign Member to Group
Notes when Configuring Inputs:
group_key: It is the email address or id of the group which we can get in the response of the app action Get group details and you can pass it via placeholder as shown below.
email: It is the email address of the user who needs to be added to the group so we can get it in the Create User action response and can pass it via placeholder as shown below.
To validate whether the user is assigned to a group or not a condition node is added to check whether the status code is in between 200 - 300.
If the workflow is successfully executed add a note using the action node.
