Capture opted-in wallet leads from mempool alerts
When a monitored transaction alert includes contact details the prospect chose to share, ask Notis to create or check the corresponding HubSpot contact.
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
Potential leads in transaction alerts are easy to miss when they have to be copied into a CRM by hand.
- Capture supplied prospect details while the alert is in context
- Avoid creating a contact when the details are incomplete
- Keep transaction monitoring separate from manual CRM entry
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 how to create or check a contact only when an alert includes prospect details the person opted to share.
- 4Choose a webhook trigger and where run reports should go.
- 5Test with one real alert containing suitable contact details.
Questions about this workflow
Will a wallet address alone become a contact?
No. The instruction should require contact details that identify a person and were supplied for CRM use; a wallet address alone is not enough.
Does this send the contact an email?
No. The selected action creates contact records and does not send an email.
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.