Having an "On Demand" trigger should be pretty simple to create, as it would be similar (though I'm sure not exactly the same) to the code necessary to generate a "Test". AND, this would be extremely helpful. Sometimes there are occasional manual processes that could be replaced with a recipe, but you don't want it to run unless you tell it to - similar to activating a webhook.
I think you could use the Workato Utility to start and stop recipes on demand?
Hi, I've yet to find a way to manually (not scheduled, not triggered) kick off a recipe in Workato and would really like for the feature to be available.
it’s just something that needs to happen in response to a manual action - like a time event but now. (I envision it as a “run now” button in the workato interface. Zapier has a way to do it where they have a Chrome plug-in that simply allows you to click the name of the zap and optionally supply some input data for the recipe and the recipe runs.There is no trigger in the current sense that another application is triggering the event. Let me know if that doesn’t help.
If you use Slack, you can create a Workbot command that will manually trigger like a button. I've been doing this since my last post here and it's amazing.
I just use the Scheduler trigger set to 5 min interval for this. Whenever I need to run the recipe on demand, I just press Test Recipe. If I need to run in again within 5 mins, I just rerun the Job.
Brad, good idea except if your data is changing.... Workato will reuse the data that was picked up from that Job.
You're right Chase, that only works when you don't bring in any data through the trigger, which is I think what Carlos was suggesting. All of my recipes that run on Schedules start with a Search action as the first step to look for data that meets the condition I want to run the recipe for. That way, even when rerunning a Job it will always pick up fresh data.
Ahh I see your thought process. That makes sense.
At the end of the day, we have no way to run a single job with the click of a button. The use cases are limited because this is mostly for testing purposes (assuming your recipe doesn't search for new data first). The majority of the times I need this, I'm testing "snippets" of a larger recipe I'm building out.
Send us a ticket, we will try our best to assist you with your problem