---
title: MarketMaster Marketing Automations
description: Run recurring signal trackers, lead radar, event scans, and tracked-page research with in-app and Slack digests.
canonical_url: https://marketmaster.dev/automations
html_url: https://marketmaster.dev/automations
content_type: text/markdown
robots: noindex, follow
---

# MarketMaster Marketing Automations

> Always-on research that collects new market signals on a daily or weekly schedule, removes repeats, ranks what matters, and writes a source-linked digest.

Creating, pausing, running, and deleting an automation requires JavaScript, a signed-in account, and a Pro or Studio plan. This document describes the workflow without requiring the dashboard.

## Monitor templates

| Template | Default cadence | Default sources | What it looks for |
|---|---|---|---|
| Daily GTM signal tracker | Daily | Reddit, web/news, tracked pages | Category shifts, objections, competitor moves, and useful conversations |
| Weekly lead radar | Weekly, Monday | Reddit, web/news, Hacker News | People describing a live problem, evaluating options, switching, or asking for recommendations |
| Event and conference scanner | Weekly, Monday | Events, web/news | Conferences, summits, meetups, and webinars where the target buyer may learn, speak, or buy |

Each monitor accepts a short category, product, or ideal-customer query. A signed-in user can adjust the cadence, weekly delivery day, sources, and delivery method before saving.

## Supported sources

- **Reddit:** new discussions and buying questions.
- **Web and news:** recent category and competitor coverage.
- **Hacker News:** technical and startup conversations.
- **Tracked pages:** up to six competitor blogs or industry pages supplied by the user.
- **Events:** conferences, summits, meetups, and webinars.

At least one usable source is required. A tracked-page source is removed if no valid HTTP or HTTPS page was supplied.

## Cadence, limits, and delivery

- Cadence can be daily or weekly.
- Scheduled collection runs at 12:00 UTC; a weekly monitor also stores a weekday.
- A Pro or Studio account can keep up to ten automations.
- Digests are delivered in the app, to a connected Slack incoming webhook, or to both.
- If Slack delivery fails, the complete in-app digest remains available.
- Runs expose source health instead of silently treating a failed source as a successful empty result.

## What a digest contains

Each new signal can include its source, title, source URL, publication time, why it matters, and a suggested next move. The digest also records source success or failure, a summary, a confidence label, and a watchlist. Old links are deduplicated rather than recycled as new findings.

## No-JavaScript planning worksheet

1. Choose one job: GTM signals, lead radar, or events.
2. Write a bounded query naming the product, category, audience, or competitor set.
3. Choose the smallest source set that can answer that query.
4. For tracked pages, list no more than six specific HTTP or HTTPS URLs.
5. Choose daily only when the decision can change daily; otherwise choose a weekly weekday.
6. Decide whether the digest belongs in the app only or also in Slack.
7. Return to [the automation dashboard](https://marketmaster.dev/automations) with JavaScript enabled, sign in, and save the reviewed specification.

## Security and access boundary

The public page and this Markdown document do not create or run monitors. Automation APIs require an authenticated browser session and plan access. Slack webhooks are stored as account connections and should never be pasted into a guessed URL, a public prompt, or a public Markdown document.

See [pricing](https://marketmaster.dev/pricing) for plan availability and [account](https://marketmaster.dev/account) for sign-in and connection management.