The flow
Starts it 2Logic 12Service 7
The steps in the order they run, from what starts it.
- 1When Executed by Another WorkflowExecute Workflow triggerStarts it
- 2ProspectPro Trigger ExampleProspectpro triggerStarts it
- 3Get prospectProspectproService
- 4No Existing Errors?IfLogic
- 5return { result: false };CodeLogic
- 6Continue?IfLogic
- 7Search Companies by Bedrijfsdata IDHttp RequestService
- 8Set Tag: HubspotSyncFailedCodeLogic
- 9Found by ID?IfLogic
- 10Update Tags: FailProspectproService
- 11Set hsCompanyCodeLogic
- 12Has Domain?IfLogic
- 13Update a companyHubspotService
- 14Search Companies by DomainHttp RequestService
- 15Create a companyHubspotService
- 16Update Successful?IfLogic
- 17Found by Domain?IfLogic
- 18Creation Successful?IfLogic
- 19Set Tag: HubspotSyncedCodeLogic
- 20Update Tags: SuccessProspectproService
- 21return { result: true };CodeLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 21, with 7 branches
- Size
- Large: read it before trusting it with anything live
- Connects to
- HubSpot
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own HubSpot account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Take your time. At 21 steps it is large: read it before trusting it with anything live.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 21 steps before you point it at anything that matters.