Automations beta - FAQ

Frequently asked questions regarding the automations beta.

Overview

Welcome to the FAQ (Frequently Asked Questions) page for the automations beta. The purpose of this page is to provide answers to common questions regarding the automations feature.

What is a beta program?

A beta program is where we make a new feature available to customers who’d like to try it early and share feedback before its general release. During this phase, you can explore the automations feature in your own environment, experiment with triggers/actions etc., and provide valuable feedback as to features, and usability. Because it’s still in beta, some aspects of the experience will evolve based on your feedback: that’s the goal. This approach helps us refine automations faster and ensures that when it’s fully released, it delivers the functionality and stability you expect.

Automations is an open beta: unlike a closed beta, there’s no application or approval process. Any administrator can enable it directly from their own team’s settings.

What are automations?

See Introduction to automations for what automations is and how it works.

What trigger types does automations support?

Automations currently supports four trigger types:

  • Record Modified: start a workflow when a record is created, updated, or deleted
  • Record Time Offset: start a workflow at a time relative to a date field on a record, for records matching a condition
  • Scheduled: start a workflow on a recurring schedule, independent of any record
  • Event: start a workflow when a named platform event occurs, such as a rules violation

See Triggers for full reference documentation on each trigger type.

How do I enable or disable automations?

Any administrator can enable automations from Settings > System administration > Beta features by checking the Enable automations (browser refresh required) checkbox, then refreshing the browser. Unchecking the same box, and refreshing again, disables it.

See Learn about the automations beta for step-by-step instructions.

Who can use automations?

Automations is a feature aimed at administrators, who manage the configuration of a Skedulo team.

  • Viewing automations: requires the Administrator role, or a role that includes the “View webhooks and triggered actions” permission.
  • Creating, editing, or deleting automations: requires the Administrator role, or a role that includes the “Modify webhooks and triggered actions” permission: this also covers activating and deactivating them.

Once you have created and activated an automation, the effects of the workflow will be apparent to other users, for example, if the automation makes changes to a record, users with access to the record will see those changes.

Can I use automations in my production environment?

We strongly recommend fully testing automations in a non-production environment before considering any use in production.

How do automations differ from triggered actions?

Automations have many advantages over triggered actions, and we expect to ultimately replace the triggered actions feature by converting them to automations.

Automations differ from triggered actions in the following ways:

  • Automations can execute multiple actions sequentially
  • Automations can include logic, such as choice steps, to branch the execution logic

Automations don’t currently support:

  • Bulkified payloads from the record modified trigger: automations process record modified events one record at a time
  • Send SMS with template: the Send SMS action in automations requires you to pass a prepared message. We don’t currently support message templates the same way triggered actions does

Triggered actions’ deferred trigger: executing at a time relative to a datetime field on the record: is supported in automations, under the Record Time Offset trigger.

Can I turn off the beta if I no longer wish to participate?

Yes: automations is a self-service open beta, so you can disable it yourself from Settings > System administration > Beta features by unchecking the Enable automations (browser refresh required) checkbox and refreshing your browser. We recommend deactivating any active automations first.

When will automations be generally available?

Our plan is to release the GA version of automations in Q3 2026. This is subject to change based on feedback from our customers.