Turn customer signals into contact records
Let Notis review connected-device activity on a schedule and capture identifiable people as HubSpot contacts when the source data supports it.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Customer signals can prompt a follow-up, but the person behind the signal may never be entered into the CRM.
- Review relevant activity on a routine schedule
- Create contacts only when contact details are available
- Reduce CRM entry overhead
Setup
Build it in a few focused steps.
- 1Connect Adafruit IO and HubSpot once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to review the relevant activity and create a contact only when it contains an identifiable person and required contact details.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real example that includes valid contact details.
Questions about this workflow
Can a sensor reading identify a person by itself?
No. The source data must include identifying information and the details needed to create the contact.
What happens when the data has no contact details?
The instruction should tell Notis to skip contact creation and report that the required details are missing.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Adafruit IO to Hubspot. A trigger fires from one place; an action lands in another.
Adafruit 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.
Adafruit 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.