Requesting connectors

You want a single pane of glass to manage your enterprise.

You want to manage all your endpoints, mobile phones, computers, and network endpoints, and SaaS applications and desktop software, and users, and contracts, and security systems, and client management systems.

All in one place. 

Before you raise requests for custom integrations

Review the following information:

• Check out the extensive list of available extended integrations. With the integrations that are provided, you can ingest endpoint, user, and SaaS information and accelerate time to value by using the presets that Oomnitza provides to interwork with external vendor applications. 
• Create your own universal connector. You can leverage Oomnitza’s integration builder to connect to the REST API that your organization wants to use to ingest and manage data in Oomnitza.

Oomnitza extended integrations

Oomnitza universal connectors

Checklist

If you want to request additional extended integrations, send a request to Oomnitza Support. In the request ensure that the following information is provided:

General information

1. The name of the system and the vendor of the system.
2. Use cases. Describe the use cases in detail and the interactions between users and the system such as:
   1. User integration. "I need a list of SaaS users and their last login activity to track license usage in Oomnitza."
   2. Ticketing integration. "I want to automate the creation of tickets in Oomnitza."
3. The objects that you want to integrate with. For example,  assets, users, or SaaS users, or both users and SaaS users.
4. The type of system such as on-premises or SaaS.  
5. Deadline for creating the integration. Provide the due date or explain the urgency of the request.

Technical information

To expedite the integration process, provide as much and as detailed information possible about the REST API that you want to integrate with. 

Accelerate development
The more information we have about the REST API that you want to integrate with, the quicker we can build the integration. 

1. REST API availability. Confirm whether the system has a REST API to read the required objects, such as assets, users, or SaaS users?
2. Documentation. Provide a link to the REST API documentation.
3. Authentication method. Describe the authentication method that us used by the REST API such as basic authorization, token-based authorization, OAuth 2.0.
4. Test System availability. Confirm whether a test system is available for integration testing.
5. Provide the URL.
6. Provide a sample user account. The sample user must have permission to read the necessary information and generate API credentials and access the REST API.
7. Main Contact. Who do you wish to nominate as the main contact in your organization who will collaborate with our team to create the custom integration.

Request a custom extended integration
Contact Support.  

Next steps

When you submit the required information,  we will contact you to discuss the next steps. We'll also inform you when the custom extended integration will be available.

Note
Because of technical requirements, we might not be able to fulfil all of the requests for custom extended integrations.
If the requested extended integration requires an additional authentication mechanism or has other technical requirements that are not currently supported, the delivery of the custom extended integration might take longer.