Keep lead follow-up email activity in HubSpot
Submit follow-up activity details to Notis. It checks the lead email with Abstract and records the supplied activity in HubSpot for valid addresses.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create a batch of emails
Creates multiple email objects for record-keeping (does not send emails) within hubspot crm in a single batch, allowing properties and associations to other crm objects to be set for each email.
Why this helps
Follow-up context gets lost when email activity details stay outside the CRM record.
- Validate the lead email before recording follow-up activity.
- Keep supplied email activity details in HubSpot.
- Reduce manual CRM record keeping after outreach.
Setup
Build it in a few focused steps.
- 1Connect Abstract and HubSpot once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Describe in one instruction how to validate the lead email with Abstract and create a HubSpot email record using the follow-up activity details in the request.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real follow-up activity.
Questions about this workflow
Will this send the follow-up email?
No. The HubSpot action creates an email engagement record for record keeping; it does not send an email.
What information should the request include?
Include the email activity properties and any valid HubSpot associations required for the record.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Abstract to Hubspot. A trigger fires from one place; an action lands in another.
Abstract 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.
Abstract 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.