Keep recurring protocol feedback visible
Give each review cycle a clear record of the feedback people actually shared about the protocol.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Create batch of feedback submissions
Creates a batch of feedback submissions in hubspot, ideal for bulk imports; all property names, `associationtypeid`s, and association `to id`s must reference existing entities in hubspot.
Why this helps
Feedback collected during recurring reviews can disappear before the next planning discussion.
- Process collected responses on a recurring cadence.
- Create HubSpot feedback submissions for team review.
- Retain the protocol and review-cycle context supplied by your team.
Setup
Build it in a few focused steps.
- 1Connect Alchemy and HubSpot once in the Notis portal.
- 2Create an automation and specify the protocol review cycle and feedback source.
- 3Tell Notis to create feedback submissions only from responses actually collected for that cycle.
- 4Choose a recurring schedule and report channel.
- 5Test with one real response and valid HubSpot association details.
Questions about this workflow
Does Alchemy collect user feedback?
The workflow needs a feedback source you specify. Alchemy can provide blockchain context, but the response itself must be collected elsewhere.
Will it create a submission when there are no responses?
No. The instruction should have Notis report an empty review rather than create placeholder feedback.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Alchemy to Hubspot. A trigger fires from one place; an action lands in another.
Alchemy 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.
Alchemy 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.