Create Reusable Custom Action and use in Playbooks

Prerequisites

• Google Workspace integration connected in Zluri
• Google Workspace admin account with user management permissions

Step 1: Open Custom Actions

1. Open the Zluri dashboard
2. Navigate to Settings > Custom Actions
3. Select Create Custom Action

[Add screenshot: Open Custom Actions]

Step 2: Select the application

1. Select Google Workspace from the application list
2. Zluri uses the connected Google Workspace authentication
3. OAuth tokens and API authentication are handled automatically

[Add screenshot: Select application]

Step 3: Configure basic action details

Action name

Update Job Title in GWS

Use a clear and descriptive name for identification during playbook creation.

[Add screenshot: Action name]

Step 4: Define input fields

Input fields appear during playbook configuration.

Field: Job Title

• Field name: jobTitle
• Description: Enter the new job title for the user
• Required: Yes

[Add screenshot: Input field configuration]

Step 5: Configure API details

HTTP method

• Select PUT to update existing user data

API endpoint URL

https://admin.googleapis.com/admin/directory/v1/users/{{user.user_email}}

Headers**(Optional)**

Leave this section empty. Zluri applies the required authentication headers automatically.

Step 6: Configure request body

Add the following JSON payload in the Body section:

{
"organizations":[
{
"title":"{{input_field.jobtitle}}",
"primary":true
}
]
}

The {{input_field.jobtitle}} value resolves dynamically during execution.

Step 7: Save and test

1. Select Save Custom Action.
2. The action becomes available across playbooks.

Step 8: Use the Custom Action in playbooks

1. Add the Custom Action to any playbook.

   

2. Configure the input field value during setup. Input values support static values or dynamic inputs.

   

Supported variables in Custom Actions

User attributes

• user.user_id
• user.user_email
• user.user_name
• user.user_designation
• user.user_status
• user.user_role
• user.user_department_name
• user.user_reporting_manager_name

Application attributes

• app.app_id
• app.app_name
• app.app_status
• app.app_owner_name
• app.app_owner_email
• app.app_financial_owner_name
• app.app_financial_owner_email
• app.app_technical_owner_name
• app.app_technical_owner_email