> For the complete documentation index, see [llms.txt](https://docs.pushpulse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pushpulse.com/integrations/intellisee-integration.md).

# IntelliSee Integration

Connect IntelliSee AI video analytics to PushPulse so camera detections like weapons, fire, or a person down automatically send an alert with the snapshot and video attached.

### What You Get

**Automatic alerts from your cameras.** When IntelliSee detects something on one of your cameras, it sends the event to PushPulse. PushPulse matches it against the rules you set up and sends the right alert template to the right location. No one has to be watching a monitor for the alert to go out.

**The capture comes with the alert.** The detection snapshot (and a short video clip, when the appliance recorded one) is attached to the alert, so recipients can see what happened before they respond.

**Detection details in the message.** Alert templates can include IntelliSee details such as the detection type, camera name, and time of detection, filled in automatically when the alert is sent.

{% hint style="info" %}
The IntelliSee integration is available on the **Unified Plan**. Recipients need the latest version of the PushPulse mobile app to see attached images and video. You'll also need an active IntelliSee subscription and admin access to your IntelliSee account.
{% endhint %}

<div><figure><img src="https://1237304485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYEKqXMDhT5qkEe8tbUev%2Fuploads%2FxDtDrL0XRs79nvgFMtHp%2FScreenshot%202026-10-12%20at%202.09.35%E2%80%AFPM.png?alt=media&#x26;token=a7b4eba8-0891-4157-b484-0f8b8dda4560" alt=""><figcaption></figcaption></figure> <figure><img src="https://1237304485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYEKqXMDhT5qkEe8tbUev%2Fuploads%2FLLyikkO8hTbc3k5EXmML%2Fintellisee-1.png?alt=media&#x26;token=9703e7ed-ac62-4ca1-a413-5a7a508d5c25" alt=""><figcaption></figcaption></figure></div>

***

### How It Works

1. **IntelliSee** watches your cameras and detects an event (for example, Weapon or Person on Ground).
2. IntelliSee sends that detection to a private **webhook URL** that PushPulse gives you. Every event is signed with a **signing secret**, so PushPulse only accepts events that really came from your IntelliSee account.
3. **PushPulse** checks your **rules**. Each rule says: at this location, when IntelliSee detects these types, send this alert template.
4. The matching alert goes out to that template's recipients at that location, with the camera capture attached.

You set things up in both products. The steps alternate between them, so it helps to have PushPulse and IntelliSee open side by side.

***

### Setup Overview

1. **Create a connection in PushPulse** - name it and copy its webhook URL
2. **Add PushPulse in IntelliSee** - paste the webhook URL, choose what to send, and copy the signing secret
3. **Paste the signing secret in PushPulse**
4. **Send a test from IntelliSee** - PushPulse confirms the connection
5. **Create rules in PushPulse** - map detection types to alert templates for each location
6. **(Optional) Add IntelliSee details to your alert templates**

Before you start, make sure the alert templates you want to use (for example "Weapon Detected" or "Emergency Alert") exist and are enabled in PushPulse.

***

### Step 1: Create a Connection in PushPulse

In the PushPulse web app, go to **Manage → Integrations** and find **IntelliSee** in the **Marketplace** tab. Click it to open the **Connect IntelliSee** drawer. (If you already have a connection, open the IntelliSee page and click **Add connection**.)

Enter a **Connection name**, such as "Main Campus", and click **Continue**.

PushPulse creates the connection and shows its **Webhook URL**. Click the copy icon next to the URL. Keep this drawer open: you'll come back to it in Step 3.

<figure><img src="https://1237304485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYEKqXMDhT5qkEe8tbUev%2Fuploads%2F0OaW4we51nF0Za40x2JC%2F02-webhook-step.png?alt=media&#x26;token=24647a84-73ac-47f4-adf0-89191a423bd1" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Most organizations need one connection. You can create more, for example one per campus or one per IntelliSee account, and each gets its own webhook URL and signing secret.
{% endhint %}

***

### Step 2: Add PushPulse in IntelliSee

In a new browser tab, sign in to IntelliSee as an administrator.

1. Go to **Account Settings → Advanced Settings**, open **Integrations**, and choose the **PushPulse** partner.
2. Paste the webhook URL into **PushPulse endpoint URL**.
3. Under **What to send**, **Detection types** is set to all by default. Leave it as is, or choose only the detection types this channel should send. Detection types you leave out here never reach PushPulse.
4. Select **Include the detection snapshot and video clip** so the capture is attached to your PushPulse alerts. It's off by default. If you leave it unchecked, alerts are still sent, just without the image or video.
5. Click **Save**. IntelliSee shows a **signing secret** with the message *"Copy it now; it won't be shown again."* Copy it.

<figure><img src="https://1237304485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYEKqXMDhT5qkEe8tbUev%2Fuploads%2Fe9YlaZHAvna9VOeJmx9C%2FScreenshot%202026-10-12%20at%202.13.20%E2%80%AFPM.png?alt=media&#x26;token=9d0825de-c992-461d-8e29-b52ed14da497" alt=""><figcaption></figcaption></figure>

***

### Step 3: Paste the Signing Secret in PushPulse

Back in the PushPulse drawer, click **Continue** to reach the **Secret** step. Paste the signing secret into **Signing secret** and click **Save and wait for test**.

PushPulse uses this secret to verify every event IntelliSee sends. It's stored securely and never shown again.

<figure><img src="https://1237304485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYEKqXMDhT5qkEe8tbUev%2Fuploads%2FkT18ECwbn46PEt0Tn88K%2F05-secret-step.png?alt=media&#x26;token=21150bf2-840c-466c-85b6-1c31bdc0c37d" alt=""><figcaption></figcaption></figure>

***

### Step 4: Send a Test from IntelliSee

PushPulse now shows **Waiting for IntelliSee to send a test**.

In IntelliSee, click **Send test to channel** on the PushPulse channel. Within a few seconds the PushPulse drawer updates to **Connected**, and in IntelliSee the channel shows **Enabled** with the time it was confirmed. IntelliSee only turns the channel on once PushPulse accepts this test, so don't skip it. Make sure **Send automatically** is switched on in IntelliSee.

If you need to step away, click **Close, I'll finish later**. The connection stays in **Waiting for test** until IntelliSee's test arrives, and you can reopen the instructions with **Show setup steps** on the connection card.

<figure><img src="https://1237304485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYEKqXMDhT5qkEe8tbUev%2Fuploads%2FQrA8R2GyjZSjUxCyFpVZ%2FScreenshot%202026-10-12%20at%202.15.34%E2%80%AFPM.png?alt=media&#x26;token=66036480-f88a-4999-9e22-be3b13d4eb5e" alt=""><figcaption></figcaption></figure>

If PushPulse shows **Signature didn't match**, the secret in PushPulse doesn't match the one in IntelliSee. Click **Update secret**, paste the secret again (or click **New signing secret** in IntelliSee and paste the new one), and send another test.

***

### Step 5: Create Rules

Rules decide which detections send an alert, where, and which alert. Without at least one rule, PushPulse receives IntelliSee events but doesn't send anything.

From the **Connected** screen click **Add your first rule**, or click **Add rule** on the connection card. Fill in:

* **Where** - the PushPulse location the alert is sent to.
* **When** - one or more **detection types**: Weapon, Smoke & Fire, Slip Risk, Person on Ground, Trespassing, Loitering, Vehicle, Crowd, Cellphone, No Show.
* **Then** - the alert template to send. Only enabled templates are listed. The alert goes to that template's recipients at the selected location.

Click **Save rule**.

<figure><img src="https://1237304485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYEKqXMDhT5qkEe8tbUev%2Fuploads%2FosRx9vD9uEnnX5UjdQHr%2FScreenshot%202026-10-12%20at%202.17.22%E2%80%AFPM.png?alt=media&#x26;token=0ca36c78-a64d-40fa-b697-377c0f193626" alt=""><figcaption></figcaption></figure>

A few things to know:

* **Every matching rule fires.** If two rules on the same connection both include Weapon, a weapon detection sends both alerts. That's useful for a dedicated "Weapon Detected" alert alongside a general one, but check for overlap if you see duplicate alerts.
* **Rules are grouped by location** on the connection card. Use the pencil and trash icons to edit or delete a rule.
* **Rules match on detection type only.** PushPulse doesn't filter by camera or appliance. To limit which detections reach PushPulse, choose the detection types on the channel in IntelliSee (Step 2).
* If a location is deleted in PushPulse, its rules are marked **location removed** and stop firing. Delete them or recreate them for a current location.

<figure><img src="https://1237304485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYEKqXMDhT5qkEe8tbUev%2Fuploads%2FoiS1gTVpnh6stSghtN4q%2FScreenshot%202026-10-12%20at%202.17.47%E2%80%AFPM.png?alt=media&#x26;token=bdf792a9-b208-41df-8f98-5d014b3b579e" alt=""><figcaption></figcaption></figure>

***

### Step 6 (Optional): Add IntelliSee Details to Your Alert Templates

Alert templates can include **tokens** that fill in details from the IntelliSee detection when the alert is sent. In the template's message, click **Insert Token** (or type `/` or `{{`) and choose **IntelliSee**:

| Token                     | What it shows                                                  | Example                    |
| ------------------------- | -------------------------------------------------------------- | -------------------------- |
| Detection type            | What IntelliSee detected                                       | Weapon                     |
| Camera                    | Camera name, as named in IntelliSee                            | Lot B Camera 04            |
| Camera location           | Area the camera covers, as named in IntelliSee                 | North Parking              |
| Appliance                 | IntelliSee appliance the camera is connected to                | Main Campus Appliance      |
| Detected at               | When it was detected, in each recipient's time zone            | Oct 7, 2026 at 3:04 PM CDT |
| IntelliSee dashboard link | Link to the event in IntelliSee (requires an IntelliSee login) | app.intellisee.com/...     |

Tokens appear as green pills in the message. Click a token to set **fallback text**. The fallback is used when the template is sent some other way (for example, manually from the dashboard), so the message still reads well without IntelliSee data.

<div><figure><img src="https://1237304485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYEKqXMDhT5qkEe8tbUev%2Fuploads%2FGr2yHqZ38QuIeWzuQ0qB%2FScreenshot%202026-10-12%20at%202.18.29%E2%80%AFPM.png?alt=media&#x26;token=3a87b806-e9f7-40ea-b8b0-db3602711d7c" alt=""><figcaption></figcaption></figure> <figure><img src="https://1237304485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYEKqXMDhT5qkEe8tbUev%2Fuploads%2FHb74kgnYd8ukNRPmgwlC%2FScreenshot%202026-10-12%20at%202.19.27%E2%80%AFPM.png?alt=media&#x26;token=599c7680-7e51-4cac-889f-08f85f788b99" alt=""><figcaption></figcaption></figure></div>

***

### What Recipients See

The alert arrives like any other PushPulse alert, using the template's sound, delivery channels, and recipients. When IntelliSee shares media, the alert shows the detection snapshot and video clip with an IntelliSee badge. In the web dashboard the alert also shows the camera, detection time, and a **View in IntelliSee** link.

Recipients need the latest version of the PushPulse mobile app to see attached images and video in the app.

<div><figure><img src="https://1237304485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYEKqXMDhT5qkEe8tbUev%2Fuploads%2FY33fOGj6WF5aKc1I6uMg%2Falert-mobile-1.png?alt=media&#x26;token=3ad4074b-e784-4f42-8d9d-7ec0a6855bf4" alt=""><figcaption></figcaption></figure> <figure><img src="https://1237304485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYEKqXMDhT5qkEe8tbUev%2Fuploads%2FWaBhE6GWc538t2ruPSYL%2Falert-mobile-2.png?alt=media&#x26;token=89769b0c-db78-4d82-9650-5c9a632cec36" alt=""><figcaption></figcaption></figure></div>

<figure><img src="https://1237304485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYEKqXMDhT5qkEe8tbUev%2Fuploads%2FF7XBGcRRmhuyPOJYDXJP%2F10-alert-web.png?alt=media&#x26;token=b540f85c-e8c2-486d-b4b8-fa454c556909" alt=""><figcaption></figcaption></figure>

***

### Managing a Connection

Open **Manage → Integrations → IntelliSee** to see all your connections. Each card shows its status and when the last event arrived:

| Status                   | Meaning                                                                       |
| ------------------------ | ----------------------------------------------------------------------------- |
| **Connected**            | Events are arriving and passing verification.                                 |
| **Waiting for test**     | Setup isn't finished. Click Send test to channel in IntelliSee.               |
| **Signature mismatch**   | Events are failing verification. Update the signing secret.                   |
| **No events in 30 days** | Connected, but nothing has arrived recently. Check the channel in IntelliSee. |

From the **⋮** menu on a card you can:

* **Edit connection** - rename it.
* **View webhook URL** - copy the URL again.
* **Update signing secret** - paste a new secret after clicking **New signing secret** in IntelliSee. Events signed with the old secret fail as soon as you save, so update both sides together.
* **Remove connection** - deletes the connection and all its rules. IntelliSee events sent to its URL are rejected. Remove the PushPulse channel in IntelliSee as well.

**Recent events.** Expand **Recent events** on a card to see the last 10 deliveries from IntelliSee: the capture, detection type, camera, time, and what PushPulse did with it.

| Outcome                 | Meaning                                                         |
| ----------------------- | --------------------------------------------------------------- |
| Template name           | A rule matched and that alert was sent.                         |
| **Connection verified** | IntelliSee's test event arrived.                                |
| **No matching rule**    | The event was valid but no rule covers that detection type.     |
| **Signature failed**    | The event didn't pass verification and was rejected.            |
| **Alert not sent**      | A rule matched but the alert couldn't be sent. Contact support. |

<figure><img src="https://1237304485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYEKqXMDhT5qkEe8tbUev%2Fuploads%2FJm64ycTPzUTZcp6ylFmU%2FScreenshot%202026-10-12%20at%202.28.46%E2%80%AFPM.png?alt=media&#x26;token=4bfe0b3f-3a31-4400-b5e3-d71575a2026d" alt=""><figcaption></figcaption></figure>

***

### Troubleshooting

**The connection is stuck on Waiting for test.** Click **Send test to channel** on the PushPulse channel in IntelliSee. Make sure the **PushPulse endpoint URL** in IntelliSee exactly matches the one shown in PushPulse (use **View webhook URL** to copy it again).

**Signature mismatch or Signature failed.** The signing secret in PushPulse doesn't match IntelliSee's. Click **New signing secret** in IntelliSee, paste it with **Update signing secret** in PushPulse, then send a test.

**Events show No matching rule.** Add a rule for that detection type, or add the type to an existing rule. Events received before a rule existed are not resent.

**No events are arriving.** Check in IntelliSee that the PushPulse channel is **Enabled**, **Send automatically** is on, and its **Detection types** include the detections you expect.

**Alerts arrive without the image or video.** Make sure **Include the detection snapshot and video clip** is checked on the PushPulse channel in IntelliSee, and that recipients are on the latest PushPulse mobile app. Video is only included when the appliance recorded a clip.

**The same detection sent two alerts.** More than one rule includes that detection type. Review the rules on the connection card.

**The IntelliSee dashboard link asks me to sign in.** That link opens the event in IntelliSee and needs an IntelliSee login. The snapshot and clip in the PushPulse alert don't.
