Overview
Hyperscience provides the ability to integrate with external systems through various APIs and blocks in your flows. These include:
Type | Description |
API Endpoints | Hyperscience provides an API for maximum flexibility with integrations. For more information, see our API documentation. |
Input Blocks | Input Blocks allow you to integrate your organization’s data sources into our system. Through these blocks, you can process documents from a variety of sources, such as inboxes, message queues, or folders on the network. More information about these blocks can be found in the Input Blocks section of this site. |
Output Blocks | With Output Blocks, you can send data extracted by Hyperscience to other systems for downstream processing. More details about these blocks can be found in the Output Blocks section of this site. |
API Blocks | API Blocks allow you to connect to other data sources in your organization in order to augment or verify extracted data. To learn more, see API Blocks. |
Database Blocks | Database Blocks allow you to make queries from Hyperscience to databases, which increases the overall speed of your flows by minimizing the need for manual transcription. For more information, see Database Blocks. |
Integrations in SaaS
There are some key differences between on-premise and SaaS integrations. The following integrations are not currently supported in SaaS:
Universal Folder Listener
Bizagi
In many cases, systems like Message Queues and databases are not exposed to the internet. Provided they are available for Hyperscience to access, the customer should open a firewall pinhole if the service is not public. We may provide a range of IP addresses used by our cloud infrastructure, so the firewall access may be more restrictive.