Skip to product information

Telegram to Slack Repair Threads with Claude Sonnet (n8n Workflow)

Telegram to Slack Repair Threads with Claude Sonnet (n8n Workflow)

 (200+Reviews)
Regular price £60.99
Regular price £60.99 Sale price
SAVE Sold out
Instant Digital Download
Unlimited Downloads
Lifetime Access in Your Account
🔥
128+ Sold
Popular with n8n builders
23 people viewing
High interest right now
9 added today
Fast-moving digital product
Telegram to Slack Repair Threads with Claude Sonnet (n8n Workflow)

Telegram to Slack Repair Threads with Claude Sonnet (n8n Workflow)

Regular price £60.99
Regular price £60.99 Sale price
SAVE Sold out

Turn Telegram repair updates into organized Slack ticket threads—with Claude Sonnet filtering

This n8n workflow watches a Telegram group for repair-job posts, uses Anthropic Claude (Claude Sonnet) to identify and categorize relevant updates, and automatically posts them to Slack as one threaded ticket per asset. Photos/documents are optionally uploaded to the correct Slack thread, and open/closed status is tracked in an n8n Data Table.

What this workflow does

  • Monitors Telegram: Triggers whenever a new message is posted in your Telegram group.
  • Claude-based triage: Sends message text (or caption) and sender details to Anthropic Claude to:
    • decide whether the update is job-relevant,
    • extract the asset/unit identifier,
    • classify the event type, and
    • produce a short Slack-ready update line.
  • Skips irrelevant messages: Messages Claude marks as not relevant are ignored.
  • Threading by asset: Looks up the asset in an n8n Data Table named repair_cases to find an existing open Slack thread.
  • Creates or replies: Posts to Slack as a reply in the existing thread if an open ticket exists; otherwise creates a new thread and stores the new thread timestamp (slack_ts) for that unit.
  • Uploads attachments: If the Telegram message includes a photo or document, the workflow downloads it from Telegram and uploads it to the corresponding Slack ticket thread.
  • Closes on “job done”: When Claude marks an update as “job done,” it updates the case status in the Data Table to closed, so the next issue starts a fresh ticket thread.

Use cases

  • Maintenance teams sharing repair updates in Telegram while leadership tracks everything in Slack.
  • Operational workflows that require consistent asset-based ticket history and attachment capture.
  • SaaS operators coordinating field repair communications across tools without manual copy/paste.

Technical details

  • Trigger: Telegram message trigger
  • AI step: Anthropic Claude (Claude Sonnet) via n8nn8n-nodes-langchainagent
  • Logic & storage: if logic and n8n Data Table (repair_cases with columns unit, slack_ts, status)
  • Posting & attachments: Slack node + Slack threaded replies with uploaded files
  • Telegram setup: Telegram bot via @BotFather (privacy mode disabled) with bot token as Telegram credentials
  • Optional documentation: Sticky Note node for workflow guidance
View full details