Understand your email response timing
Use the timestamps you have to see how long replies take and where follow-up may be needed.
Trigger
New Email Received
Trigger for new emails in an AgentMail inbox
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
Without a clear view of response timing, follow-ups can quietly fall through the cracks.
- Calculate timing from supplied message and reply records
- Review response patterns in a compact report
- Spot threads that may need your attention
Setup
Build it in a few focused steps.
- 1Connect Agent mail and Codeinterpreter once in the Notis portal.
- 2Create an automation and name it.
- 3Tell Notis which message and reply timestamps or history to use, and ask it to calculate the response intervals with Python.
- 4Choose Agent mail's New Email Received trigger and select where run reports should go.
- 5Test with a real message and the reply history needed for the calculation.
Questions about this workflow
Can the new-email event alone calculate how long I took to reply?
No. Response timing requires a matching reply timestamp or history. Supply those records or ask only for a report of received message times.
Will it remind me to reply?
This action returns a code execution result. It does not send reminders or change email state.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agent mail to Codeinterpreter. A trigger fires from one place; an action lands in another.
Agent mail 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.
New Email Received
Trigger for new emails in an AgentMail inbox
Get File
Get a file from the sandbox and returns the file. the files should be read from /home/user folder.
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.
Agent mail 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.