Adding a trigger

Let’s say you want to create a workflow such that when a new to-do item is created in Wunderlist, translate the title text to Spanish, and send the translated text to my email address. For this workflow, you will need to set up the trigger Wunderlist - Task Created. Let’s look at the steps involved in setting up this trigger.

  1. Create a new workflow

    To define a new trigger, you need to create a new workflow. To do so, navigate to the project and create a blank workflow. Add Google Translator connector and Send an Email action on canvas and connect them. If you are new to IBM® webMethods Integration, get more help on creating first workflow.

  2. Configure Start icon

    Trigger is the starting point of a workflow. Therefore, the Start icon houses all the settings related to triggers. Hover on the Start icon, and click the Settings icon to add and configure a trigger.

  3. Add Wunderlist

    A new window will appear where you can see the list of all web services for which IBM webMethods Integration supports trigger events. Locate the Wunderlist service from the list of services, and click on it.

  4. Configure Wunderlist trigger

    Certain fields are common for every trigger:

    • Trigger Label: Provide a suitable name for the trigger.

    • Select trigger: Each service has multiple trigger actions to choose from. Select the trigger action of your choice, from the drop-down list. For the purpose of this example, we will select the Task Created trigger.

    • Authorize Wunderlist: Select the account for which you want to set up the trigger, from the drop‐down list. If you have not created an account yet, hover on the + button. You will see two options:

      • Default Authorization: Select this option to allow IBM webMethods Integration to automatically generate all keys required to execute all Wunderlist triggers and actions.

      • Or: Select this option to provide the relevant keys required to execute all Wunderlist triggers and actions.

    After you have entered these details, click Next. This will redirect you to the trigger configuration window.

    Apart from these fields, you may see a few other fields, depending on the trigger you choose. You need to enter relevant data in these fields in order to successfully set the trigger. View our categories on various service-specific triggers to get in-depth info on how to configure each trigger.

    Once you enter data in all the fields, click Save to save your trigger. This will create the specified trigger on IBM webMethods Integration.

  5. Test Wunderlist trigger

    After this, you will be redirected to the Test trigger window, where you can check if you have configured the trigger settings properly.

    To test your trigger, you need to perform the trigger action in the web service account for which you are setting up a trigger (these instructions can be seen in the Test trigger window as well). In this example, Wunderlist - Task Created trigger, you will need to create a new task in the specified list of your Wunderlist account.

    Once this is done, go back to your trigger in IBM webMethods Integration and click on the Test button given at the bottom of the Test trigger form IBM webMethods Integration will then fetch the data of the item your just created in your Wunderlist account.

    If you have configured the trigger correctly, you will see the output data for the trigger. This will give you an idea of how your trigger will work when used in a workflow and which keys are returned in the output of the trigger. This output data will then be used to configure the rest of the workflow.

    You can alternatively Skip testing the trigger.

    If you Skip testing the trigger, IBM webMethods Integration will use mock data for that trigger to configure the rest of the workflow.

    You can also set custom filters to specify the conditions which must be met in order to execute the workflow. To do this, click on the filters link given at the bottom of the trigger output.

    A new window will appear where you can set up custom triggers using the sample output data returned.