---
title: "July 2025"
slug: "july-2025"
updated: 2026-01-05T21:24:14Z
published: 2026-01-05T21:30:00Z
canonical: "docs.hunters.ai/july-2025"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hunters.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# July 2025

## Product updates - July 2025

## **Workflows**

### **Response Actions - Open Beta**

In the following days, we will **roll out Response Actions to all customers, allowing them to take response actions directly from a lead.**

Key capabilities:

- Out-of-the-box templates - predefined actions for containment, management, and communication
- Custom Response Actions - tailor response workflows to fit your needs
- Categorization - organize your actions into relevant categories
- Contextual Action Listing - dynamically surfaces relevant actions for each lead
- Audit Trail - log all actions directly in the lead collaboration section
- Powerful Automation - use any lead attribute to trigger flexible response workflows

Known limitation - we do not support folder hierarchy yet. Make sure all recipes are under one of the approved folders. Read more [https://docs.hunters.ai/docs/create-response-action](https://docs.hunters.ai/docs/create-response-action)

![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXd51slVHW-St2NecU0lQDeXdQFkEXy8GjqIbEy_HLr1gfkDKs3DWTaTd6EEQS5t_E9CFeXgQ9b7kitAtjLHUujOhNMEf1n2oEjq0qJrjkR8XVASpDNx9sFrzBDeVXvENtxj_Z4O8w?key=RwYuHc4trhTsWy5cLuoozA)

### **Optimization and template alignment**

In the upcoming days, we will start a new periodical optimization work on the customer’s Workflows environment, **deleting old unused recipe templates deployed by Hunters and disconnecting unused active connectors for the last 90 days.**

In addition to the above, we will also **deploy new Automation Workflows and Response Actions templates** to your environment in dedicated folders (Automation template, Hunters_Actions). **All templates will have a [Template] prefix in their names**. Please remove this prefix and/or move them to a different folder before activating them. We will use those folders to deploy new templates moving forward.

## **Search**

### **Export CSV**

We’ve introduced a new **Export CSV capability across all our search experiences,** making it easier to analyze, share, and act on search results outside the platform.

With a single click, users can now export search results into a CSV file for offline analysis or reporting. This allows more flexible use of search outputs in spreadsheets or other data tools.

## **Data Source Health Notification**

### **Planned changes to communication on health issues for customers**

In the near future, Hunters will phase out and will not notify customers using support tickets for some of the ingestion issues that are covered with the new Data Source Health Notification email feature released during Q2. Customers are encouraged to register for this new feature to stay informed on data ingestion issues.

Enablement docs [https://docs.hunters.ai/v1/docs/set-up-data-health-notifications](https://docs.hunters.ai/v1/docs/set-up-data-health-notifications)

## **Security content**

### **New detectors**

**Slack Workspace Export**

Detection of manual Slack workspace exports initiated via the admin console. These exports may indicate malicious attempts to exfiltrate sensitive data such as credentials, access tokens, or confidential communications.

### **Integrations**

**New CrowdStrike Alerts api endpoint**

Crowdstrike has announced that the **“Detects” API endpoint will be deprecated in September**.

The new endpoint that Crowdstrike exposes is “Alerts”. Hunters have created an integration with the new endpoint and have also added support to all relevant out-of-the-box content.

If you would like to continue streaming the information after September, please make sure to follow the Hunters documentation here:

[https://docs.hunters.ai/docs/crowdstrike?highlight=Crowdstrike%20alerts](https://docs.hunters.ai/docs/crowdstrike?highlight=Crowdstrike%20alerts)

Please advise that since the data being sent on the new endpointdoess not fullymatchg, the leads and alerts might also be different. In addition, if you have any custom configuration like custom scoring rules over the “Detects” data, we advise you to recreate and validate it using the “Alerts” data.