Quick overview
This workflow runs daily and monitors Meta Ads Library creatives for changes using an Apify Actor, then sends a single formatted change report (or failure alert) to a Telegram chat with links to the full Apify dataset and run details.
How it works
- Runs every day at 08:00 (or on manual test) to start a monitoring cycle.
- Builds a safe Apify Actor input from your targets (brand terms or Facebook page URLs) and applies filters like country, active status, media type, and maximum ads per target.
- Runs the Apify Actor
luminar~meta-ads-library-creative-changefeed with a maximum cost-per-run guard and waits for the run to finish.
- If the run succeeds, fetches the Actor’s dataset items from Apify and analyzes them to detect NEW, UPDATED, and ENDED ads and any coverage warnings.
- Renders exactly one HTML Telegram message that summarizes changes (or confirms “no changes”), and adds buttons to open the Apify dataset and the run & cost page.
- If the Apify run does not finish successfully, sends a Telegram failure alert with a link to the failed Apify run.
Setup
- Install the community node package
@apify/n8n-nodes-apify in your n8n instance.
- Add an Apify OAuth2/API credential and connect it to both Apify nodes used to run the Actor and read the dataset.
- Add a Telegram bot credential, start a chat with the bot, and set your Telegram chat ID in the Monitoring settings.
- Update Monitoring settings with your targets, country/status/media filters, max ads per target, and the maximum cost per run in USD.
- Test the workflow with the manual trigger, then activate the daily 08:00 schedule.