Bring Canny feedback into HubSpot
Capture product feedback in HubSpot as it arrives, so customer context stays close to the work.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 scattered across tools is easy to overlook when reviewing customer accounts.
- Keep feedback available in HubSpot for follow-up and review.
- Reduce manual copying between product feedback and CRM tools.
- Give teams a central place to look for customer feedback.
Setup
Build it in a few focused steps.
- 1Connect Canny and HubSpot once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to create a HubSpot feedback submission for each new Canny feedback item, preserving its available context.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real Canny feedback item and review the HubSpot result.
Questions about this workflow
What starts this automation?
A webhook request to Notis starts it. Canny does not provide a listed trigger event here, so configure an available Canny integration or external sender to send the request.
Does this create a Canny post?
No. It creates a HubSpot feedback submission using the available information in the incoming request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Canny to Hubspot. A trigger fires from one place; an action lands in another.
Canny 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.
Canny 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.