Trigger Automation, as a step of an Automation ( Automation Nesting )

[poirazis]

Imginary Scenario I have an Automation, called logValueChange which tracks various fields history, using the User.email as the key to who made this change. Now during many other different automatons, i would like to run my logValueChange automation as a step.

Example Automation - App Trigger

• Step1. Query Rows
• Step2. Do Something Awesome
• Step3. Trigger Automation logValueChange
• Step4. Trigger Automation dispatchSMS

Now, this opens the door to automation nesting so the user can break up large automations into smaller, reusable parts.

[martkaczmarek]

You could create Automation with Webhook trigger and reference that webhook in another Automation with some custom Rest API source query But yeah, that would be useful to have an Action Trigger Autimation ready to use

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity.

[cray74]

When self-hosting, automations can trigger other automations through events.

For example if one automation creates a row, then you can use the Row Created trigger in another automation to catch this.

Currently this is not the case in the cloud environment, however we do plan to make this option available there.

does this statement still hold true for self-hosted setups? for our setup (just updated from 2.11.41 to 2.13.28) it appears the trigger "row created" is not firing if the row was created from within another automation.

[melohagan]

Hey @cray74

I gave this a test and self-hosted automations do not trigger other automations. So the behaviour between cloud and self-host is consistent.

I have deleted my original comment as it was not correct.