OpenRuna
Sign in
← Workflows

Property Lead Contact Enrichment from CRM

16 nodes · manual, schedule, httpRequest, spreadsheetFile, hubspot, emailSend

Engine
n8n
Nodes
16
Trigger
scheduled/triggered
Source file
1628_Emailsend_Code_Automation_Webhook.json

Workflow flow

IntegrationsManualScheduleHTTPSpreadsheetFileHubSpotEmailSendSetCode
100%
TRIGGER

When clicking "Execute Workflow"

Manual

TRIGGER

Daily Schedule

Schedule

Configure Search Parameters

Set

Search Properties API

HTTP

Filter Property Results

Code

Get Owner Contact Info

HTTP

Format Lead Data

Code

Create Excel Spreadsheet

SpreadsheetFile

Push to CRM

HubSpot

Summarize Results

Code

Email Notification

EmailSend

11 steps · flows top to bottom, branches left to right

Browse by integration

Browse all integrations →

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Property Lead Contact Enrichment from CRM is a free n8n workflow on OpenRuna — 16 nodes connecting manual, schedule, httpRequest, spreadsheetFile, hubspot, emailSend. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

"Property Lead Contact Enrichment from CRM" automates a manual-to-schedule flow in n8n across 16 nodes. 16 nodes · manual, schedule, httpRequest, spreadsheetFile, hubspot, emailSend A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Share it with your team as a documented reference for scheduled/triggered automations in the manual stack.
  • Study how data moves from manual to schedule before building your own variant.
  • Use it as a starting template when wiring manual, schedule, httpRequest, spreadsheetFile, hubspot, emailSend — adjust node parameters to your accounts and record IDs.
  • Import "Property Lead Contact Enrichment from CRM" into n8n, reconnect credentials for manual, schedule, httpRequest, spreadsheetFile, hubspot, emailSend, and run the same automation in your own workspace.

Example output

Imported into n8n, "Property Lead Contact Enrichment from CRM" exposes 16 configured nodes. Trigger type: scheduled/triggered. Integrations: manual, schedule, httpRequest, spreadsheetFile, hubspot, emailSend. Reconnect the manual credential first, then walk the remaining nodes top to bottom. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Paste the exported JSON for "Property Lead Contact Enrichment from CRM" into Claude and ask it to explain each of the 16 nodes. Claude is good at suggesting credential mappings for manual, schedule, httpRequest, spreadsheetFile, hubspot, emailSend, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "Property Lead Contact Enrichment from CRM" to your accounts — which manual, schedule, httpRequest, spreadsheetFile, hubspot, emailSend credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 16 nodes.

Frequently asked questions

How do I import "Property Lead Contact Enrichment from CRM" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Property Lead Contact Enrichment from CRM" use?
It uses: manual, schedule, httpRequest, spreadsheetFile, hubspot, emailSend. The flow diagram above shows how each service connects across the 16 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own manual and schedule credentials in n8n after import.
What trigger type does "Property Lead Contact Enrichment from CRM" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Property Lead Contact Enrichment from CRM" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for manual, schedule, httpRequest, spreadsheetFile, hubspot, emailSend.

Related resources