Setting number of operations generated by one module as a variable in route filter

How To
, ,
1

Hi everyone :wave:

I’m just starting to play with Make (and I love it already :)) and I’d like to ask you (as my own search for the answer wasn’t successful till now):

Is there an option to put number of operations generated by one module as a variable in a route filter? (in a free plan)

I am setting up a scenario where I’m creating Asana tasks based on Slack masseges from a defined channel.

I have Slack - Watch Private Channel Messages module then Asana - Create a Task or a Subtask module and I’d like to end with another Asana - Create a Task or a Subtask module.

I would like to set a Route Filter between the two Asana modules in a way that if the first module generates operations (1 or more), it will create 1 new task in Asana (not for every operation generated, but if there were any operations generated, 1 asana task will be added).

I was thinking to set the number of module-generated operations as a variable in the filter. But I cannot find a way how to map it there.

Is there any way how to do it? Or could you help me figure out another scenario scheme that would do the trick?

The idea is that we don’t want to asign an asignee to every task generated in Asana based on Slack messages. Instead we have a dedicated person who is responsible for delegating the tasks further once they’re in Asana. And we need to create a task for this person to do that when there are some new tasks added from running the scenario.

Thank you very much guys for helping me :).

2

Hey Michala,

when a module produces more than one bundle you have two variables: Bundle order position and Total number of bundles. You can configure a filter that is Bundle order position equals 1, this way this way only the first bundle will go through and the secondary task will be created, the rest of the bundles will only create the first task.

Now if you need the secondary task to be created explicitly after the first tasks are done creating → use and Aggregator module to combine all of the previous operations in a single operation. This way the secondary task module will run only once when the rest are done running.

3

wow, thank you, these are both excellent ideas, I’ll try them both, play with it a bit and see what suit us better :slight_smile: thank you!