Tutorials on Skedulo Documentation

Tutorial 1 - Hello automations

Mon, 01 Jan 0001 00:00:00 +0000

Beta feature

This feature is currently in beta, and should be considered ‘under development’. Learn about the automations beta.

Overview

In this tutorial you will create a simple automation that runs whenever a job is created or updated. The automation will use an Echo action to write a message to the activity log. This is a great way to verify that your trigger configuration is correct before adding more complex actions.

Tutorial 2 - Automatically setting the urgency of a job

Mon, 01 Jan 0001 00:00:00 +0000

Beta feature

This feature is currently in beta, and should be considered ‘under development’. Learn about the automations beta.

Overview

In this tutorial you will create an automation that automatically marks a job as Urgent whenever a Break Fix job is created, or an existing job’s type changes to Break Fix. This is a practical example of using the Update Records action to modify a field on a record based on the conditions that triggered the automation.

Tutorial 3 - Automatically calculating a line item total

Mon, 01 Jan 0001 00:00:00 +0000

Beta feature

This feature is currently in beta, and should be considered ‘under development’. Learn about the automations beta.

Overview

In this tutorial you will create an automation that automatically sets the Total field on an invoice line item to the correct value whenever Quantity or Unit Price is set or changed. This is a practical example of the calculated field pattern: keeping a derived value in sync with its source fields without any manual effort.

Tutorial 4 - Automatically create a job when a contact is added

Mon, 01 Jan 0001 00:00:00 +0000

Beta feature

This feature is currently in beta, and should be considered ‘under development’. Learn about the automations beta.

Overview

Scenario

You work for a home care organization. When a care coordinator registers a new client as a contact record in Skedulo, your team wants a needs assessment job automatically created so it can be picked up and scheduled promptly. Not every account should trigger this behavior: vendor accounts and referral partners should not create jobs: so each account has an AccountType field that classifies what kind of account it is.