Create HubSpot deals from BotPenguin sales conversations
Capture a sales opportunity in your pipeline without switching from the conversation to retype it.
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
Sales intent in a chat is easy to miss when deal creation depends on someone remembering it later.
- Record sales opportunities in the CRM promptly
- Reduce missed pipeline updates
- Use the deal details provided with the incoming request
Setup
Build it in a few focused steps.
- 1Connect BotPenguin and HubSpot once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for sales opportunities.
- 3Tell Notis to create a HubSpot deal from each webhook payload that contains sales intent and the details needed for a deal.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real opportunity payload and valid pipeline details.
Questions about this workflow
Will the workflow decide the deal stage for me?
Notis can use a stage included in the payload or described in your instruction. The stage and pipeline must be valid in your HubSpot account.
What if the webhook payload lacks deal details?
Provide the missing details in the payload or your instruction before relying on the workflow to create deals.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BotPenguin to Hubspot. A trigger fires from one place; an action lands in another.
BotPenguin 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.
BotPenguin 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.