Is it possible to use multiple CRON triggers in the same Automation, also while "passing" values from one workspace block to another using values from an embedded Automations writer? Essentially I would like to set up a single Automation that triggers at a given time, completes a number of steps, and then "waits" for a second CRON trigger to continue with additional steps, and with the additional steps part of the routine using a value from an upstream block.
Best Answer
It is possible to set up multiple CRON triggers in a single Automation AND use JSON messages from upstream block set by an embedded Automations writer?
+10- Contributor
Best answer by richardatsafe
Hi @pmcpherson ,
Thanks for the great questions and interesting scenario. At this time workspaces are limited to one trigger per workflow meaning you can't use the merge to merge a new trigger into the workflow. If this is useful for you I would recommend creating an idea for this enhancement. For now, I think you are going to have to use two automation workflows and have a staging/temp table to hold the values you want to pass to the second part of the workflow. We'd love to hear more about this scenario, and if others have similar needs.
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+10- Safer
- Best Answer
Hi @pmcpherson ,
Thanks for the great questions and interesting scenario. At this time workspaces are limited to one trigger per workflow meaning you can't use the merge to merge a new trigger into the workflow. If this is useful for you I would recommend creating an idea for this enhancement. For now, I think you are going to have to use two automation workflows and have a staging/temp table to hold the values you want to pass to the second part of the workflow. We'd love to hear more about this scenario, and if others have similar needs.