Send a Digest to Discord or Slack

The email always comes. A Digest can also post each Issue to the same destinations your Alerts use: a Discord channel, a Slack channel or a URL you own.

Add the destination

Under Settings, Destinations:

• Add Discord channel for a Discord channel.
• Add to Slack for a Slack channel.
• Add destination URL for a URL you own.

Choose it on the Digest

Pick the destination under Destinations when you set up the Digest, or later in the View's Digest card. A Digest can post to more than one.

What gets posted

One post per Issue, a summary rather than the whole table:

• Discord: the View's name, linking to the Issue, then "Your Digest," and the date, the count per section ("3 Movers | 2 New | 2 Gone"), and the top 5 Movers, each with its get-in, its change and a link to the event.
• Slack: "Your Digest:" with the View's name and the date, linking to the Issue, then the count per section and the top 5 Movers.
• A URL you own: a JSON body with kind set to digest_issue, so it can tell an Issue from an Alert.

A first Issue posts "Your Screen today" with its number of events, and no Movers.

{
  "source": "ticker",
  "kind": "digest_issue",
  "view": "GA rooms in my markets",
  "view_url": "https://findticker.com/views/…",
  "issue_id": "…",
  "issue_url": "https://findticker.com/views/…/issues/…",
  "issue_date": "2026-10-08",
  "first": false,
  "count": 40,
  "sections": { "movers": 3, "new": 2, "gone": 2 },
  "movers": [
    {
      "event": "…",
      "event_url": "https://findticker.com/…",
      "get_in": 120,
      "get_in_change": 40,
      "get_in_pct": 50,
      "listings": 18,
      "days_to_event": 21
    }
  ]
}

The whole Issue is one click away: the post links to it, and the Issue page has the files. See Read an Issue.