Surface possible risks when a deal changes stage
Use your own risk signals to spot deal changes that deserve a closer look.
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
Potential deal risks are easy to miss when pipeline updates arrive without a consistent review.
- Apply founder-defined risk signals consistently.
- Distinguish observed evidence from a possible concern.
- Identify follow-up questions when the event lacks context.
Setup
Build it in a few focused steps.
- 1Connect HubSpot and Codeinterpreter once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Tell Notis your risk signals and ask it to review each stage update, showing evidence, uncertainty, and useful questions.
- 4Choose Deal Stage Updated as the trigger and select a report channel.
- 5Test with one real deal update and check the review against what you know.
Questions about this workflow
Does this predict whether a deal will be lost?
No. It flags possible concerns against criteria you provide and available event details; it does not establish an outcome.
What if stage updates do not include enough context?
The report should name what is missing and offer questions to investigate rather than make up a risk explanation.
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.