Auto-enrich new monday.com boards
Build an upstream enrichment motion: when a new monday.com board is created, Pipedream grabs a company domain or name, calls Lusha’s Company API, then writes firmographic fields back into monday, so the board is complete and usable from the get-go.
Why this works
monday boards usually don’t fail because they’re messy. They fail because they’re incomplete. A board gets created fast, but key context (industry, size, revenue, location) is missing—so people pause, research, and build side spreadsheets to compensate.
This play fixes the problem at the source: the moment a board exists, it gets enriched automatically, before routing, workflows, SLAs, and reporting start depending on fields that may or may not be filled.
What you get
A monday workspace where new boards arrive with standardized company fields already populated, including industry, employee count, estimated revenue, HQ/location, domain, and company name standardization (plus signals like tech stack/funding when available).
monday.com field model
“Company identifier” field (required)
Pick one field your team can reliably provide when creating boards:
- Company domain (best), or
- Company name
“Firmographics” fields (outputs to write back)
Create columns (or board fields) for:
- Industry
- Employee count
- Estimated revenue
- HQ / location
- Domain
- Standardized company name
- Optional: tech stack signals / funding context (when available)
Tip: Keep naming consistent across workspaces so automations don’t break when teams copy templates.
How to set it up
Use the Pipedream template
Start from the Pipedream template designed for this exact flow: it listens for a “new board created” event in monday.com.
Connect monday.com + authenticate your Lusha API key
Authorize monday, then connect Lusha using your API key so Pipedream can call the Company API.
Decide which boards should trigger enrichment
Add filters so only relevant boards get enriched (by board type, board name pattern, workspace, or field availability).
Tip: This is also how you avoid wasting API calls on internal project boards.
Map the company identifier field
Tell the workflow where to grab the domain/name from the board’s initial fields, then pass that into Lusha’s Company API.
Map Lusha outputs to monday fields
Write enriched firmographics back into the board columns you created (industry, size, revenue, location, etc.).
Tip: The workflow won’t overwrite trusted fields unless you configure it to. All overwrite behavior is under your control.
Test with a new board
Create a sample board with a valid domain/name. Confirm:
- Enrichment runs on creation
- Fields are populated correctly
- Non-matching boards get skipped (no change)
What to do next
- Extend enrichment from board-level to item-level (accounts/companies inside a board) for ongoing updates.
- Add a Slack/email alert when a “high-fit” company board is created (based on industry/size thresholds).
- Sync enriched companies with your CRM to keep systems aligned (monday for work, CRM for record-of-truth).
The goal: monday becomes a reliable GTM workspace, and complete context shows up automatically. So nobody has to play data catch-up.
No FAQ items available at this time.
Ready to build this?
Get started with Lusha and set up this play in minutes.
