clearbit and hubspot and update company hubspot
Configured with Calendly Trigger, Clearbit, Filter, Hubspot. Review the connections and setup before adapting this template.
Node categories in this workflow
- Routing
- Integration
- Trigger
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| if company does not exist on CRM | Routing | If | See node parameters |
| Enrich company | Integration | Clearbit | See node parameters |
| Create company | Integration | Hubspot | company |
| Upsert contact | Integration | Hubspot | See node parameters |
| Update company | Integration | Hubspot | company / update |
| Contact not found, do nothing | Routing | No Op | See node parameters |
| Enrich email | Integration | Clearbit | person |
| Filter out personal emails | Routing | Filter | See node parameters |
| Search company | Integration | Hubspot | company / searchByDomain |
| Upsert lead | Integration | Hubspot | See node parameters |
| If person has a company | Routing | If | See node parameters |
| Calendly Trigger | Trigger | Calendly Trigger | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
calendlyApiclearbitApihubspotOAuth2Api
Workflow notes
Setup
Setup
- Add
Clearbit,Hubspot, andCalendlycredentials - Click on
Test workflow - Book meeting on Calendly so the event starts the workflow
Sticky Note1
Replace this node with your booking tool of choice
Sticky Note2
Map all data found about the company that you interested in
Sticky Note3
Make sure to map the email field from the data your booking tool provides
Enrich company
Enrich company
Enrich email
Enrich email
clearbit and hubspot and update company hubspot
clearbit and hubspot and update company hubspot
Purpose and structure
This folder contains the clearbit and hubspot and update company hubspot workflow. Its executable nodes use calendlyTrigger, clearbit, filter, hubspot, if, noOp. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Calendly Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Calendly/0430_Calendly_Filter_Create_Triggered.json MIT; preserve source notices.