Content Update Manager
This playbook checks for any available content updates for selected installed content packs and notifies users via e-mail or Slack. It also contains an auto-update flow that lets users decide via playbook inputs or communication tasks if they want to trigger an auto-update process to install all updates that were found. This playbook can be used as a Cortex XSOAR job to help users track marketplace pack updates and install them regularly.
XSOAR Content Update Notifications · 46 tasks · 7 inputs · 0 outputs
Inputs
notificationemail— Provides semi-colon delimited e-mail addresses for the new content notifications. Note: You must have an installed and configured integration that supports the send-mail command.slackuser— Provides a Slack username for the new content notifications. Note: You must have an installed and configured Slack integration.slackchannel— Provides a Slack channel for the new content notifications. Note: You must have an installed and configured Slack integration. Also, make sure the Cortex XSOAR application has access to this channel.slackchannelid— Provides a Slack channel ID for the new content notifications. Note: You must have an installed and configured Slack integration.packs— A CSV of packs to monitor.auto_update— Establishes whether to automatically update the content packs if there are available updates or wait for an analyst's approval or the manual update process. Specify 'Yes' for auto-update or 'No' for manual update.demisto_rest_api_name— Defines which instance of a configured Demisto API to use for checking updates against.
Commands used
closeInvestigation
core-api-get
send-mail
send-notification
setIncident