Check the handoff when a task changes section
A section change often signals a handoff. Have Notis compare the task details with the transition checklist you provide and flag missing information.
Trigger
Task Moved to Section
Triggers when a task is moved to a section in a project.
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
A task can move forward while the details needed for its next stage are still unclear.
- Review transitions against your own checklist
- Surface missing information at the handoff
- Keep process assumptions explicit
Setup
Build it in a few focused steps.
- 1Connect Asana and Codeinterpreter once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis what transition checklist to apply and to report only gaps visible from the task details it receives.
- 4Pick the Asana Task Moved to Section trigger and choose where run reports go.
- 5Test with one real task transition and refine your checklist.
Questions about this workflow
Can it use a different checklist for each section?
You can describe the rules in the instruction, but only rely on section and task information actually available to the automation.
Does it move tasks or change their status?
No. The selected action analyzes information with Python and returns a report.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Asana to Codeinterpreter. A trigger fires from one place; an action lands in another.
Asana 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.
Attachment Added to Task
Triggers when an attachment is added to a task.
Get File
Get a file from the sandbox and returns the file. the files should be read from /home/user folder.
New Comment on Task
Triggers when a comment is added to a task in a project.
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.
New Task Created
Triggers when a new task is created in a project.
Upload File
Upload a file to the sandbox environment. the files should be uploaded to the /home/user folder.
Task Moved to Section
Triggers when a task is moved to a section in a project.
Tag Added to Task
Triggers when a tag is added to a task. Note: Asana's event structure is inverted for tag events — the resource is the task and the parent is the tag. So parent.gid gives the tag GID.
Task Updated
Triggers when a task is updated in a project.
Connect any two apps with Notis in the middle.
Asana 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.