Skip to main content
What is the proposed idea/solution?

Disabling an action would skip that action during the automation run.

How does is solve the user problems?

This would allow me to build out actions, as they are supposed to be, but turn them off so I am only using the actions when I am ready for them. 

How was this validated?

I am currently building out a brand new system where multiple people get notified at different stages of the process. I need to build out the notification actions but I don't want those actions to run, to avoid annoying active users with system testing.

Who is the target audience?

Anybody that uses automations in Airtable.

Yes this is NEEDED.

Running into the same issue right now. Want to be able to turn off a notification step in an automation, without needing to delete and rebuild. I'm already using a repeater step so I can't hide in a logic step that would 'never be activated'. 

Yes. Yes. Yes.


Reply