/managing-subscriptions

name: managing-subscriptions
description: 'Manage PostHog subscriptions — scheduled email, Slack, or webhook deliveries of insight or dashboard snapshots, optionally with an AI-written summary attached to each delivery. Use when the user wants to subscribe to an insight or dashboard, get an AI summary attached to those deliveries, check existing subscriptions, change delivery frequency, add or remove recipients, or stop receiving updates.'

Managing subscriptions

This skill guides you through managing PostHog subscriptions. Subscriptions deliver scheduled snapshots of insights or dashboards via email, Slack, or webhook.

When to use this skill

Use this skill when the user:

• Wants to "track", "follow", "subscribe to", or "get updates" about an insight or dashboard
• Asks for "daily updates", "weekly reports", or "send me this every morning"
• Wants an **AI-written summary** attached to each delivery of an insight or dashboard (see step 6)
• Asks to "post", "send", or "share" the key numbers from an existing dashboard or insight to a channel on a schedule — even when phrased as "set up a scout/bot to post this daily" (a recurring message like this is usually a better fit for a dashboard/insight subscription than a Signals scout; when it's unclear which they want, confirm before building — see the happy path below)
• Wants to know what subscriptions they have
• Asks to stop, pause, or unsubscribe from something
• Wants to change who receives an update or how often

Subscriptions vs alerts

Subscriptions and alerts serve different purposes:

• **Subscriptions** deliver a snapshot on a fixed schedule (daily, weekly, etc.) regardless of the data
• **Alerts** fire only when a condition is met (threshold crossed, anomaly detected)

If the user says "notify me when this drops below 100", use alerts. If the user says "send me this every morning", use subscriptions.

The happy path: recurring numbers from a dashboard or insight

When someone wants the **key numbers from an existing dashboard or insight** posted to a channel on a schedule — "post the top-line from this dashboard in #launch once a day", "send the team these metrics every morning", or even "set up a scout/bot to post this daily" — the right tool is a **dashboard (or insight) subscription**, and an AI summary is its natural companion:

• Set `dashboard` (or `insight`) and deliver to Slack or email. For a **dashboard** subscription, pick the tiles via `dashboard_export_insights` — that field is dashboard-only, and an insight subscription is rejected if you send it (an insight subscription needs no tile list).
• **Offer the AI summary, don't assume it.** Per step 6, ask before enabling it, then set `summary_enabled: true` once the user agrees — it has AI-consent, quota, and budget gates that can reject the create, so keep it opt-in.
• The attached **tile snapshots are exact**. The AI summary text is model-written, so treat any figure it quotes as approximate (the same drift caveat as a prompt subscription) and lean on the snapshot for exact numbers.

Usually a better fit than a **prompt subscription** (`creating-ai-subscription`) or a **Signals scout**. A prompt subscription composes its own HogQL and can drift from the dashboard's numbers; a scout is for open-ended watching that decides what's worth surfacing, not scheduled delivery of a fixed, user-specified metric set. Don't override a user who's certain they want one of those — but when the ask is ambiguous (e.g. "set up a scout to post this daily"), suggest the subscription and confirm before building: _"A dashboard subscription is a better fit for a recurring message. Want me to set that up?"_ Reach for a prompt subscription when the user specifically asks for a free-text AI report, or when no existing insight/dashboard covers the ask.

Workflow

Listing existing subscriptions

Before creating a new subscription, check if one already exists.

Use `subscriptions-list` with optional filters:

• Filter by insight: pass the `insight` query parameter with the insight ID
• Filter by dashboard: pass the `dashboard` query parameter with the dashboard ID
• Filter by channel: pass `target_type` as `email`, `slack`, or `webhook`

Creating a subscription

Step 1: Ask the user how they want to receive it

**Always ask the user whether they want email or Slack delivery** before creating a subscription. Do not assume a channel — ask explicitly:

> Would you like to receive this via **email** or **Slack**?

If the user says Slack, you must verify the integration is available (see step 2). If the user doesn't have a preference, suggest email as the simplest option.

Step 2: Verify channel availability

**Email** requires no setup — it works out of the box. You just need the user's email address. Get it from the user context or from `org-members-list`.

**Slack** requires a connected Slack integration. Before creating a Slack subscription:

1. Call `integrations-list` and look for an integration where `kind` is `"slack"` 2. If a Slack integration exists, note its `id` — you'll need it as `integration_id` 3. If **no Slack integration exists**, tell the user: > Slack isn't connected to this project yet. You can set it up in > [Project settings > Integrations](/settings/integrations). > In the meantime, would you like to receive this via email instead?

Slack setup requires an OAuth flow in the browser — it cannot be done via MCP.

**Webhook** requires the user to provide a URL. Verify it looks like a valid URL before submitting.

Step 3: Identify the target

Get the insight ID or dashboard ID. If the user provides a URL like `/project/2/insights/pKxzopBG`, fetch the insight first with `insight-get` to get the numeric ID.

Step 4: Determine delivery settings from the user's request

| User says | Parameters | | --------------------------------------