Include email history in regular prospect planning
Bring previous HubSpot conversations into the review before planning the next prospecting step.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Read Batch Emails
Retrieves a batch of hubspot email objects by their internal ids or values of a specified unique property, allowing targeted property selection, including historical data.
Why this helps
Prospect planning often overlooks past email context because it lives outside the enrichment table.
- Review known email records as part of prospect planning.
- Surface relevant conversation details before deciding on follow-up.
- Reduce repetitive searches through CRM history.
Setup
Build it in a few focused steps.
- 1Connect Clay and HubSpot to Notis once.
- 2Create an automation that retrieves selected HubSpot email records for IDs available from your Clay prospect list.
- 3Pick a recurring schedule as the trigger.
- 4Choose where run reports should go, then test with one real example.
Questions about this workflow
What identifiers are needed?
Supply the HubSpot email object IDs or a supported unique property for the records you want retrieved.
Can the workflow decide whether to follow up?
It can summarize supplied history and apply criteria you describe, but the decision should rely on information present in the records.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Clay to Hubspot. A trigger fires from one place; an action lands in another.
Clay 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.
Clay 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.