Review pending transactions for qualified opportunities
Set a regular review so potential opportunities do not depend on remembering to revisit transaction activity manually.
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
Pending transactions can change quickly, while founders may not have a reliable moment to scan for commercial signals.
- Review the available activity on a predictable cadence
- Create deals only when a defined opportunity is present
- Surface missing pipeline details in run reports
Setup
Build it in a few focused steps.
- 1Connect Blocknative and HubSpot once in Notis.
- 2Create an automation in the portal or tell Notis in plain language.
- 3Describe the opportunity criteria and the valid HubSpot pipeline and stage to use.
- 4Choose a recurring schedule and where run reports should go.
- 5Test with one real review of available pending-transaction data.
Questions about this workflow
Can a scheduled review see all past transaction history?
Only data available through the connected Blocknative access can be reviewed. Specify any needed time window in the prompt.
What happens if no opportunity qualifies?
Tell Notis to create no deal and report that no qualifying opportunity was found.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Blocknative to Hubspot. A trigger fires from one place; an action lands in another.
Blocknative 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.
Blocknative 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.