Make excels at scheduled HTTP calls, routers, and alerts. Trends MCP returns normalized series and growth windows from one POST endpoint so scenarios can branch on momentum without maintaining scrapers for each platform.
Teams that live in Make often stitch LLM steps to brittle trend scrapers. Trends MCP keeps the contract simple: https://api.trendsmcp.ai/api accepts JSON for get_trends, get_growth, and related operations described in the site docs, with one bearer token for every source the product supports.
A scheduler module fires daily. An HTTP module posts a get_growth payload with the keywords the team cares about, the sources that match the campaign, and preset windows such as 30D and 3M. A router reads the parsed JSON and sends Slack messages only when growth clears an agreed cutoff. That pattern mirrors how n8n teams describe trend automation while staying inside Make’s module vocabulary.
Affiliate editors, ecommerce analysts, and agency pods already run Make for reporting. Giving them the same growth math the engineering org uses in code reduces duplicate research and keeps alerts honest when a spike is real versus noisy. The real-time trends API overview explains how those windows map to product behavior.
Make is strong at delivery; it is weaker at exploratory charts. When stakeholders need a shared view, export the JSON to Sheets or warehouse tables, then layer the visualization steps outlined on how to build a trends dashboard. The API stays the single source so chart refreshes never fork from the alerting logic.
FAQ