Automatically enrich Easy Redmine CRM leads using Lusha and n8n.
This workflow pulls leads from Easy Redmine, enriches them with verified contact and company data via the Lusha API, and syncs updates back to the CRM — keeping records accurate without manual work.
Keeping CRM data accurate over time is harder than enriching it once.
New leads come in every day. Contact details change. Company size updates. LinkedIn profiles get refreshed. And unless someone is actively maintaining those records, CRMs quietly drift out of sync with reality.
In this post, we’ll walk through a real n8n workflow that connects Easy Redmine CRM with Lusha, automatically enriching lead records and keeping them up to date — without manual lookups or copy-paste.
The problem: enrichment that doesn’t stick
Most teams enrich leads at a single point in time:
- When a lead is created
- Before routing to sales
- Ahead of an outbound campaign
But GTM systems don’t stop there.
Contacts change roles. Companies grow. Data goes stale. And once workflows depend on that data — routing, scoring, segmentation — inaccuracies start to compound.
What RevOps teams actually need is repeatable enrichment that fits into automation, not one-off lookups.
The workflow: Easy Redmine + Lusha via n8n
This n8n workflow automates lead enrichment by:
Pulling new or updated leads from Easy Redmine
Querying Lusha’s API for verified contact and company data
Transforming the results into CRM-ready fields
Syncing enriched data back into Easy Redmine automatically
Once set up, the workflow runs on a schedule and keeps records current without manual intervention.
How it works (step by step)
1. Schedule trigger
The workflow runs daily (for example, every morning at 10:00), ensuring new leads are enriched consistently.
2. Fetch leads from Easy Redmine
Leads are pulled using a saved query — such as “today’s leads” or “leads missing key fields.”
3. Split records for enrichment
Each lead is processed individually, making it easier to enrich, transform, and update records cleanly.
4. Enrich with Lusha
Using lead fields like email, name, and company, the workflow sends an API request to Lusha to retrieve verified contact and company data.
5. Filter failed matches
Leads that can’t be matched or enriched are skipped, preventing partial or broken updates.
6. Transform data for CRM use
The workflow flattens and cleans the response:
- Extracts phone numbers, emails, LinkedIn profiles, job info
- Normalizes company size ranges
- Maps nested fields into Easy Redmine-friendly formats
7. Update Easy Redmine
Each enriched lead is updated back into the CRM via API, keeping records complete and usable.
What this enables
Once enrichment is automated inside your workflows, teams can:
Keep CRM records accurate over time
No cleanup sprints or manual updates.Improve lead routing and scoring
Use employee count, role data, or LinkedIn fields reliably.Reduce manual work
No more switching tabs to enrich leads one by one.Build workflows that don’t break
Data stays consistent as systems scale.
Example use cases
- Enrich inbound leads before they hit sales
- Keep Easy Redmine records complete without manual edits
- Add firmographic data for segmentation and scoring
- Maintain CRM hygiene as lead volume grows
What you need to run this workflow
- Easy Redmine API access
- Lusha API access
- n8n instance (cloud or self-hosted)
Optional improvements include:
- Filtering only leads missing key fields
- Adding error notifications
- Handling rate limits for larger lead volumes
Why this approach works
This workflow treats Lusha as a data layer, not a lookup tool.
Instead of enriching once and hoping the data stays relevant, enrichment becomes part of an ongoing system — running quietly in the background, supporting GTM workflows that depend on accuracy and timing.
That’s the difference between enrichment as a task and enrichment as infrastructure.
Try it yourself
You can import this workflow directly from n8n and adapt it to your Easy Redmine setup.
Once it’s live, enrichment becomes automatic and your CRM stays aligned with how your GTM system actually runs.
Keep reading:
How Lusha uses job-change signals to re-activate high-intent prospects
Lusha + monday CRM: keep every board enriched with verified data
Waterfall data enrichment: why streaming data beats static stacking
FAQ
Easy Redmine lead enrichment is the process of automatically adding missing contact and company data—such as phone numbers, job titles, company size, and LinkedIn profiles—to lead records inside Easy Redmine CRM.
Lusha enriches Easy Redmine leads by matching existing lead fields (like email, name, or company) with verified contact and company data from Lusha’s database. Using the Lusha API, enriched fields are then synced back into the CRM automatically.
Yes. Using n8n, you can fully automate Easy Redmine lead enrichment. The workflow runs on a schedule, pulls leads from Easy Redmine, enriches them with Lusha data, and updates the CRM without manual work.
No. Once the workflow is set up, enrichment runs automatically. There’s no need to open Lusha, copy data, or update records by hand.
Common enrichment fields include:
- Phone numbers
- Email addresses
- Job titles and roles
- LinkedIn profiles
- Company size and firmographics
Additional fields can be added depending on your API setup.
The workflow can run on any schedule you choose—daily, hourly, or based on your CRM needs. Many teams run it once per day to keep data fresh without unnecessary API usage.
If Lusha doesn’t return a match, the workflow skips that lead. This prevents partial or incorrect updates and keeps your CRM clean.
Yes. The workflow processes leads in batches and can be adjusted to handle large volumes. You can also add rate-limit handling or filters to enrich only leads missing specific fields.
No deep engineering work is required. You’ll need access to:
- Easy Redmine API credentials
- Lusha API credentials
- An n8n instance
Basic familiarity with APIs or n8n nodes is helpful, but most teams can set this up without developers.
Because GTM workflows depend on data staying accurate over time, not just at the moment of enrichment. Lusha is designed to support ongoing automation—keeping CRM records aligned with real-world changes as systems continue to run.
