Block 1 - if company does not exist on CRM
- Type / Role
- n8n-nodes-base.if - if
- Config choices
- Version 2
This workflow is provided as-is. Please review and test before using in production.
Use Case Whenever someone shows interest in your offerings by subscribing to a list in ConvertKit it could be a potential new customer. Typically you need to gather more detailed information about ...
n8n-nodes-base.if, n8n-nodes-base.stickynote, n8n-nodes-base.clearbit, n8n-nodes-base.hubspot, n8n-nodes-base.convertkittrigger, n8n-nodes-base.filter, n8n-nodes-base.noop
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Ricardo Espinozaas.
Original n8n.io sourceWhenever someone shows interest in your offerings by subscribing to a list in ConvertKit it could be a potential new customer. Typically you need to gather more detailed information about them (data enrichment) and finally update their profile in your CRM system to better manage and nurture your relationship with them. This workflow does this all for you!
The workflow runs every time a user is subscribed to a ConvertKit list. It then filters out personal emails, before enriching the email. If the email is attached to a company it enriches the company and upserts it in your Hubspot CRM.
Clearbit, Hubspot, and ConvertKit credentials.Test workflow.ConvertKit to trigger the workflow.Be aware that you can adapt this workflow to work with your enrichment tool, CRM, and email automation tool of choice.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Enrich lead captured by ConvertKit and save it in Hubspot |
|---|---|
| Complexity | intermediate |
| Nodes | 16 |
| Categories | Lead Generation |
| Author | Ricardo Espinozaas |
| Published | 23 Feb 2024 |
Use the JSON export at /data/workflows/2130/2130.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Use Case Whenever someone shows interest in your offerings by subscribing to a list in ConvertKit it could be a potential new customer. Typically you need to gather more detailed information about ...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Lead Generation use case.