Factori People data enrichment community node for n8n enables users to enrich People data at scale directly within their n8n automation workflows.

By integrating Factori's data enrichment capabilities into n8n, teams can apply multi-dimensional filters and generate structured output, either as individual records or in bulk, without writing custom code.

Prerequisites

Before proceeding with the installation, ensure the following requirements are met:

An active n8n account (cloud or self-hosted)
Access to n8n Settings with permissions to install community nodes
Sign in to your Factori account to get your API key generated

Installing the People Data Enrichment Community Node

The Factori People data enrichment node is distributed as a community node and must be installed through n8n's community node manager. Follow the steps below:

Step 1 — Open Community Node Settings

Log in to your n8n account.
Navigate to Settings from the left-hand sidebar.
Select Community Nodes from the Settings menu.

Step 2 — Install the Factori Node

Click Install on the Community Nodes page.
In the search field, enter n8n-nodes-factori (the official Factori community node package name).
Click Install and wait for the installation to complete.
Once successfully installed, the Factori People data enrichment node will appear in the confirmation list.

Step 3 — Verify the Node in the Gallery

Navigate to your workflow canvas (create a new blank canvas if needed).
Click the + Add Node button or press Tab to open the node gallery.
Search for Factori in the search bar.
The Factori People data enrichment node should appear in the results. Click on it to open the node configuration panel

Step 4 — Generate a Factori API Key

Authentication with the Factori platform is handled via an API key. You must generate this key from the Factori Console.

Access the Factori Console

Visit the Factori Console at console.factori.io and sign up or log in to your account.
Navigate to the API Keys section within your account settings.
Click Generate API Key.

Once the API key has been generated, copy and store the key securely, once pasted into the Factori People data enrichment node in n8n, you will be all set to execute your workflows.

Filters reference

You can apply one or more of the following filters to narrow down results. All filters are optional; however, providing at least one filter is required to execute the node.

Filter	Type	Description	Example value
Name	String	Full or partial name of the person	Jane Smith
Email address	String	Professional or personal email address	[email protected]
Company/ Organisation.	String	Company or organisation the person works at	Acme Corporation
Job Title/ Role	String	Current job title or role	Head of Engineering
Location	String	City, state, or country	San Francisco, CA
LinkedIn URL	String	Full LinkedIn profile URL	linkedin.com/in/janesmith

Enriching People Data

With authentication configured, the Factori People data enrichment node is ready to enrich People data within your n8n workflows.

You can apply one or more filters — Name, Email Address, Company / Organization, Job Title / Role, Location, or LinkedIn URL, to get more refined results as per your business needs.

Once your filters are set, choose Single Output for a targeted one-record result, or Multiple Output to retrieve all matching records, then click on Execute Node.

Review the output in the node's output panel. The enriched data will be available as structured JSON for downstream nodes in the workflow.

Output Schema

The node returns enriched records as structured JSON. Each record contains the following feilds-

Sample output:

