Do wMio support multiple triggers?

Consider - I want to have two triggers in a workflow -

1. Clock trigger
2. Gmail trigger

If multiple triggers are allowed, how to set the Join conditions ?

Thank you

Hi Naidu,

We dont support Joins with multiple triggers yet. BUt we might be able solve this with webhooks and callbacks. Can you please explain the use case?

Usecase1: Periodically call a SaaS service (svc1), and update the google sheet with the svc1 output.

Now, we have usecase2
Usecase2: On receiving an email (support email), if the subject contains a keyword (key1), then call the SaaS service (svc1), and update the google sheet with the svc1 output.

If you observe, the sequence of - " call the SaaS service (svc1), and update the google sheet with the svc1 output) " is same in both the usecases.

It is more ideal to join these two usecases into 1 workflow, as entire flow is very same except the trigger part.

So, I’m looking to have two triggers (or any alternate) in 1 workflow which -

1. Kicks off on clock period (every 6 hours)
2. Gmail email subscription (condition on the email subject key1)

/Thank you

Hello Naidu,

Thanks for getting back, you can achieve this runflow - https://docs.webmethods.io/integration/additional_features/run_flow/#gsc.tab=0.

Implement the re-usable module as a child workflow.

Trigger joins could be a good feature request.

Hi Naidu,

as Srikanth explains this functionality can be easily implemented with help of 3 WorkFlows.

(1) you implement your “doing workflow” independently of the trigger. For sure you need to model his interfaces as “Webhook” with return values. Alternatively you can implement this also as so called Integration Connector like “Node.js” or “webMethods.io Flow” if that in other cases better meet your needs.
(2) you implement your “periodic workflow” that use the “Developer Tools > Run Workflow” feature to execute your “doing workflow” from (1)
(3) you implement your “GMail triggered workflow” just doing the same as (2) and call (1)

Reminder: Consider to activate the authentication feature if you not want your service public available.