Configure external applications for forwarding

Configure Cortex AgentiX external applications and Cortex Gateway egress for forwarding cases, issues, and logs to third-party services.

Cases, issues, and logs can be forwarded to third-party external services. The external service must be configured in Cortex AgentiX before you set up notification forwarding.

Only cases and issues can be forwarded to Slack, Amazon S3, Amazon SQS, Splunk, and Webhook. Before forwarding cases or issues to Splunk, Amazon S3, Amazon SQS, or Webhook, you need to configure egress in the Cortex Gateway.

You do not need to configure egress for email, Slack, or syslog forwarding. No prior configuration is required to send data or logs to an email distribution list.

You can configure external applications using either of these methods:

• Pre-configuration: Navigate to Settings → Configurations → Integrations → External Applications and follow the setup guide for your specific service:

  • Forward notifications to Amazon SQS

  • Forward notifications to Amazon S3

  • Forward notifications to Splunk

  • Forward notifications to webhook

  • Integrate a syslog receiver

  • Integrate Slack for outbound notifications

• In-workflow configuration: Navigate to Settings → Configurations → General → Notifications → Add Forwarding Notifications. Define the configuration and notification scope, then click Add Application and complete the setup steps for your chosen service.