General Automations

Prev Next

Servitly allows defining automations, which are executed on environment specific events, to trigger actions, like calling a third-party system API.

Creating an Automation

To add a new Automation to a Thing Definition, you should:

  1. Enter the Automations page.

  2. Select the General tab.

  3. Press the Add Automation button.

  4. Provide the required information.

  5. Press the Save button and edit the additional information, if needed.

Editing an Automation

By selecting an Automation, you can edit its properties, including event and the related actions to be executed.

Automation Events

According to the event type, different conditions can be then specified.

  • On Partner/Customer/Location/Thing/User Created/Updated/Deleted

    The automation is called each time a certain object type (Partner, Customer, Location, Thing, User) is created, updated or deleted in the DPS.

  • On Command Executed (DEPRECATED)

    The automation is called each time a user executes a command on a thing.

  • On Parameter Updated (DEPRECATED)

    The automation is called each time a user updates a parameter on a thing.

  • On Work Session Started

    The automation is called each time a work session is started on a thing.

  • On Work Session Stopped

    The automation is called each time a work session is stopped or completes on a thing.

  • On Store Order Created

    The automation is called each time a store order is placed.

  • On Store Order Status Updated

    The automation is called each time a store order status is updated (Pending Approval to Approved).

Automation Conditions

You can define one or more property-based conditions to be evaluated on the object where the event has occurred.
If the conditions are verified (all in AND), the defined actions are executed.

Conditions can be defined on all events related to Thing, Location, Customer, Partner, User objects.

Automation Actions

The automation allows configuring the actions to be triggered when the condition is verified.

You can define multiple actions of these following types:

  • Notification: email a specific address including into the body information of the event context.

  • REST API: performs an HTTPS request on an external REST API.
    This action supports authentication, header configuration and payload configuration in case of POST/PUT methods.

Automation Execution policy

The automation is periodically evaluated, for more details refer to the Periodic Evaluations article.