Review patterns in your sent email subjects
Turn sent subject lines into a compact review of recurring wording, useful for keeping outreach and follow-ups clear.
Trigger
Email Sent
Triggers when a Gmail message is sent by the authenticated user. It polls the 'SENT' label and emits metadata including sender, recipients, subject, timestamp, and thread ID.
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
Finding repeated or unclear subject wording across sent email takes a lot of manual scanning.
- Review subject wording in a consistent way.
- Get a structured Python output for the triggering message or supplied history.
- Avoid claiming trends without a sufficient set of subjects.
Setup
Build it in a few focused steps.
- 1Connect Gmail and Codeinterpreter once in the Notis portal.
- 2Create an automation with a name for the subject review.
- 3Tell Notis in one instruction how to assess the subject and whether historical subjects will be supplied.
- 4Choose the Email Sent trigger and select a run report destination.
- 5Test with one real sent email and confirm what message history is available.
Questions about this workflow
Can one sent event reveal long-term subject patterns?
A single event provides only its own metadata. Supply a history of subjects if you want a broader pattern summary.
Which subject information is available on the trigger?
The listed sent event emits the message subject along with sender, recipients, timestamp, and thread ID.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Gmail to Codeinterpreter. A trigger fires from one place; an action lands in another.
Gmail 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.
Email Sent
Triggers when a Gmail message is sent by the authenticated user. It polls the 'SENT' label and emits metadata including sender, recipients, subject, timestamp, and thread ID.
Get File
Get a file from the sandbox and returns the file. the files should be read from /home/user folder.
New Gmail Message Received Trigger
Triggers when a new message is received in Gmail.
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.
Gmail 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.