See llms.txt for all machine-readable content.

Back to Templates

Route rising Google Trends queries into editorial tasks with Apify and Google Sheets

Created by

Created by: Vadim || automa-flow
Vadim

Last update

Last update 2 days ago

Categories

Quick overview

Give an SEO editor a page to review when a related search starts rising. The workflow matches Google Trends queries to a page and an owner, sends unmatched queries to triage in Google Sheets, and posts the editorial queue to Slack.

How it works

  1. A daily or manual run reads your topic watchlist from Google Sheets and checks relative interest and related searches through Apify. The first run establishes a baseline.
  2. When a fully checked topic produces a new rising query or Breakout, the workflow looks up the topic ID and market in your page inventory. A match with both a page URL and owner creates a review task. Missing either puts the query in Needs triage.
  3. Repeated events leave the task alone. A later growth change updates the evidence on an open task while preserving the editor's assignment, page and status. Closed and dismissed tasks stay closed. Incomplete topic checks appear in Errors.
  4. Slack receives the query, market, reason for review, page when assigned, and a link to the Editorial Tasks tab. Editors decide which pages to update and record their decision in the queue.

Setup

  1. Download the six-tab starter workbook from the yellow Setup note and import it into a new Google Sheet. Keep the tab names and row-one headers. In Topics, replace the example entries with your keywords, country, a unique externalId, a page URL and an editor. Leave the page or owner blank to use triage.
  2. Open the Editorial Tasks tab. Copy its full browser URL, including the gid, into tasksUrl in Configure. Choose a stable monitorId unique to this watchlist. Review the per-run Actor spending cap, which defaults to USD 1.
  3. Select a Google Sheets credential with edit access on all ten Sheets nodes. On the five Apify HTTP Request nodes, select one Header Auth credential. Set the header name to Authorization and the value to Bearer followed by a space and your Apify API token.
  4. Connect Slack, select your channel ID and invite the bot. Alternatively, disable Send to Slack and enable and configure the SMTP node. Execute once manually, inspect Runs and Errors, and enable the daily schedule at 06:17 in your workflow time zone when ready. Keep executions for one watchlist sequential.

Requirements

  • A Google account with edit access to the workbook, an Apify account with permission to run the Google Trends Actor and read its output, and a Slack channel or an SMTP sender for delivery.

Additional info

This template is free. The template creator also publishes the Google Trends Actor on Apify. Apify usage may incur charges. The default spending cap is USD 1 per Actor run.

The worked example shows two outcomes: “cold brew ratio” goes to the editor responsible for the US guide, and “iced tea concentrate” goes to UK editorial triage. The example uses simulated data.

View the example: https://api.apify.com/v2/key-value-stores/BA7oG61aVmyDVfjEw/records/trends-editorial-demo-99d7011677f9.png