Move Cardly campaign responders into HubSpot
When a Cardly response arrives, let Notis create a HubSpot contact from the details in the request.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Campaign responses can sit outside your CRM while you switch between Cardly and HubSpot to enter each person manually.
- Capture campaign responders in your CRM promptly.
- Reduce manual contact entry and context switching.
- Keep a clear starting point for follow-up.
Setup
Build it in a few focused steps.
- 1Connect Cardly and HubSpot once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe that each incoming Cardly response should create a HubSpot contact, using only details present in the request.
- 4Pick the notis_webhook trigger and choose where run reports should go.
- 5Test with one real response request and check the resulting HubSpot contact.
Questions about this workflow
Does Cardly provide a trigger event for this workflow?
No. Start it with a Notis webhook, which runs when an HTTP request arrives.
What information can Notis use to create the contact?
Notis can use the details included in the incoming request. If a required detail is missing, supply it in the request or ask Notis to skip creating that contact.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cardly to Hubspot. A trigger fires from one place; an action lands in another.
Cardly 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.
Cardly 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.