Quick Overview This workflow runs weekly to track your Google rankings for multiple keywords using SearchApi, compares current positions to the previous run stored in an n8n Data table, and posts a formatted movement report to Slack. How it works Runs every week on a schedule. Loads your target domain, comma-separated keyword list, and Google location, then fetches previously saved ranks from an n8n Data table. Splits the keyword list into individual keywords and queries Google via SearchApi for the first 5 pages of results per keyword. Scans the organic results to find your domain’s best position per keyword and calculates week-over-week movement (up, down, new, dropped out, or not ranking in the top 50). Formats the results into a Slack Block Kit message with a plain-text fallback. Posts the report to a Slack channel and upserts currently ranking keywords back into the Data table for the next comparison. Setup Add a SearchApi.io credential in the SearchApi node. Create or select an n8n Data table (for example, “Rank History”) with columns for keyword, position, url, and last_checked, and select it in both the read and upsert Data table nodes.
Tags
Related workflows
See all Slack→
Clean duplicate and dead YouTube playlist videos with Slack reports
Quick overview This workflow runs weekly to scan a YouTube playlist, flagging deleted/unavailable/private videos and duplicate entries, optionally removing them from the playlist, and posting a cleanup report to a Slack channel. How it works Runs every week on a schedule trigger. Loads the target YouTube playlist ID, the dry-run toggle, and the Slack channel ID. Retrieves all items from the specified YouTube playlist and looks up each referenced video’s status. Classifies each playlist item as active or dead (deleted/unavailable/private) and flags duplicates by video ID while keeping the first occurrence. If dry run is disabled, deletes the flagged playlist items from YouTube in batches. Builds a summary of what was found/removed and posts the report to the configured Slack channel. Setup Connect a YouTube (Google) OAuth2 credential with permissions enabled to read playlists and delete playlist items as needed. Connect a Slack credential with permission enabled to post messages to your chosen channel. Set your playlistId, slackChannelId, and (optionally) dryRun in the workflow options before turning on the workflow. Requirements A Google account with YouTube access and an OAuth2 cr
Draft and stage LinkedIn re-engagements with HeyReach, Twain, and Slack
Quick overview This workflow runs weekly (or manually) to pull tagged “cold” HeyReach conversations, uses Twain to draft context-aware re-engagement messages, then stages leads in a HeyReach list and notifies Slack for review while tagging processed leads to avoid duplicates. How it works Runs on a weekly schedule or via a manual trigger. Fetches all conversations from the HeyReach Inbox API using pagination. Filters conversations by HeyReach lead tags (include tags like “Cold”/“Not interested” and exclude tags like “Re-engaged”) and extracts each lead’s LinkedIn URL, name, and prior message thread. Sends the conversation context to Twain to generate a re-engagement sequence draft and add the contact to the specified Twain campaign. Adds the lead to a HeyReach re-engagement list and stores the first Twain draft message in a custom user field. Posts the drafted re-engagement message to a Slack channel for review. Tags the lead as “Re-engaged” in HeyReach to prevent reprocessing. Setup Add HeyReach API credentials for HTTP Header Auth and ensure the header matches HeyReach requirements (for example, X-API-KEY). Add Twain API credentials for HTTP Header Auth and ensure the header matc
Create social visuals from blog RSS with Canvora and Slack
Quick overview This workflow watches your blog RSS feed for new posts, sends each post URL to Canvora to generate branded social image formats (and an optional carousel), polls until generation completes, and posts the resulting image links to a Slack channel for review. How it works Triggers when a new item appears in the configured RSS feed on an hourly polling schedule. Builds a Canvora generation request using the blog post URL plus your selected output formats, optional carousel settings, language, and brand kit ID. Creates the generation in Canvora via its API. Polls Canvora every 30 seconds to fetch the generation status until it completes, fails, is cancelled, or times out after about 10 minutes. If the generation succeeds (completed or partial), sorts the returned assets and formats a Slack message containing the public file URLs and an edit link. Posts the message to the chosen Slack channel for human review, or sends a Slack alert if the generation fails or times out. Setup Create a Canvora account and add an API key as an HTTP Header Auth credential (header name X-API-Key). Update the RSS Feed Trigger with your blog’s RSS URL. Optionally set Canvora format IDs, carousel