Output Blocks
- 6 Articles
Routing of Extracted Data
- Published on Sep 24, 2024
By default, if you have multiple notification connections enabled in the system, every submission's extracted data is output through each enabled notification connection. In other words, if Hyperscience is connected to multiple downstream systems, e...
Salesforce Notifier
- Published on Sep 24, 2024
Overview With the Salesforce Notifier Block, you can configure your flow to send extracted information to Salesforce. The Salesforce Notifier Block can use extracted information to look up, and then update any number of fields on a Salesforce...
Box Notifier
- Published on Sep 24, 2024
Overview Note that the Box Notifier Output Block must be used in conjunction with the Box Listener Input Block. To learn more about this Input Block, see Box Listener . With our Box Notifier Output Block connections, you can integrat...
HTTP Notifier
- Published on Sep 24, 2024
Overview The HTTP Notifier (REST) output connection will POST results from the system to a specified HTTP endpoint. If you would like to use the HTTP Notifier connection in a SaaS instance and your service is not public, you should create a f...
Message Queue Notifier
- Published on Sep 24, 2024
Overview With the Message Queue Notifier Output Block, you can configure connections to the following message queue types: ActiveMQ Amazon SQS IBM MQ RabbitMQ To select the message queue type you want to use for a Messag...
UiPath Notifier
- Published on Sep 24, 2024
Overview You can use the Hyperscience UiPath output connector to integrate directly with a UiPath Orchestrator Queue. Using the connector, all document-processing notifications, including extracted data, are queued directly in UiPath for further...