---
title: "Hooks: webhooks and automations from your analytics"
description: "A hook is one trigger and the actions that follow it. Data arrives, a cohort changes, an alert fires or the clock strikes, and Countly calls your webhook…"
url: https://countly.com/feature/hooks
last_modified: 2026-11-11
---

Hooks

# When something happens in Countly, tell the rest of your stack

A hook is one trigger and the actions that follow it. Data arrives, a cohort changes, an alert fires or the clock strikes, and Countly calls your webhook, emails a team or runs your own code. No middleware to host, no polling.

In this demo deployment, each hook reads as a sentence: when this happens in this project, do that.

Part of engagement

## The automations teams set up first

Each is one trigger and one or two actions, built in a form, with no code unless you want it.

- “When someone signs up, add them to the CRM.” A tracked event triggers an HTTP request with the whole payload as JSON.
- “When a crash appears for the first time, post it to Slack.” The new crash activity triggers a request to a Slack webhook.
- “When a customer slips into the at-risk cohort, email their account manager.” Entering a cohort triggers an email, to anyone, with or without a Countly account.
- “When an alert fires, open a ticket.” An alert triggers a request to your ticketing tool’s API.
- “When a variable changes, tell the release channel.” Changes to Adaptive Variables are activities a hook can follow.
- “Let our backend start it.” A hook gets its own URL. Call it, and its parameters become the payload.
Triggers and actions

## One trigger, as many actions as you need

The actions run in order, and one failing does not stop the next.

### Tracked data

The moment matching data arrives from your apps.

Any event Sessions Conditions on properties

### Internal activity

Something Countly itself did.

Cohort entry and exit Profile group entry and exit Profile changes New crash Alert fired Variable changes Another hook ran

### Schedule and API

On the clock, or when something calls it.

Daily, weekly, monthly In your time zone Its own URL

### Actions

What happens next.

HTTP request Email Custom JavaScript

Built in a form

## Set up in a minute, tested before it runs

Pick the trigger, add the actions, run it once for real, then turn it on.

- Forward an event Pick the event, point a request at the destination, and send the whole payload with one token.
- Tell a team When a profile enters a cohort, email the people who should know.
- Send only what they need Put a few lines of JavaScript before the request, so the payload arrives in the shape the receiver wants.
- Try it for real Run the whole chain once and read each action’s result, without touching the hook’s history.
Safe by design

## Automation that cannot be turned against you

A hook sends your data out, so the limits are part of the design.

- 01 No reaching inside your network Destination addresses are checked against internal and private ranges when a hook is saved and every time it runs. HTTP
- 02 A sandbox for your code Custom JavaScript runs isolated, for up to three seconds and 128 MB, with no network, files or access to the rest of Countly. Code
- 03 Requests that cannot hang A destination that does not answer within fifteen seconds is recorded as a failure. HTTP
- 04 Failures where you can see them Each hook keeps its ten most recent failures with their errors. Monitoring
- 05 A rate limit if you want one Cap how often hooks run in a time window. Runs beyond it are dropped and recorded. Server
Works with

## Hooks, with the rest of Countly

Every feature reads the same live data, so an answer in Hooks doesn’t stop there. These are the handoffs built in.

[All features](https://countly.com/platform/features)

Alerts

An alert can hand its trigger to a hook, which posts it wherever your team works.

Open

[(Alerts An alert can hand its trigger to a hook, which posts it wherever your te](https://countly.com/feature/alerts)

Cohorts

Run a hook when someone enters or leaves a cohort.

Open

[(Cohorts Run a hook when someone enters or leaves a cohort. Open)(https://countl](https://countly.com/feature/cohorts)

Crashes & Errors

Run a hook on a crash the project has never reported before.

Open

[(Crashes & Errors Run a hook on a crash the project has never reported before. O](https://countly.com/feature/crashes-errors)

Adaptive Variables

Run a hook when a variable or condition is added, changed or removed.

Open

[(Adaptive Variables Run a hook when a variable or condition is added, changed or](https://countly.com/feature/adaptive-variables)

Profiles

Run a hook when a profile is created, updated or deleted, or joins a profile group.

Open

[(Profiles Run a hook when a profile is created, updated or deleted, or joins a p](https://countly.com/feature/profiles)

Data ownership

## Your data goes only where you send it

Hooks run on your Countly server. Nothing is forwarded until you point a hook at a destination.

[Data privacy](https://countly.com/platform/data-privacy)

### No middleware

No integration service to host or trust in between. The server that holds your data makes the call.

### Send only what is needed

Reshape the payload before it leaves, so the receiving system gets three fields, not thirty.

### Self-hosted, or dedicated

Run Countly in your own cloud, your data center or an air-gapped network. Or let us run a single-tenant instance in the Google Cloud region you choose.

ISO 27001 Certified

ISO 27017 Certified

ISO 27018 Certified

SOC 2 Type II examined

TISAX® Participant*

*Countly Ltd. is a TISAX® Participant. TISAX® is a registered trademark of and governed by ENX Association. Learn more at [enx.com/tisax](https://enx.com/tisax)
