How to connect APITube to Zapier
Pull live news into any Zap with the Webhooks by Zapier app — set the method to GET, add your X-API-Key header, and call the News API
Written by Jacob Partington
July 4, 2026
How to connect APITube to Zapier
To connect APITube to Zapier, use the Webhooks by Zapier app: Zapier has no built-in APITube integration, so you make a plain HTTP call to the News API instead. Set the request Method to GET, add an X-API-Key header with your key, and point the URL at an APITube endpoint such as https://api.apitube.io/v1/news/everything. That single Webhooks step pulls live news into any Zap, so you can push matching articles to Google Sheets, Slack, email, or an AI summarizer without writing code.
You need a Zapier account (free or paid) and an APITube API key from your dashboard. Everything below builds on that one Webhooks step.
Why do you use “Webhooks by Zapier” instead of an APITube app?
There is no dedicated APITube app in the Zapier directory, so you call the REST API directly. Zapier’s own Webhooks by Zapier app makes arbitrary HTTP requests, which is all APITube needs — every News API endpoint is a normal GET URL.
Inside a Zap, add an action step, choose Webhooks by Zapier, and pick the Custom Request event. Set Method to GET and paste an APITube endpoint as the URL. This same step works for any endpoint, so once one Zap is running, the rest are just different URLs.
How do you authenticate the Zapier request?
APITube reads your key from one of three places, so pick whichever the Webhooks step makes easiest. In the Webhooks step’s Headers section, add a header named X-API-Key with your key as the value — this is the recommended way. You can instead append api_key=YOUR_API_KEY to the URL, but a key in the URL ends up in logs, so prefer the header. A third option is an Authorization header with the value Bearer YOUR_API_KEY.
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 the full breakdown, see how to authenticate your API requests.
Which APITube endpoint should the Webhooks step call?
The base URL is https://api.apitube.io. The endpoints you will reach for most from Zapier 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 looks like this — keywords in the title, English only, newest first:
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 complete list is in the official News API parameter reference.
How do you build a news-monitoring Zap step by step?
A common recipe collects matching articles into a spreadsheet on a schedule. It chains four steps, each a built-in Zapier app:
- Schedule by Zapier (trigger) — set it to run Every 15 Minutes so the Zap polls on its own.
- Webhooks by Zapier — a
GETCustom Request to your/v1/news/everythingURL with theX-API-Keyheader, as above. - Looping by Zapier — Create Loop From Line Items, with the articles array from the Webhooks step as the values to loop.
- Google Sheets — Create Spreadsheet Row, mapping each article’s fields into columns.
Swap Google Sheets for Slack (Send Channel Message) or Gmail (Send Email) to get alerts instead of rows, and add a Filter by Zapier step that only continues when the article count is greater than 0 so you never send an empty notification.
How do you map article fields correctly?
The Webhooks step returns a JSON envelope, and the articles live in the results array — that is what you point Looping by Zapier at. Each item in results is one article, and the field names you map matter:
- Article link is
href— there is no top-levelurlfield, so mappingurlreturns nothing. - Source is
source.domain(for examplereuters.com) — the source object has nonamefield. - Headline is
title, and publish time ispublished_at(ISO 8601, UTC). - Sentiment label is
sentiment.overall.polarity(positive,neutralornegative).
Using the real field names — href and source.domain rather than url and source.name — is the difference between a row full of data and a row full of blanks. See how to run your first news search for what each field means.
How do you avoid duplicates and rate-limit errors?
Two settings keep a scheduled Zap 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 gets the key temporarily banned after 30 violations, so keep the Schedule interval sensible (every 15–30 minutes is plenty). Ask for at most per_page=250 articles per call, and encode spaces in query values as + or %20 (for example title=climate+change). To page through more results, increment the page parameter — see how to paginate through results.
Common Questions
- Does Zapier have an official APITube app?
- Where do I put my API key in a Zap?
- Which field holds the article link?
- How many articles can one Webhooks step return?
Does Zapier have an official APITube app?
No. There is no dedicated APITube app in the Zapier directory, so you use Webhooks by Zapier to call the News API over HTTP. That app can hit any APITube endpoint with a GET request, which covers search, top headlines, single articles, stories and trends — everything a no-code workflow needs.
Where do I put my API key in a Zap?
In the Webhooks by Zapier step, 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 logs, 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 in your Zapier field mapper to fill your spreadsheet, Slack message or email correctly.
How many articles can one Webhooks step return?
Up to per_page=250 in a single call. Ask for more and the request is rejected, so page through larger result sets with the page parameter across multiple calls. For frequent polling, pair per_page with a published_at.start cutoff so each run only pulls what is new.