{ "people_id": "a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0", "first_name": "jane", "last_name": "doe", "age": 32, "gender": "Female", "date_of_birth": { "year": 1993, "month": 6, "day": 21 }, "social": { "linkedin_url": "https://www.linkedin.com/in/janedoe", "twitter_url": "twitter.com/janedoe", "facebook_url": "facebook.com/janedoe" }, "emails": { "personal": [ { "email_address": "[email protected]", "email_domain": "gmail.com", "email_md5": "abcdef1234567890abcdef1234567890", "email_sha1": "aabbccddeeff00112233445566778899aabbccdd", "email_sha2": "1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef" } ], "work": [ { "email_address": "[email protected]", "email_domain": "acmecorp.com", "email_md5": "1234567890abcdef1234567890abcdef", "email_sha1": "ffeeddccbbaa99887766554433221100ffeeddcc", "email_sha2": "abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890" } ] }, "phone": [ { "phone_number": "4155550192", "phone_number_sha1": "aabbccddeeff00112233445566778899aabbccdd", "phone_number_sha2": "1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef", "phone_number_md5": "abcdef1234567890abcdef1234567890", "is_cellphone": true, "is_landline": false, "is_workphone": false } ], "address": { "full_address": "742 evergreen terrace", "city": "austin", "state": "Texas", "zip": "73301", "zip4": "1234", "delivery_point_bar_code": "101", "carrier_route": "r001", "fips_state_code": "48", "county_name": "travis", "latitude": 30.267153, "longitude": -97.743057, "metropolitan_statistical_area": "1922", "core_based_statistical_area": "12420", "census_tract": "001100", "census_block_group": "1000-1999", "census_block": "1010", "primary_address": "742 evergreen terrace", "street": "evergreen", "address_suffix": "terrace", "address_abrev": "austin", "address_type": "Street or Residential", "fips_county_code": "453" }, "education": { "education_level": "Completed College", "education_history": [ { "school": "University of Texas at Austin", "degrees": [ "Bachelor of Science (BS)", "Computer Science" ] } ] }, "employment": { "employee_title": "product manager", "employee_level": "senior", "employee_job_function": "product", "recent_job_change": true, "skills": [ "product management", "agile", "roadmapping", "data analysis", "stakeholder management", "jira", "sql" ], "work_experience": [ { "end_year": "2019", "start_year": "2017", "title": "Associate Product Manager", "company": "Amazon" }, { "end_year": "2022", "start_year": "2019", "title": "Product Manager", "company": "Stripe" } ] }, "company": { "company_id": "f1e2d3c4b5a6f7e8d9c0b1a2f3e4d5c6b7a8f9e0", "company_name": "acme corp", "office_address": "500 main street", "office_city": "austin", "office_state": "tx", "company_linkedinurl": "https://www.linkedin.com/company/acme-corp/", "company_website": "acmecorp.com", "company_industry": "technology", "company_num_employees": "1001-5000", "company_sic_code2_description": "computer programming services", "company_revenue_range": "100m-500m", "company_hq_address": "500 main street", "company_hq_city": "austin", "company_hq_state": "tx", "company_naics_code": "541511", "company_sic_code2": "7371", "company_hq_zip5": "73301" }, "financial": { "income": { "net_worth": "$50000 - $99999" }, "credit_information": { "credit_rating": "Between 700-749" }, "mortgage": { "mortgage_loan2_lender": "wells fargo" } }, "household": { "household_id": "b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0", "dwell_type": "SFDU (Single Family Dwelling Unit)", "household_income": "$95000 - $104999", "marital_status": "Single", "homeowner": "Renter", "generations": "1 Generation - 1 Adult", "census_median_household_income": "$72000", "household_size": 2, "number_of_kids": 0, "children": [], "adults": [ "25-34y Female" ], "length_of_residence": 3 }, "property": { "home_market_value": 320000, "property_with_pool": false, "property_with_ac": "CENTRAL", "census_median_home_value": 410000, "property_build_year": 2005 }, "hobby": [ "avid_readers", "cooking_hobby", "fitness_hobby" ], "buyer": [ "electronics_buyer", "books_buyer", "health_buyer" ], "interests": [ "interest_in_technology", "interest_in_fitness", "interest_in_travel" ] }

Troubleshooting

In cases where an API request encounters an error, the Factori API provides informative error messages and corresponding status codes. The error handling section of the documentation explains the possible error scenarios, their meanings, and recommended approaches for error handling and troubleshooting.

HTTP Error codes

Error Name	Status Code	Description
Bad Request	400	The request body or parameters are incorrect, malformed, or fail validation.
Unauthorized	401	Authentication failed (e.g., invalid API key ).
Insufficient credits	402	Insufficient credits to process the request.
Forbidden	403	Authentication is valid, but the user/app does not have permission to access this resource.
Conflict	409	A conflicting operation is in progress (e.g., unlock in progress while another unlock request is made).
Too Many Requests	429	Allowed rate limit exceeded
Internal Server Error	500	A general server-side error occurred that does not fit other error categories.

Resources

n8n community nodes documentation