Keep product follow-up requests attached to a contact
Give explicit requests for a demo, update, or conversation a clear next step in HubSpot.
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
Follow-up requests made to an AI agent can be overlooked when they do not reach the contact list.
- Catch direct requests for a demo or product follow-up.
- Avoid adding people whose identity is unclear.
- Keep requested next steps visible to the team.
Setup
Build it in a few focused steps.
- 1Connect BotMape and HubSpot once in the Notis portal.
- 2Create an automation in Automations, New Automation, for product follow-up requests.
- 3Ask Notis in one instruction to review recent conversations and create contacts only for people who explicitly request follow-up and provide sufficient identifying details.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real follow-up request and review the contact.
Questions about this workflow
Does a product question count as a follow-up request?
Set the instruction to require an explicit request, such as asking for a demo or asking the team to contact them.
What if the person has already contacted us?
The available action creates contacts. If deduplication is important, specify the available identifying details and review outcomes before relying on it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BotMape to Hubspot. A trigger fires from one place; an action lands in another.
BotMape 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.
BotMape 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.