Sync Oomnitza with Zendesk to gain visibility of user data.
The following types of integrations are available:
-
Zendesk User Load (OAuth 2.0) — client credentials. You must choose this option.
-
Zendesk User Load (basic auth)
- Although this option is available, it is to be deprecated on 30 April 2027 and is not to be used to create new Zendesk user integrations. See Announcing the removal of API tokens as an authentication method for API requests.
-
If you edit a Zendesk User Load (basic auth) that was previously created, your credentials become invalid and you must create a new extended user integration that uses OAuth 2.0 client credentials.
Contents
- Before you start
- Setting the Zendesk domain as a global variable
- Creating the user integration
- Creating custom mappings
- Creating API block workflows
- Creating SaaS user workflows
Before you start
To easily find the records that are uploaded to Oomnitza, it's best practice to create a dedicated user account for each integration. This will make it easier for you to retrieve the records that are uploaded to Oomnitza from the vendor application.
To create the Zendesk user integration in Oomnitza, you must:
- Add OAuth 2.0 credentials to Oomnitza. See Adding credentials.
- Add your subdomain. For example, if your Zendesk URL is
https://mycompany.zendesk.com, your subdomain ismycompany. - The roles that you want to retrieve data for such as end-user, agent, or admin. See Zendesk: Users.
Setting the Zendesk subdomain as a global variable
Add the value as a global variable so that when you create workflows that use presets the variable is automatically added. See Adding global settings.
The name of the global variable is
Zendesk.Subdomain. The value is your subdomain.
Creating the user integration
- In Oomnitza, click Configuration > Integrations > Overview.
- Click Block view
.
- On the Integrations page, scroll down to the Extended section for user integrations.
- Click NEW INTEGRATION.
- In the sidebar, search for the integration.
- Click ADD.
Integration details overview
More information is provided about the following fields to help you complete the integration:
- User only. Add user records.
- User plus SaaS user. Add user and SaaS user records.
The benefit of adding SaaS user records is that you can run a workflow to validate the status and activity of SaaS users and retrieve information such as the role of the SaaS user. The information that can be retrieved depends on whether SaaS user workflows are available for the integration.
Installation types
- Cloud. Store credentials in the Oomnitza cloud.
- Local. Store credentials locally. If you want to sync Oomnitza with vendor applications that require AWS or OAUTH authentication, select cloud as the type of installation. Local installations don't support AWS and OAuth authentication.
Integration preferences
- Create & Update. Add and update records.
- Create only. Add records.
- Update only. Update records.
Editing the integration details
When you edit the Integration details section, you can select the name or names of integration contacts. Integration contacts will receive an in-app notification and an email, when the integration fails, when the integration fails to complete within 24 hours, or when the scheduled integration fails to run.
- Click Edit
.
- Make your changes.
Editing the credential details
If you selected Cloud as the installation type, choose one of the following options:
- Select the credentials that were created for the integration.
- Edit the credentials that were created for the integration.
- Create new credentials
Scheduling the integration
By default, data is synced once every day. Change the interval or the time so that the data is streamed when your system isn't busy.
- Click Edit
.
- Make and save your changes.
Mapping fields to Oomnitza
To map the fields to Oomnitza, click Edit .
Select Edit integration to add rules for syncing data.
Filtering integration results.
You can add new fields to your integration by selecting Add new field on the mapping page.
Creating custom API fields.
Creating custom mappings
Map the Zendesk fields to Oomnitza fields and create custom mappings to get the user information that you need.
- Click Smart Mapping to automatically detect appropriate mapping fields. Values from the integration can also be dragged to the appropriate field on the Oomnitza side, or selected from the integration field dropdown.
- You have the option to create custom mappings to map any other field that you want to add to Oomnitza. To create an optional custom mapping, do the following:
- Click the down arrow on the field that you want to map.
- Select Add new Oomnitza users field.
- Change the name of the field.
- Click CREATE.
- Ensure that the Email is mapped to the
- Username field on the Oomnitza side (required for integration).
- Email field on the Oomnitza side (required for integration).
- Select the Role field on the Oomnitza mapping side.
- Choose a suitable role from the list (a defined role is necessary for the integration)
- Assign a sync key to a unique field, such as the Email.
- Click UPDATE.
Mappable fields
The following Zendesk fields can be mapped to Oomnitza:
Active
Alias
Chat Only
Created At
Default Group ID
Details
Email
External ID
IANA Time Zone
ID
Last Login At
Locale
Moderator
Name
notes
Only Private Comments
Organization ID
Phone
Report CSV
Restricted Agent
Role
Role Type
Shared
Shared Agent
Shared Phone Number
Suspended
Ticket Restriction
Time Zone
Two-Factor Auth Enabled
Updated At
Launching the integration
Your integration is in Draft mode until the required mandatory fields are added. When added, click Launch to activate your integration.
If you selected Cloud as the installation type when creating the integration, see Running an extended integration
If you selected Local as the installation type when creating the integration, see Running an extended integration locally.
Viewing data ingested by Oomnitza
Viewing ingested asset data
For asset integrations, click Hardware. If the asset integration also ingests software data, click Software.
Viewing ingested user data
For user integrations, click People. If you chose the option to ingest User and SaaS user data, click Software > SaaS, click the SaaS app, and then click the Users tab.
Related Links
Creating workflows
To reduce your workload and automate complex and repetitive tasks, you can create use API blocks to create user workflows.
The following Zendesk presets are available for completing actions:
- Zendesk Add Comment and Status to Ticket Preset
- Zendesk Add Comment to Ticket Preset
- Zendesk Create Ticket Preset
- Zendesk Create User Preset
- Zendesk Delete User Preset
- Zendesk Get User Organization Preset
- Zendesk Suspend User Preset
- Zendesk Update Ticket Preset
Creating API block workflows
- From the menu, select Configuration.
- Click Workflows.
- Click Add
.
- Type users in the search field and select Users from the list.
- Select the Blocks tab
, and drop the API block in the Integrations section onto the canvas.
- On the API block, Click Edit
.
- Type Zendesk in the Search presets field.
- Select the preset you want to use.
Zendesk Add Comment and Status to Ticket preset
Add a comment and change the status of a Zendesk ticket.
- Select your OAuth 2.0 Zendesk credentials.
- Add the description or comment that you want to add to the ticket.
- Specify the status of the ticket.
- Add your Zendesk subdomain. It is automatically populated if you added your subdomain as a global variable.
- Save your changes.
You can click the Advanced Mode button to make additional changes before you save the API block. For example, the ID of the ticket is assumed to be stored in a workflow variable called ticket id (Data type= Short text). If you want to use a different value, go to Advanced Mode > Information and replace the variable {{WFVariables.ticket_id}} in the URL field with the ticket ID you want to use. See Creating a Workflow variable.
Zendesk Add Comment to Ticket preset
Add a comment to a Zendesk ticket that was created.
- Select your OAuth 2.0 Zendesk credentials.
- Add the description or comment that you want to add to the ticket.
- Add your Zendesk subdomain. It is automatically populated if you added your subdomain as a global variable.
- Save your changes.
You can click the Advanced Mode button to make additional changes before you save the API block. For example, the ID of the ticket is assumed to be stored in a workflow variable called ticket id (Data type= Short text). If you want to use a different value, go to Advanced Mode > Information and replace the variable {{WFVariables.ticket_id}} in the URL field with the ticket ID you want to use. See Creating a Workflow variable.
Zendesk Create Ticket preset
Create a Zendesk ticket.
- Select your OAuth 2.0 Zendesk credentials.
- Enter the subject of the ticket.
- Add the description or comment that you want to add to the ticket.
- Enter the ticket priority such as urgent, high, normal, or low.
- Add your Zendesk subdomain. It is automatically populated if you added your subdomain as a global variable.
- Save your changes.
You can click the Advanced Mode button to make additional changes before you save the API block. For example, you can select the Body tab and verify the in the Body field, the fields that you want to send to Zendesk when a ticket is created.
Zendesk Create User preset
Create a new user in Zendesk.
- Select your OAuth 2.0 Zendesk credentials.
- Add your Zendesk subdomain. It is automatically populated if you added your subdomain as a global variable.
- Save your changes.
You can click the Advanced Mode button to make additional changes before you save the API block. For example, you can select the Body tab and verify the fields, in the Body field, that you want to send to Zendesk when a user is created.
Zendesk Delete User preset
Delete or deactivate a Zendesk user.
- Select your OAuth 2.0 Zendesk credentials.
- Add your Zendesk subdomain. It is automatically populated if you added your subdomain as a global variable.
- Click Advanced Mode. On the INFORMATION tab, update the URL field with the {{user_external_id}} of the user that is to be deleted.
- Save your changes.
Two SaaS user records were added to Oomnitza. Subsequently, the two user records are merged into one user record in Zendesk. After the records were merged, the workflow is run to deactivate the user record.
Neither of the two SaaS user records can be deactivated.
Zendesk Get User Organization preset
Use the organization ID to retrieve a user.
- Select your OAuth 2.0 Zendesk credentials.
- Enter the organization ID assigned to the user.
- Add your Zendesk subdomain. It is automatically populated if you added your subdomain as a global variable.
- Save your changes.
See Zendesk - Users.
Zendesk Suspend User preset
Suspend a user in Zendesk.
- Select your OAuth 2.0 Zendesk credentials.
- Enter the organization ID assigned to the user.
- Add your Zendesk subdomain. It is automatically populated if you added your subdomain as a global variable.
- Click Advanced Mode.
- On the INFORMATION tab, update the URL with the ID of the user,
{{user_id}}, you want to suspend. - Save your changes.
See Zendesk - Suspending a User.
Zendesk Update Ticket preset
Update a Zendesk ticket.
- Select your OAuth 2.0 Zendesk credentials.
- Enter the subject of the ticket.
- Add the description or comment that you want to add to the ticket.
- Enter the status of the ticket.
- Enter the type of ticket.
- Enter the ticket priority such as urgent, high, normal, or low.
- Enter an additional tag.
- Add your Zendesk subdomain. It is automatically populated if you added your subdomain as a global variable.
- Save your changes.
You can click the Advanced Mode button to make additional changes before you save the API block. For example, the ID of the ticket is assumed to be stored in a workflow variable called ticket id (Data type= Short text). If you want to use a different value, go to Advanced Mode > Information and replace the variable {{WFVariables.ticket_id}} in the URL field with the ticket ID you want to use. See Creating a Workflow variable.
Reference articles for workflows
- Creating workflows: introduction
- Mapping positive and negative responses
- Troubleshooting workflows
- Using the API block
Creating SaaS user workflows
To add the preset, see Creating API block workflows. When you add the workflow, type SaaS in the search field and select Software SaaS users.
See Creating SaaS user workflows.
Zendesk User Role (OAuth2) preset
Read a user’s role and last login date in Zendesk.
See Creating SaaS user workflows.
Reference articles for creating workflows
Comments
0 comments
Please sign in to leave a comment.