Accessing Sample Output Data for Integration Commands

LAST UPDATED: DEC 11, 2024

Overview

This article provides guidance on accessing sample output data for integration commands in vSOC. This information is useful for understanding the format of an integration command’s output data, troubleshooting issues, and performing other related tasks.

Steps to Access Sample Data

Navigate to Configuration > Integrations and search for the integration for which to view its sample output data.
Select a command.
Click on the Outputs tab to see all available sample output data.

READER NOTE

Not all integration command outputs include Key Fields and Context Data.
- Common cybersecurity indicators, including unique IDs, file hash values, CVE numbers, and IP addresses, are extracted from Raw Data as Key Fields and stored in the path $.[playbookTask].outputData.
  - These key-value pairs can be used as data points for playbook task inputs.
- Context Data may be identical to Raw Data in some cases
All sample output data will, at a minimum, include Return Data and Raw Data.
The exception is Test Connection, which only includes Return Data.

Additional Notes

For an overview of integrations and their configuration within the D3 platform, refer to Integrations.
For detailed documentation on individual integrations, refer to Integration Docs.