See llms.txt for all machine-readable content.

Back to Templates

Route Juicer brand mention alerts between Telegram support and marketing chats

Created by

Created by: Juicer Social || juicer-social
Juicer Social

Last update

Last update a day ago

Categories

Quick overview

This workflow listens for new posts in a Juicer feed and sends real-time brand mention alerts to Telegram, routing negative-sentiment posts to a support chat and all other mentions to a marketing chat while limiting large batches to a configurable number of top-priority posts.

How it works

  1. Triggers when Juicer sends a post.created event for new feed posts (one item per post).
  2. Adds your Telegram support and marketing chat IDs and a maximum alerts-per-delivery limit to each incoming post.
  3. Sorts and trims incoming posts to the most important items by prioritizing negative sentiment first and then the newest posts.
  4. Checks each remaining post’s ai_sentiment value to determine whether it is negative.
  5. Sends negative mentions to your support Telegram chat with the post text and URL.
  6. Sends non-negative mentions to your marketing Telegram chat with the post text and URL.

Setup

  1. Install and configure the Juicer community node (n8n-nodes-juicer) and add your Juicer API key credentials to the Juicer trigger.
  2. In Juicer, create or select a feed that delivers post.created events and ensure posts include the ai_sentiment field (for example by enabling AI moderation/sentiment in the feed).
  3. Add Telegram bot credentials in n8n and replace the support and marketing chat IDs in the workflow settings.
  4. Set the max_alerts_per_delivery value to control how many posts are sent when Juicer delivers a large batch.
  5. Activate the workflow and ensure your n8n instance is reachable over HTTPS so Juicer can deliver webhook events.

Requirements

  • A Juicer account with an API key and a feed with AI moderation turned on
  • A Telegram bot added to your support and marketing chats

Customization

  • Limit alerts to specific feeds with the trigger's Feed IDs option
  • Swap the Telegram nodes for Slack, Microsoft Teams or email

Additional info

This template uses the verified Juicer community node (n8n-nodes-juicer). On self-hosted n8n, install it first under Settings > Community nodes. Tested end to end with a live Juicer feed: the first sync of a new source can deliver 100+ posts at once, which the alert cap keeps to a few messages.