I’ve been leveraging Asana’s Script Actions in the rule builder since it was in beta, and it’s truly saved my butt. Before that, I was relying in a precariously long rule that had about 18 different branches and failed just about every other day.
Script Actions are great if you know how to code, but can be very intimidating if you don’t. I was fortunate enough to have an engineer for a partner who helped me whip up the primary script I needed.
What is Vibe Coding?
Vibe coding is coding for the rest of us. Once you know what it is you are trying to accomplish with your script, you provide your prompt to your fave LLM to start the process. Just like with anything you use AI to assist with, it’s not going to be an immediate success every time. You’ll likely still go through rounds of testing, debugging, and iterating before you’ve got a functioning script.
My Asana Script Vibe Coding Process
With vibe coding, it’s still important to follow your standard AI best practices. The success of your output is highly dependent on the prompt you put in.
Best Practices
DO NOT override or delete your current rule.
Start a new rule for your script action. You will likely need to test a lot.
PAUSE your other rule to ensure you aren’t getting false results
Our Case Study
In the rule below, we are dynamically adding tasks to their corresponding project based on the assignee. In this example, we only have 3 branches, but let’s say I’m replicating this for a team of 20. This approach requires significant upkeep, and holds a high risk of breakage. What happens if I forgot to add someone? What if someone leaves the company?
Initial Prompting
When writing my prompt, I ask myself:
“What is the outcome I’m looking for?”
“What problem am I solving?”
“How would I explain this process to someone, step-by-step?”
It’s helpful to get prescriptive on the steps that need to happen to accomplish the goal to ensure your code is checking the correct things. Often times, my LLM will suggest an alternate approach (in this example, it kept encouraging me to use the basic rule instead of debugging the code), so it’s helpful to provide that context.
I currently have a basic rule in Asana that is requiring too much manual upkeep and keeps breaking. I would like to switch this rule to a Script Action. Can you please help me design an Asana Script that completes the following steps:
1. Identifies the task Assignee
2. Locates the project that contains their name
3. Adds the task to the new project
For testing, I ALWAYS make a new rule and pause the one I am replacing. DO NOT delete or override your current rule.
Building a Script Action Rule
As always, you will begin with your +When trigger. Depending on what kind of rule you are building, you can add +Check If conditions, but for this example I am working around that.
To add a script action to your +Do This, go to external triggers and select run script. This is where you will paste in your code.
Testing Your Script
Once your script is added, run some tests. If the rule fails, you’ll see an error up in the Customize button. From here, I check the log and go back to your LLM.
In this example, it took some time to troubleshoot: me, copy/pasting the error logs; Claude, asking me for additional info and providing revised code. Rinse, repeat.
Debugging Prompts
Knowing how to debug is a critical step if you do not have experience in engineering. But how do you know what you don’t know?
In some cases, the Asana script will require you to locate something called a GID to reference a specific custom field, project, or team. Other times, I’ll uncover that Claude needs to use a different API call than the one it defaulted to.
Because I’ve had these experiences, I have a series of questions I ask when I’m getting repeated failures:
Are you using the tasksApiInstance for this script?
Do you need a GID for a project/custom field/portfolio to execute this code?
Can we simplify this script?
It may seem intimidating, but you’ve got this!
My Final Rule
Our complex, multi-branched rule is now a single step with a functioning script! This script does not rely on custom GIDs, and should be ready to go. Start your own vibe coding journey by debugging this in your workspace with your preferred LLM!
async function run() { let opts = { 'opt_fields': "gid,name,assignee.name,workspace.gid" };
// Fetch the task data tasksApiInstance.getTask(task_gid, opts).then((result) => { log("Script started"); log("Task GID: " + result.data.gid);
if (!result.data.assignee) {
log("No assignee found");
return;
}
const assigneeName = result.data.assignee.name;
log("Assignee: " + assigneeName);
const targetProjectName = assigneeName + "'s Dashboard";
log("Looking for: " + targetProjectName);
const workspaceGid = result.data.workspace.gid;
log("Workspace GID: " + workspaceGid);
// Search for projects in the workspace
let projectOpts = {
'workspace': workspaceGid,
'opt_fields': "gid,name"
};
log("About to search projects...");
projectsApiInstance.getProjects(projectOpts).then((projects) => {
log("Projects retrieved: " + projects.data.length);
// Find matching project
const targetProject = projects.data.find(p => p.name === targetProjectName);
if (!targetProject) {
log("Project not found: " + targetProjectName);
return;
}
log("Found project: " + targetProject.name + " (GID: " + targetProject.gid + ")");
// Add task to project
tasksApiInstance.addProjectForTask({
data: {
project: targetProject.gid
}
}, task_gid).then(() => {
log("✓ Added to " + targetProjectName);
});
}).catch(err => {
log("Error getting projects: " + err.message);
});
}).catch(err => { log("Error getting task: " + err.message); }); }
run();
More Script Actions Resources
Join future Asana AI Office Hours
This open Q&A session is your chance to get live answers and hands-on guidance from our team. Whether you’re fine-tuning a prompt, exploring AI Studio features, or looking for best practices, bring your questions and use cases for a collaborative, real-time learning experience.
If you already know what you’d like to ask, you can submit your question using this form. Not sure yet? Don't sweat it! We will be taking questions on the call.
P.S. If 2026 is the year you finally start your newsletter, I highly recommend checking out beehiiv 👇🏻 Have I personally made $132,341 from newsletters? No, but it’s a catchy graphic, right?
Your readers want great content. You want growth and revenue. beehiiv gives you both. With stunning posts, a website that actually converts, and every monetization tool already baked in, beehiiv is the all-in-one platform for builders. Get started for free, no credit card required.