Ops

Auto-enrich companies from Discord messages

Build a real-time workflow that listens to new messages in specific Discord channels, identifies company mentions (names or domains), enriches them with Lusha’s Company API, and routes the enriched results to your CRM, database, or Slack—so your team can act on community signals the moment they appear.

Why this works

Discord communities move fast: product launch mentions, “we’re evaluating vendors,” hiring spikes, partnerships, funding rumors. The problem is those signals are buried in threads—and by the time someone notices, it’s too late.

This play captures the signal instantly and adds context automatically. Every company mention becomes a structured, enriched record (industry, size, location, revenue range, tech stack, funding stage), ready for routing and scoring—without manual research.

What you get

  • Instant monitoring of Discord messages in channels you choose
  • Company extraction from message text (company name and/or domain)
  • Real-time enrichment via Lusha Company API (firmographics + technographics where available)
  • Structured outputs you can route to CRM, Sheets, Slack, Airtable, or a warehouse
  • Signal-to-action workflow: filter, score, dedupe, and alert the right team automatically
Built by: Lusha
Difficulty: Medium
Tools: Discord, Google Sheets, HubSpot, Lusha, Pipedream, Salesforce

How to set it up

01

Start from the Pipedream template

Open the template and create a new workflow:

  • Trigger: New Message (Instant) from Discord API
  • Action: Lusha Company Enrich

Destination: Your CRM/DB (optional steps included/extendable)

02

Configure the Discord connection

You’ll connect Pipedream to Discord so it can listen for new messages.

Option A: Connect a Discord user (fastest for internal/private servers)

  • In Pipedream, click Connect Discord account
  • Authorize access
  • Make sure you have permission to read the target channels

Option B: Use a Discord bot (best practice for shared/team workflows)

  • Create a bot in the Discord Developer Portal
  • Add the bot to your server
  • Grant permissions:
    • Read Messages / View Channels
    • Read Message History

Then, use the bot token in Pipedream when prompted

Tip: If you can’t see a channel in selection later, it’s almost always a permissions issue.

03

Select the Discord server and channels to monitor

In the trigger step, choose:

  • Server (Guild): the Discord workspace where signals live
  • Channel(s): pick the channel(s) that generate relevant mentions, for example:
    • #partnerships
    • #vendor-recommendations
    • #jobs / #hiring
    • #startups / #funding
    • #introductions

Recommendation: Start with 1–3 high-signal channels before expanding.

04

Define what counts as a “company mention”

Add (or adjust) extraction logic to capture company identifiers from messages:

Best practice: Prefer domain extraction when possible (it reduces false positives).

05

Connect the Lusha API step

In the Lusha enrichment step:

  • Add your Lusha API key
  • Map the extracted identifier:
    • Domain (preferred) or
    • Company name (fallback)
06

Route enriched results to the right destination

Choose your “system of record”:

  • CRM (HubSpot/Salesforce):
    • Create new Account/Company records
    • Or update existing records (recommended)
  • Google Sheets: log every enriched company for review
  • Airtable/Database: store structured signals + enrichment for scoring
  • Slack: alert the team when high-fit companies appear
07

Add filters, scoring, and deduplication

Turn raw signals into qualified actions.

08

Test end-to-end

Post a test message in a monitored channel like:

  • “Anyone using acme.com for sales intelligence?”

Confirm:

  • Trigger fires instantly
  • Identifier extraction works
  • Lusha enrichment returns fields
  • Routing creates/updates the right record
  • Failures are handled (no silent drops)

What to do next

  • Monitor multiple servers (partner communities, customer communities, niche vertical groups)
  • Add “high-fit alerts”: ping Slack only when ICP match + strong intent language appears
  • Create an Ops review queue: push uncertain matches (name-only, ambiguous) into a “Needs Review” table
  • Combine signals: merge Discord mentions with RSS, job changes, intent, or webhooks for multi-signal targeting
  • Track trends: build a historical log of mentions and enrichment to spot rising accounts early

The goal: Discord is where market signals show up first. This play turns those signals into enriched, routed account intelligence automatically—so your team engages while the conversation is happening, not after the opportunity passes.

No FAQ items available at this time.

Ready to build this?

Get started with Lusha and set up this play in minutes.