Taskguid is the guid of the task you want to run. In my prev post I create a task on the fly and import it into the SMP, so I "control" this GUID, technically. If you manually create one on the SMP, you can get the guid by checking the task properties on the SMP.
ExecutionName is just a name, any name, you use to call the "execution" of the task
Input parameters is the input to the task, in XML format. In my video the input XML looks like this:
<inputParameters>
<parameter>
<name>@AssignedResources</name>
<value>CollectionToRunTaskAgainst</value>
</parameter>
<parameter>
<name>@CompRequirements</name>
<value>
<minWaitTime>1 minutes</minWaitTime>
<maxWaitTime>1 minutes</maxWaitTime>
<minCompletion>1 %</minCompletion>
</value>
</parameter>
</inputParameters>
Where it says CollectionToRunTaskAgainst, you have to use a Merge Text component to merge in collection/filter guid you want to run the task on.
Note theres a doc that goes with the vid that goes into a little more detail here: https://www-secure.symantec.com/connect/articles/creatingimportingexecuting-ns-tasks-workflow (I fly through the vid, but it's basically walking through this doc)