n8n Larvabot to Slack Lead Alerts via HTTP Request

Turn high-relevance Larvabot conversations into Slack lead alerts—automatically every 15 minutes

This n8n workflow automatically pulls the newest scored conversations from the Larvabot API, filters for items with a high relevance score (85+), and posts each qualifying result to your selected Slack channel with the source link, fit rationale, and a drafted reply.

What this workflow does

• Runs on a schedule: Executes every 15 minutes using a Schedule Trigger.
• Fetches new conversations: Calls the Larvabot API to retrieve up to 100 of the newest conversations.
• Prevents duplicates: Skips conversations that were already sent in previous workflow executions (via a remove-duplicates step).
• Filters by relevance: Keeps only conversations with a relevance score of 85 or higher.
• Posts to Slack: For each qualifying conversation, sends a Slack message that includes:
  • the conversation title
  • platform
  • relevance score
  • source link
  • “why it fits” rationale
  • the suggested reply draft

Use cases

• Sales & partnerships: Surface only highly relevant conversations as “lead alerts” in Slack for fast follow-up.
• SaaS operators: Monitor emerging signals and route top-matching opportunities to your team without manual checking.
• Automation engineers: Stand up a clean, scheduled n8n pipeline using HTTP Request + Slack notifications with deduplication.

Technical details

• Schedule Trigger (runs every 15 minutes)
• HTTP Request to Larvabot API using Authorization: Bearer <token>
• Filter (relevance score threshold at 85)
• Remove duplicates (skip previously sent conversations)
• Slack node (posts to a selected channel)
• Sticky Note for workflow documentation

Quick setup

Create a Larvabot API key and add it as an HTTP Header Auth credential, connect your Slack credential, and choose the target channel. Optionally adjust the relevance threshold or query parameters (such as limit) to control how many conversations are monitored.