This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Inspire EMEA 2022 On-Demand is live! Watch now, and be sure to save the date for Inspire 2023 in Las Vegas next May.
We'll be completing standard maintenance for our Single Sign-On system on November 30th 6pm Pacific Time for approximately one hour. During this time My Alteryx and sign-in functionality to all My Alteryx programs (Licensing Portal, Community, Beta Program, Case Portal, and others) may be inaccessible. Thank you for your patience.
Hi @olivierMPW, for the file you can use this tool here (https://github.com/bobpeers/Alteryx_SDK_EventTrigger). For the data I don't know a tool that does that, but you could build a workflow that keeps querying the database through an iterative macro for instance. You could insert something like the wait a sec (Crew macro) to delay the next iteration.
I think it depends on how quickly the event has to trigger the job from the customer's point of view. Could the job be run hourly to see if the file or DB has been updated? An hourly quick hit would keep that resource clear for use by other jobs. If that's an acceptable interval for the end customer, I'd be inclined to look in that direction.