Make does not ship a Trends API module. Official HTTP app docs send arbitrary REST through HTTP > Make a Request. Method POST. URL https://api.trendsapi.ai/api. The envelope is {"statusCode": int, "body": string}. Enabling Parse Response decodes the envelope, not the inner payload. Open body again. Contract: the API reference. Caps: pricing.
Make a Request is the client
Headers:
Authorization: Bearer <api_key>
Content-Type: application/json
Body type JSON or raw application/json:
{"mode":"get_time_series","source":"google search","keyword":"bitcoin"}
A growth compare uses mode get_growth and a comma-separated source list. That shape is on compare sources. Do not paste a live type into source.
Set a timeout on the module. 401 is the header. 429 is the cap. Failed 4xx calls do not count as a successful lookup.
Parse Response then Parse JSON
Parse Response on the HTTP module yields statusCode and a string body. Add JSON > Parse JSON and point it at body. After that, date and value exist on each series point. Skipping the JSON module leaves later modules mapping a quoted string. The two-step rule is on parse the body.
Iterator walks points, not the envelope
get_time_series after the second parse is an array. Add an Iterator on that array to write one row per week into Sheets or a datastore. get_growth is an object. Iterate results, not the root. get_top_trends iterates data. Mixing those three shapes in one scenario without a router is an empty bundle, not a 401.
Auth header rules stay on authentication.