Hyperproof includes several different ways to pull information from other systems or to exchange data with them. All of these methods could be interpreted as integrations, though formally, only some types are referred to as integrations in our product nomenclature.
Task Management
Hyperproof has integrations with task management systems. At the time of this writing, Hyperproof includes support for Jira, Asana, and ServiceNow. To connect a task to Jira, Asana, or ServiceNow, you would go to a task in Hyperproof. These integrations can be enabled in Settings/Integrations.
Messaging Integrations
There are integrations with Slack and Microsoft Teams to deliver Hyperproof notifications. These integrations can be enabled in Settings/Notifications.
β
Cloud Storage Integrations
There are integrations with cloud storage systems like Google Drive, Dropbox, etc. Confluence is not exactly a file storage system, but it is configured the same way. Those integrations are not set up from Settings but from the "proof picker" window. When you upload proof, you have the option to configure integrations with several file storage systems.
Hypersyncs
Another type of information exchange is a Hypersync. This could be interpreted as another type of integration, though it is not referred to as an integration in the documentation or product nomenclature. Hypersyncs allow you to connect to service apps, also known as cloud apps, and pull data from them, similar to running a report in that system and storing the results as evidence, what we call proof, in Hyperproof.
All generally available Hypersyncs are enabled by default in all Hyperproof organizations. They can be configured from the Automations tab on a Control or Label, and you will need credentials for the third-party systems that have privileges to access the data in them.
This article in the help system is a good starting point to learn more about Hypersyncs.
Many third-party systems are compatible with Hypersyncs and the list continues to grow. This help article has the details about each Hypersync and what data it can pull.
If there is a system that has a REST API that we do not have a Hypersync for, the Hypersync SDK enables people with programming skills to create their own Hypersyncs using our framework.
β
β
β
REF 000001331



