Make expansion activity visible in the pipeline
Ask Notis to recognize your chosen expansion signal and create a HubSpot deal when the required details are present.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create batch of deals
Creates multiple deals in hubspot crm; ensure any associated object ids, deal stages, and pipeline ids specified are valid and exist within the hubspot account.
Why this helps
Expansion signals can be buried in billing changes while the sales team has no deal to follow up on.
- Surface expansion signals in the sales pipeline
- Reduce manual deal entry
- Make follow-up easier to coordinate
Setup
Build it in a few focused steps.
- 1Connect Billsby and HubSpot once in the Notis portal.
- 2Create an automation for the expansion signal you want to track.
- 3Describe the qualifying change and the required deal details.
- 4Choose the Notis webhook trigger and where run reports should go.
- 5Test with one real expansion event and valid pipeline details.
Questions about this workflow
Can Notis determine whether a change is expansion?
Yes, if the available Billsby data supports the rule you describe. State what should count as expansion.
What if a pipeline or stage is missing?
Provide valid pipeline and stage details in the instruction or ensure they are available from the connected account.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Billsby to Hubspot. A trigger fires from one place; an action lands in another.
Billsby 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.
Billsby 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.