Bring signed orders into the pipeline on schedule
A recurring review can catch signed order agreements that were not turned into deals during a busy week, then report missing details for follow-up.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
When deal creation depends on memory, signed orders can be absent from pipeline reviews and forecasts.
- Catch pipeline gaps on a regular cadence
- Reduce manual document review
- Make missing deal details visible
Setup
Build it in a few focused steps.
- 1Connect Boloforms and HubSpot once in Notis.
- 2Create an automation and describe which recent signed orders should become deals.
- 3Pick a recurring schedule trigger and define the lookback window in your instruction.
- 4Choose a report channel and test using one signed order with valid pipeline details.
Questions about this workflow
Will it create duplicate deals on each run?
Tell Notis how to identify orders already processed using details available to the workflow, and test that behavior. The listed HubSpot action creates deals and does not describe a deduplication operation.
What if an order lacks a pipeline or stage?
Have Notis report it for review rather than creating a deal with guessed pipeline details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Boloforms to Hubspot. A trigger fires from one place; an action lands in another.
Boloforms 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.
Boloforms 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.