Analyze ClickUp time tracking changes
Understand effort patterns as time is recorded.
Trigger
Task Time Tracked Updated
Triggers when a time-tracking interval is created, edited, or deleted on a task. Fires once per interval-change. Reads ClickUp's top-level `data.description` for the lifecycle action and `data.interval_id` for the correlation key — these are unique to time-tracking events and are present even on Deleted (where `history_items` is empty).
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
Time entries accumulate without showing where effort is really going.
- Analyzes each interval change
- Reveals effort patterns
- Supports better planning
Setup
Build it in a few focused steps.
- 1Connect ClickUp and Code Interpreter once in Notis.
- 2Create an automation describing the time analysis outcome.
- 3Pick the ClickUp Task Time Tracked Updated trigger.
- 4Choose where run reports should go.
- 5Test with one real interval change.
Questions about this workflow
Does it handle deleted intervals?
Yes. The trigger fires for created, edited, and deleted intervals.
Can it use the interval description?
Yes, the action can use the event data available to the automation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Clickup to Codeinterpreter. A trigger fires from one place; an action lands in another.
Clickup 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.
Folder Created
Triggers when a new Folder is created.
Get File
Get a file from the sandbox and returns the file. the files should be read from /home/user folder.
Folder Deleted
Triggers when a Folder is deleted.
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.
Folder Updated
Triggers when a Folder is updated (renamed, content edited, etc.).
Upload File
Upload a file to the sandbox environment. the files should be uploaded to the /home/user folder.
List Created
Triggers when a new List is created.
List Deleted
Triggers when a List is deleted.
List Updated
Triggers when a List is updated (renamed, content edited, etc.).
Connect any two apps with Notis in the middle.
Clickup 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.