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).
Tags
Related workflows
See all Slack→Manage Slack channel and users automatically
Explore this workflow on its official n8n template page.
Send selected GitHub events to Slack
Gets triggered by GitHub once a user stars/unstars a repository Checks if star got added or removed and forwards data depending on that Sends notification to Slack
Notify a team channel about new software releases via Slack and GitHub
This workflow automatically notifies the team in a Slack channel when code in a GitHub repository gets a new release. Prerequisites A GitHub account and credentials A Slack account and credentials Nodes GitHub Trigger node triggers the workflow when a release event takes place in the specified repository. Slack node posts a message in a specified channel with the text "New release is available in {repository name}", along with further details and a link to the release.