Skip to main content
HTTP Request action Tines stories call any REST API with the HTTP Request action. Point one at Keenable and a story can search the web for an alert, an indicator or a vendor, read a page as markdown, and pass the result to the next action. There is nothing to install, and no key or credential to start.

​
Search the web

Add an HTTP Request action and paste this configuration. X-Keenable-Title names your app and is required without a key.
Replace <<receive_event.body.query>> with a field from an upstream action. The action emits the results in body.results, each with title, url, snippet (text from the page) and, when known, published_at. Read snippet: description comes back empty. To keep a search to one site and a time window, add site and a date filter to payload:
Dates take YYYY-MM-DD, a timestamp or a relative window such as 7d (date filters). Results carry a few thousand characters of page text each; snippet_max_length (180 to 10000) keeps events smaller.

​
Read a page

Fetch is a GET request, and Tines sends a GET action’s payload as query parameters:
Here search_the_web is the name of the search action. The page comes back as markdown in body.content, with title and published_at (Unix seconds) when known. Add "live": "true" to payload for a page Keenable has not indexed (fetch reference).

​
With an API key

The public endpoints are limited per IP, and that limit is shared with everything else on the same address. A key lifts the hourly limit for stories that run on a schedule or at volume:
  1. Create a key in the Keenable console.
  2. In Tines, open Credentials, create a Text credential named keenable and paste the key.
  3. Drop /public from the action URLs and send the key instead of the title header:
The fetch action changes the same way, to https://api.keenable.ai/v1/fetch with the X-API-Key header. Keyed calls count against your credits; both tiers are on Rate limits.