How to connect APITube to Make.com#

To connect APITube to Make.com, use the HTTP → Make a request module: Make has no dedicated APITube app, so you call the News API over plain HTTP. Set the module’s Method to GET, add an X-API-Key header with your key, point the URL at an endpoint such as https://api.apitube.io/v1/news/everything, and enable Parse response so Make reads the JSON back as structured data. That one module pulls live news into any Make scenario, and an Iterator module then splits the returned articles so you can send each one to Slack, Google Sheets, a datastore, or an AI module — no code required.

You need a Make account and an APITube API key from your dashboard — see where to find and create your API key. Everything below builds on one HTTP module.

Why do you use the HTTP module instead of an APITube app?#

There is no dedicated APITube app in Make, so you call the REST API directly. Make’s generic HTTP → Make a request module sends arbitrary HTTP calls, which is all APITube needs — every News API endpoint is a normal GET URL. The API also accepts POST on its search endpoints, but GET is the simpler fit for a Make scenario.

Add an HTTP module as the first step after your scenario trigger, choose Make a request, and set Method to GET. Paste an APITube endpoint into the URL field, and turn on Parse response so downstream modules can map individual fields instead of a raw string.

How do you authenticate the Make request?#

APITube reads your key from any of three places, so pick whichever the HTTP module makes easiest:

• X-API-Key header (recommended) — in the HTTP module’s Headers section, add a header named X-API-Key with your key as the value.
• Authorization header — send the value Bearer YOUR_API_KEY instead.
• api_key query parameter — append api_key=YOUR_API_KEY to the URL. This works, but a key in the URL lands in scenario logs, so prefer a header.

Header name:  X-API-Key
Header value: YOUR_API_KEY

If a request comes back with HTTP 401, the key never reached APITube or did not match — recheck the header name and value. For every authentication option, see how to authenticate your API requests.

Which APITube endpoint should the HTTP module call?#

The base URL is https://api.apitube.io. The endpoints you will reach for most from Make are:

Endpoint	What it returns
/v1/news/everything	Search all articles with the full set of filters
/v1/news/top-headlines	Top news from authoritative sources
/v1/news/article	A single article by ID
/v1/news/story/:articleId	Every article covering the same story
/v1/news/trends	Trending topics and aggregations

Filters are query parameters on the same URL. A monitoring call — keywords in the title, English only, newest first — looks like this:

https://api.apitube.io/v1/news/everything?title=artificial+intelligence&language.code=en&per_page=50&sort.by=published_at&sort.order=desc

Change title to track different keywords, add source.country.code=us (a two-letter country code) to limit by country, or add published_at.start to set a date floor. The sort.by parameter also accepts relevance, engagement, quality, controversy and trust; sort.order is asc or desc. The complete list is in the official News API parameter reference.

How do you iterate over the returned articles?#

The HTTP module returns a JSON envelope, and the articles live in the results array — the envelope wraps it with status, page and limit. Add an Iterator module after the HTTP module and set the array to results. Make then emits one bundle per article, and the modules after the Iterator run once for each one.

The field names matter, because they are not the generic ones:

• Article link is href — there is no top-level url field, so mapping url returns nothing.
• Source is source.domain (for example reuters.com) — the source object has no name field.
• Headline is title, and publish time is published_at (ISO 8601, UTC).
• Sentiment label is sentiment.overall.polarity (positive, neutral or negative).

Mapping the real paths — href and source.domain rather than url and source.name — is the difference between a full record and an empty one. See how to run your first news search for what each field means.

How do you build a scheduled news scenario?#

A common recipe collects matching articles on a schedule and drops them into a destination. It chains four modules:

1. Schedule the scenario — open the scenario’s clock settings and set it to run every 15 minutes so it polls on its own.
2. HTTP → Make a request — a GET to your /v1/news/everything URL with the X-API-Key header and Parse response on.
3. Iterator — set the array to results so each article flows through separately.
4. Destination module — for example Slack (create a message), Google Sheets (add a row), or a Data store module, mapping each article’s fields into the output.

Add a Filter between the Iterator and the destination that only passes when the article count is greater than 0, so an empty poll never posts a blank alert. To summarize each article, insert an AI module and feed it the title and body fields.

How do you avoid duplicates and rate-limit errors?#

Two settings keep a scheduled scenario clean. First, add published_at.start with a rolling cutoff so each poll only asks for articles published since the last run — that stops the same story arriving on every cycle. Second, respect the limits: APITube allows 50 requests per minute on a live key, and repeatedly exceeding the limit temporarily bans the key after 30 violations, so keep the scenario interval sensible (every 15–30 minutes is plenty). Request at most per_page=250 articles per call, and page through larger result sets with the page parameter — see how to paginate through results. Encode spaces in query values as + or %20 (for example title=climate+change).

Common Questions#

• Does Make have an official APITube app?
• Where do I put my API key in Make?
• Which field holds the article link?
• Why is the article body cut short in Make?

Does Make have an official APITube app?#

No. There is no dedicated APITube app in Make, so you use the HTTP → Make a request module to call the News API over HTTP. That module can hit any APITube endpoint with a GET request, which covers search, top headlines, single articles, stories and trends — everything a no-code scenario needs. The same plain-HTTP approach works in Zapier and other automation tools.

Where do I put my API key in Make?#

In the HTTP → Make a request module, open the Headers section and add X-API-Key with your key as the value. This keeps the key out of the URL. You can pass api_key=YOUR_API_KEY in the URL instead, but that leaks the key into your scenario’s execution log, so the header is safer for anything you keep running.

Which field holds the article link?#

The canonical link to the original article is the href field on each object in the results array — not url. Likewise, the publisher is source.domain, not source.name. Map those exact paths after your Iterator module to fill a Slack message, spreadsheet row or data store correctly.

Why is the article body cut short in Make?#

Because the key is on the free plan or is a test key. In those two cases APITube trims body, description and the URL fields to a short preview and appends a marker — ...[Upgrade subscription plan] on the free plan, or ...[Test mode — use a live key for full content] on a test key. It is not a Make or mapping problem — switching to a live key on a paid plan returns full content. This is covered in detail in why are my results masked or placeholder text.