Give each CDR order a place in your pipeline
When an order request arrives, have Notis prepare a HubSpot deal that makes the next sales or delivery follow-up easier to see.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create batch of deals
Creates multiple deals in hubspot crm; ensure any associated object ids, deal stages, and pipeline ids specified are valid and exist within the hubspot account.
Why this helps
A purchase can be confirmed in one system while the people coordinating next steps rely on pipeline notes or memory.
- Give an order a visible record in the deal pipeline.
- Keep purchase coordination tied to ongoing sales work.
- Reduce the need to recreate order context by hand.
Setup
Build it in a few focused steps.
- 1Connect Cdr Platform and HubSpot once in the Notis portal.
- 2Create an automation in Automations, or ask Notis in plain language.
- 3Tell Notis in one instruction to create a HubSpot deal using the order details provided with the webhook.
- 4Pick the webhook trigger and select a report channel.
- 5Test using one real order request and review the resulting deal.
Questions about this workflow
Can this choose a deal stage automatically?
Notis can act on the information available in the request and your instruction. Use a stage and pipeline that exist in your HubSpot account; the action requires valid pipeline and stage values if those are specified.
Does Cdr Platform send the trigger directly?
No Cdr Platform trigger events are listed here. A Notis webhook must receive an HTTP request from your order process or another supported sender.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cdr platform to Hubspot. A trigger fires from one place; an action lands in another.
Cdr platform 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.
Cdr platform 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.