Daily Hightouch audience activation pulse for marketing

By General Input

Every weekday at 8am ET, get a marketing-friendly Slack summary of how your Hightouch audiences moved overnight across Meta, Customer.io, Salesforce, and more.

Integrations

  • Hightouch
  • Google Sheets
  • Slack Bot

Type

Agentic Task

Categories

  • Marketing
  • Operations

Every weekday morning at 8am ET, give my marketing team a Hightouch audience activation pulse so they can see how the audiences we push to ad platforms and lifecycle tools changed overnight. Build this as an agent workflow with a cron trigger.

Step 1. Enumerate the relevant syncs. Use Hightouch List Syncs to pull every sync in the workspace. Filter to ones whose destination is a marketing or ad activation tool based on sync names and destination metadata. Treat these as marketing destinations: Meta-style ad platforms (Meta, Google Ads, TikTok, LinkedIn), lifecycle and email tools (Customer.io, Iterable, Braze, Klaviyo), and CRMs used by marketing (Salesforce, HubSpot). Skip anything clearly internal (warehouses, internal Postgres, internal Slack channels, etc.).

Step 2. For each marketing sync, call Hightouch List Sync Runs and grab yesterday's run. Capture the run status (success, partial, failed) and the row count that was synced to the destination (the audience size).

Step 3. Read the trailing 14 days of row counts from a Google Sheet tracker using Get Values. The sheet has one row per audience per day with columns for date, sync id, sync name, destination, and row count. Compute the rolling 14 day average per audience so you have a baseline to compare yesterday against. The 14 day window is a reasonable default and should be easy for the user to change.

Step 4. Flag anything notable. A sync is notable if yesterday's audience size moved more than 15 percent versus the trailing average, or if the run failed or partially failed. Everything else is steady state.

Step 5. Append a new daily snapshot row per sync to the Google Sheet using Append Values so tomorrow's baseline includes today. One row per sync with date, sync id, sync name, destination, row count, status, and the computed delta.

Step 6. Post a marketing-friendly Slack summary to the marketing channel using the Slack Bot Send a Message action. Group by destination (one section per platform: Meta, Customer.io, Salesforce, Iterable, etc.). For each audience name within a destination, show the current size, the day over day delta in plain numbers and percent, a one line plain-English read on what the change likely means for campaign performance, and a recommendation: scale spend up, pause, or investigate. Keep it scannable. Bold the audiences with notable moves at the top of each section. Bury the steady-state audiences in a single No change footer at the bottom listing just the names. Lead the whole message with any failed runs so they are impossible to miss.

Tone: write for non-technical marketers. Avoid Hightouch jargon (do not say sync, model, source) in the Slack output. Say audience and destination. Frame deltas in terms of campaign impact, not data pipelines.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentLocal listing health board for every location you manageLet support send one-off Loops emails without an engineerA brand asset library your marketing team actually searchesTurn Mailjet email clicks into ranked HubSpot follow-upsClean out the Looker dashboards and Looks nobody opensStop cold emails to anyone with a live deal in PipedriveLiveKit live operations console for room moderationWake up dormant Keap leads with a researched reasoniMessage campaign console with pre-flight checks and delivery board