Suggest a segment for each new HubSpot contact
Get a consistent starting point for organizing new contacts without hiding uncertainty.
Trigger
Contact Created Trigger
Contact Created Trigger
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
Sorting new contacts by hand takes attention, and inconsistent judgments make lists harder to use.
- Apply your own segment definitions consistently.
- Explain which available details informed each suggestion.
- Flag contacts that do not have enough information for a confident suggestion.
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 your segment definitions and ask it to suggest one from each new contact's available details, with a reason and uncertainty note.
- 4Select Contact Created as the trigger and choose where reports go.
- 5Test with a real contact and review the suggestion against your criteria.
Questions about this workflow
Will this update a segment field in HubSpot?
This workflow returns a suggestion in its report. It does not write to a contact field.
Where do the segment rules come from?
Provide your definitions in the instruction. The automation should not invent business-specific segments.
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.