Search the web
Add an HTTP Request action and paste this configuration. If you don’t send a key, theX-Keenable-Title header is required. Set it to your app’s name.
<<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, because description comes back empty.
To keep a search to one site and a time window, add site and a date filter to payload:
YYYY-MM-DD, a timestamp or a relative window such as 7d (date filters). Each result carries a few thousand characters of page text. To keep events smaller, set snippet_max_length (180 to 10000).
Read a page
Fetch is a GET request, and Tines sends a GET action’spayload as query parameters:
search_the_web is the name of the search action. The page comes back as markdown in body.content, with title and published_at (an ISO 8601 timestamp) when known. Keenable returns its indexed copy when it has one. To fetch the page from the source every time, add "live": "true" to payload (fetch reference).
Use an API key
Keenable limits the public endpoints per IP address, and every client on that address shares the limit. For stories that run on a schedule or at volume, use a key to lift the hourly limit:- Create a key in the Keenable console.
- In Tines, open Credentials, create a Text credential named
keenableand paste the key. - Drop
/publicfrom the action URLs and send the key instead of the title header:
https://api.keenable.ai/v1/fetch with the X-API-Key header. Keyed calls count against your credits. Rate limits lists the limits for both tiers.