Keep Builder.io form leads moving into HubSpot
Send each new Builder.io form submission to Notis and create a HubSpot contact with the details provided.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create batch of contacts
Creates up to 100 new contact records in hubspot crm, optionally associating them with existing crm objects; ensure associated object ids are valid.
Why this helps
Form leads can sit in Builder.io while follow-up waits on a manual copy into HubSpot.
- Reduce manual lead entry
- Keep submission details together in HubSpot
- Make new inquiries easier to follow up
Setup
Build it in a few focused steps.
- 1Connect Builder.io and HubSpot once in Notis.
- 2Create an automation in Notis and describe the contact creation outcome in one instruction.
- 3Choose a Notis webhook and send it one real Builder.io form submission as a test.
- 4Choose where run reports should go.
- 5Test with one real example and check the resulting HubSpot contact.
Questions about this workflow
Does Builder.io provide a trigger event here?
No. This workflow starts from a Notis webhook that receives a request containing the submission details.
What if a submission does not include an email address?
Tell Notis how to handle incomplete submissions in the instruction, such as reporting them without creating a contact.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Builder.io to Hubspot. A trigger fires from one place; an action lands in another.
Builder.io triggers
Hubspot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add asset association
Associates an existing asset ('form', 'object list', or 'external web url') with a specified hubspot marketing campaign.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add token to event template
Adds a new custom data token to an existing event template for a specified hubspot application, optionally populating a crm object property if objectpropertyname is provided.
Archive email
Archives the hubspot email specified by `emailid` by moving it to the recycling bin, making it inaccessible unless restored.
Archive a batch of emails by ID
Archives multiple hubspot crm emails by id; ids must exist as archiving is irreversible.
Archive a batch of quotes by id
Archives a batch of existing, non-archived quotes by their ids; this action is irreversible and useful for managing outdated or irrelevant quotes.
Archive batch of companies by id
Archives a batch of companies by their unique ids; targeted companies must exist, not be previously archived, and this api operation is irreversible.
Archive batch of contacts by id
Archives a batch of existing contacts by their hubspot crm ids, rendering them inactive; this action is irreversible via the api and requires manual restoration or a separate unarchive endpoint.
Archive batch of deals by id
Archives a batch of existing deals by their unique hubspot ids, removing them from active views and reports (soft delete); archived deals may be restorable.
Connect any two apps with Notis in the middle.
Builder.io and Hubspot, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Hubspot.