Hey there world. I am new to Automation and Make.com, I built six automations inside of a program called Pipedrive and they all function as intended. I then built two in Zapier for ASANA. Sadly, only one works thus far. What I am finding is that it seems that I need more than one “service” to get everything done that I would like between GMAIL, ASANA, and Pipedrive.
Problem: I have emails that get forwarded to my Project in ASANA that are “Spam” tasks, and I would like to automatically delete them when they come in.
Partial Solution:
Trigger is set to Watch for Created Tasks in the Specified Project and Section (I tried even pulling out the section)
Filter is set to find Text operators: Contains {{if(3.Task name; “is ending soon!”; )}} (I also have 04 other “or” statements
(HERE IS WHERE I CAN"T FIGURE IT OUT) Once it finds the task(s) via the filter, then it should delete the task. I can Select the Task from the list, or Enter it Manually. The problem that I see with selecting from a list is I can’t “Map” the task id. When I Enter it Manually, I can map it to the “task name” field.
When I set up a Test task named with something that does contain “is ending soon!”, It does not find it, nor delete it.
Let me know where I have gone astray. Thanks for your help in advance.
This is an X-Y problem. You’re trying to patch a problem when you could likely fix it at the source.
It’s best to find out which service is “writing to” / creating those spam tasks and filter them out at the source, so they don’t even get created in the first place.
Thanks for the reply. I do agree that it is better to start at the source. In this case, the source is GMAIL, so a filter can be applied there to resolve this. Long story, but I am trying to work through this automation with Make and see if it is “better” or more user-friendly than the “other guys”, and also so that all automation/filters are controlled from “one” location to ensure that everything is being done the same.
That being said, In working through the automation this morning, I was able to get a little further along. The Trigger and the Filter are working.
My problem yesterday was that I limited the Trigger to the default of 10. I set that to 5000 this morning, and received the error "[400] The result is too large. You should use pagination (may require specifying a workspace)! I found that odd as the message states “may require specifying a workspace” and yet I had specified the Workspace, Project, and even the Section name of where the “new” tasks come to.
I lowered this down to 100, and even that was too large. It wasn’t until I specified modified after 01/01/2024 and set the number to 5000 that the “trigger” worked.
The filter works and found 386 Bundles of which 01 Bundle met the condition.
The final Action step has one bundle, but gives the error “[400] task: Not a Long: Test - is ending soon!” In searching on the web I cannot find any useful info.
