Review deal stage timing against your baseline
See whether a deal's stage timing stands out using data and benchmarks you choose.
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
It is difficult to spot unusually slow movement without calculating timing and agreeing on what counts as typical.
- Calculate a duration when the required timestamps are available.
- Compare timing with a baseline you provide.
- Make missing timestamp or benchmark data explicit.
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 which timestamps to use and provide a baseline; ask it to report missing data rather than infer it.
- 4Select Deal Stage Updated as the trigger and choose a report channel.
- 5Test with one real update that includes the required timestamps and review the calculation.
Questions about this workflow
Does the stage update event always include a stage entry timestamp?
The workflow can only calculate elapsed time if the needed timestamps are available. If they are absent, it should report that limitation.
Where does the comparison baseline come from?
You provide the baseline, such as a duration or dataset. The automation should not claim a typical duration without a source.
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.