Output Blocks
Documentation Index
Fetch the complete documentation index at: https://help.hyperscience.ai/llms.txt
Use this file to discover all available pages before exploring further.
Output Blocks
- 8 Articles
S3 Notifier
- Updated on Sep 23, 2025
- Published on Mar 18, 2025
The S3 Notifier output connection will send submission data and state-change notifications to the Amazon S3 URI you specify. If you would like to use the S3 Notifier connection in a SaaS instance and your service is not public, you should create a ...
Kafka Notifier
- Updated on May 14, 2025
- Published on Mar 18, 2025
Accessing this feature Your access to the feature described in this article depends on your license package and pricing plan. To learn which features are available to your organization and how to add more, contact your Hyperscience representat...
Salesforce Notifier
- Updated on Nov 6, 2025
- Published on Mar 18, 2025
Box Notifier
- Updated on May 14, 2025
- Published on Mar 18, 2025
HTTP Notifier
- Updated on May 14, 2025
- Published on Mar 18, 2025
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 firewall pinh...
Message Queue Notifier
- Updated on Jul 18, 2025
- Published on Mar 18, 2025
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 Message Queue Noti...
UiPath Notifier
- Updated on Jul 17, 2025
- Published on Mar 18, 2025
Routing of Extracted Data
- Updated on Jul 17, 2025
- Published on Mar 18, 2025
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...