What this workflow does This workflow allows you to monitor multiple Github repos simultaneously without polling due to use of Webhooks. It programmatically allows for adding and deleting of repos to your watchlist to make management convenient. Description Can monitor multiple repos simultaneously. Programmatically register or unregister repos from a list. No need for manual work. Webhook notification means no constant polling necessary. Setup 1. Creating Credentials on Github Generate a personal access token on github by following these esteps; Right hand side of page -> Settings -> scroll to bottom -> Developer Settings > Personal Access Token > Tokens (classic) > Generate New Token Give scopes: admin:repo_hook repo (if you want to use it for your own private repo) if you need more help, see here: https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens 2. Setting Credentials in n8n In Register Github Webhook Authenticaion > Generic Credential Type Generic Auth Type > Header Auth Header Auth > Create New Credential with Name set to 'Authorization' and Value set to 'Bearer '.
Tags
TelegramRelated workflows
See all Slack→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
Post a daily Asana project status digest to Slack
Quick overview This workflow runs every weekday morning to fetch tasks from a specified Asana project, bucket them by due status and completion activity, and post a Slack Block Kit digest with counts, key task links, and per-assignee open workload. How it works Runs on a weekday-morning schedule. Pulls tasks from a chosen Asana project via the Asana REST API, including assignee, due date, completion status, and task links, and paginates through results as needed. Groups open tasks into overdue, due today, due this week, and unassigned buckets, and also collects tasks completed within the configured lookback window. Calculates summary counts and open-task load per assignee. Formats the results into a Slack Block Kit message with a short totals line and up to five linked tasks per bucket. Posts the digest to the specified Slack channel. Setup Add an Asana Personal Access Token (Asana API credentials) and select it for the HTTP request that fetches project tasks. Add a Slack OAuth credential and ensure the app/bot can post messages to your target channel. In the configuration step, set your Asana project GID, Slack channel ID, timezone, and the lookback window for recently completed t