Overview

  • Updated on Dec 30, 2024
  • Published on Sep 24, 2024
Overview Hyperscience provides the ability to integrate with external systems through various APIs and blocks in your flows. These include: Integrations in SaaS There are some key differences between on-premise and SaaS integrations....
  • Updated on Dec 30, 2024
  • Published on Sep 24, 2024
Overview Each connection in an Input or Output Block has two types of settings: Connection-specific settings, which vary by connection and are described in Input Blocks and Output Blocks , and  Universal settings: Bloc...
  • Published on Sep 24, 2024
Overview Hyperscience provides Input and Output Blocks for plug-and-play integrations with our system. After an Input or an Output Block has been uploaded to Hyperscience, you will need to add individual connections to specific resources on your...
  • Published on Dec 14, 2024
The system conducts periodic health checks on the components of the instance, including various aspects of any input or output connections configured in deployed flows. By default, these health checks are performed every 30 seconds, but you can ch...
  • Published on Sep 24, 2024
The Connections Log provides information about connection events, including starting and stopping processes and errors related to the connector's operation. These connections are configured in the settings for your Input Blocks and Output Blocks. ...
  • Published on Sep 24, 2024
With our Box Folder Listener and Box Notifier Output Block connections, you can integrate Box as both an input source and downstream destination for your Hyperscience data. If you use metadata templates in Box, you map document fields to fields in ...