Meta Ads Change Alerts to Telegram | Apify + n8n Workflow

Get Meta Ads change alerts in Telegram—automatically with Apify + n8n

This n8n automation workflow monitors Meta Ads Library creatives for changes (NEW, UPDATED, ENDED) using an Apify Actor, then sends a single daily Telegram report with direct links to the full dataset and run details.

What this workflow does

• Runs daily at 08:00 (or can be started for manual testing) to begin a monitoring cycle.
• Builds a safe Apify Actor input based on your targets (brand terms and/or Facebook page URLs), applying filters such as country, active status, media type, and a maximum ads per target limit.
• Executes the Apify Actor luminar~meta-ads-library-creative-changefeed, including a maximum cost-per-run guard, and waits for the run to finish.
• On success, fetches the Actor’s dataset items and analyzes them to detect NEW, UPDATED, and ENDED ads, plus any coverage warnings.
• Renders exactly one HTML Telegram message: either a formatted change summary (or confirmation that there were no changes).
• Includes buttons to open the Apify dataset and the run & cost page.
• If the Apify run fails to finish successfully, sends a Telegram failure alert with a link to the failed Apify run.

Use cases

• Marketing and competitive intelligence teams tracking when competitors launch, refresh, or stop Meta ads.
• SaaS operators monitoring ad creatives for specific brands/pages and reacting quickly to changes.
• Automation engineers needing a reliable Meta Ads Library → Telegram reporting pipeline with Apify dataset references.

Technical details

• Nodes/steps: if, set, code, telegram, sticky note, and @apify/n8n-nodes-apify (Apify Actor run + dataset read).
• Credentials: Apify OAuth2/API for both running the Actor and fetching dataset items; Telegram bot for alerts.
• Primary Actor: luminar~meta-ads-library-creative-changefeed.