Understand each HubSpot deal stage change
Get a compact readout when a deal moves, so the change is easier to interpret and act on.
Trigger
Deal Stage UpdatedTrigger
Deal Stage UpdatedTrigger
Action
Execute Code
Execute python code in a sandbox and return any result, stdout, stderr, and error. use /home/user folder to write/read files. try to not use plt.show() as the code is executed remotely. use files for image/chart output instead.
Why this helps
A stage change can signal progress or a new risk, but the useful context is easy to lose between CRM checks.
- Summarize the stage update details that are available.
- Call out missing context instead of assuming why the deal moved.
- Make pipeline changes easier to review in a report.
Setup
Build it in a few focused steps.
- 1Connect HubSpot and Codeinterpreter once in the Notis portal.
- 2Create a named automation in Automations, New Automation.
- 3Tell Notis to summarize each deal stage update from available details and list any context needed to interpret it.
- 4Select the Deal Stage Updated trigger and choose where run reports should go.
- 5Test with one real stage update and check that the summary sticks to the supplied information.
Questions about this workflow
Can this tell why a deal changed stage?
Only if the reason is present in the details the workflow receives. Otherwise it should identify the reason as unknown.
Does it update the deal?
No. It analyzes the event and returns a report for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Hubspot to Codeinterpreter. A trigger fires from one place; an action lands in another.
Hubspot triggers
Codeinterpreter actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Sandbox
Create a sandbox to execute python code in a jupyter notebook cell. this is useful for agents to communicate, execute code, see output, read files, write files, etc. it's like you own personal computer, but in the cloud. use /home/user folder to write/read files.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Execute Code
Execute python code in a sandbox and return any result, stdout, stderr, and error. use /home/user folder to write/read files. try to not use plt.show() as the code is executed remotely. use files for image/chart output instead.
Contact Created Trigger
Contact Created Trigger
Get File
Get a file from the sandbox and returns the file. the files should be read from /home/user folder.
Deal Stage UpdatedTrigger
Deal Stage UpdatedTrigger
Run Terminal Command
Run a command in the terminal and returns the stdout, stderr, and error code. use /home/user folder to write/read files.
Upload File
Upload a file to the sandbox environment. the files should be uploaded to the /home/user folder.
Connect any two apps with Notis in the middle.
Hubspot and Codeinterpreter, 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 Codeinterpreter.