A workflow automates actions based on specified events or item properties. For example, it can create tasks, update information or send email. The trigger determines when the workflow starts, conditions and branches determine which situations it handles, and events determine which actions it performs.

Requirements and preparation

Creating and managing workflows requires a Spotilla administrator account and the workflow feature to be activated for your customer account. Open Workflow tool from the browser navigation. Workflows are managed in the browser; the Android and iOS apps do not have an equivalent management view.

Creating or updating a task on mobile can still trigger a workflow configured in the browser once the change has been saved to the service. This requires an active workflow and its trigger, conditions and scheduling restrictions to be met.

Before building the workflow, decide which information it may process and what the outcome should be. In particular, check the item to be updated, the content of the information to be created and the email recipients. If another workflow monitors the same information, a change made by one workflow can trigger the other. Restrict the conditions to prevent a chain of workflows that continuously trigger each other.

Create a workflow folder if needed

A folder organizes workflows by purpose. It is optional: a workflow saved without a folder appears in the Miscellaneous workflows group in the table.

  1. Select Create new workflow folder at the top of Workflow tool.
  2. Fill in the required The name of the workflow folder field. You can also add an optional Description of the workflow folder.
  3. Save using the Create new workflow folder button on the form.

You can also create a folder next to the folder selection in the final step of the workflow form. The new folder is then automatically selected in the open workflow form.

Select a trigger and build the workflow

  1. Select Create new workflow at the top of Workflow tool.
  2. Select Event when the workflow should start from an event or a change. Select Property when comparing an item's information; in this case, also select a task, service request, message or Spot as the target. Continue using the Next button.
  3. In the Set conditions and events step, specify the trigger details and restrictions. Build the branches you need and their conditions.
  4. Select Add new event from the action options for the branch you want. Select an event in its Select the event field and open Set the information. Fill in and save the event details. Selecting the event type alone is not enough.
  5. When the structure is ready, select Test and create a workflow at the bottom of the form.

The workflow must contain at least one event with its details filled in. The form also checks the branch structure and required information before moving to the final step. Correct any reported issues; a branch cannot end with only a condition or a delay.

Trigger restrictions are described in Workflow triggers and conditions. The use of branches, delays, lookups and calculations is described in Workflow branches and delays. For help with targeting events, see Creating and updating information with a workflow.

Understand the test result

The final step contains the Test your workflow, Repetition and scheduling functions and Workflow basic info sections. Test and create a workflow opens this step; it does not yet save the actual workflow.

For a property-based workflow, the item count test starts when you enter this step. You can repeat it using the button of the same name in the Test your workflow section. The test examines the information currently available for the selected item type:

  • Number of items the workflow will start for shows the number of items that proceed from the trigger conditions. If the workflow also has a branch for conditions that are not met, the count includes items directed to that branch.
  • The number of items affected by the workflow shows the items whose tested path ends in a creation, update or email event. It is not the number of tasks to be created, fields to be changed or messages to be sent.

The item count test does not create or update anything or send email. It skips delays and does not represent a later run governed by the schedule or daily execution limit. The result does not guarantee that saving an actual event or sending a message will succeed. If the count is unexpected, select Return to conditions and events at the bottom, correct the restrictions and test again.

For an event-based workflow, the testing section asks you to trigger the selected event yourself. Perform this practical test only after the workflow has been saved and is active. It performs real actions, so use a limited test scenario and check the resulting information as well.

Select the processing method, basic information and status

Open Repetition and scheduling functions. For a property-based workflow, these options determine when information is actually processed:

  • The execution option in the Manually start the workflow section starts a one-time run for existing items after saving. On its own, it does not enable monitoring of future changes.
  • Start the workflow regularly processes existing items repeatedly. Set the interval and choose whether the first run starts immediately after saving or at a specified time. The minimum allowed interval is 15 minutes. A successful item count test enables the interval settings; the displayed start limits for items may require a longer interval.
  • Start the workflow event-based enables checks of the property conditions when the item is created or updated in the future. A later update to an existing item can therefore also trigger the workflow. This option cannot be combined with regular starts.

You can combine a one-time run with a later processing method. If regular processing starts immediately after saving, a separate one-time run is not started again during the same save. The one-time run and the start of scheduled processing require an active workflow. These are actual executions, not item count tests.

For an event-based workflow, select Always or the allowed weekdays and times in the same section, and individual dates if needed. These restrict when an event may trigger the workflow; they do not themselves create a triggering event. If you use both weekdays and individual dates, meeting either restriction is sufficient.

For an event-based workflow, you can enter a positive whole number in Limit how many times per day the workflow can be completed. Leaving the field empty means this limit is not used. When a start is evaluated, the count includes executions that started during the current day in the service's time zone and were recorded as ending in an event. Executions that ended in an error or an empty branch are not included in this count. The limit does not disable the workflow.

Finally, open Workflow basic info. Fill in the required Workflow name, add a Workflow description if needed and select a folder in Select the workflow folder to which the workflow will be added. The description and folder are optional.

The default value of the Status field is Out of use. This allows you to save the configuration before enabling it. Select Active when you want the workflow to perform the processing you selected. Confirm the actual save using the Create new workflow button at the bottom of the form. Saving an active workflow may immediately start the selected one-time run or regular processing.

More detailed scheduling settings and execution monitoring are described in Workflow scheduling and history.

Check the result and manage the workflow status

Open the Datatable tab in Workflow tool and select the name of the saved workflow. Check its structure, folder, processing method, schedule and status. Save changes through the Test and save step using the Save button. You can enable or disable the workflow by changing the Status field in its basic information.

Perform a limited real test on the active workflow using your selected processing method. Check that the desired task, information change or message is created and that no other items are processed unexpectedly. Then open the History tab in Workflow tool and select the workflow in the Select workflow field. Compare the execution time, item and final status with your test scenario. Successfully creating a workflow or obtaining an item count from the test does not prove that the action succeeded.

Out of use preserves the configuration and history. New executions do not start, and a queued workflow step checks whether the workflow is active before executing. Disabling the workflow does not undo changes already made.

Disabled automatically by the system means the system has stopped the workflow. This may be caused by a limit on the number of creations, emails or updates, processing the same item too frequently, or a repeating chain of workflows. The limits depend on the customer account settings and processing method; they are separate from the daily execution limit you set yourself. Investigate and correct the cause before reactivating the workflow. The configuration and history are preserved in this status as well.

Change the folder or delete a workflow

To change a workflow's folder, open its name in Datatable and change the folder selection in the final step. You can also clear the selection to move the workflow to the Miscellaneous workflows group. Opening a folder's name displays its editing form and Workflows included in the folder. You can change the folder's name or description and save them using the Save button.

Delete a workflow or folder using the trash icon at the right end of its row in Datatable and accept the confirmation. Deleting a workflow removes its configuration, scheduling configuration, execution history and saved continuations after delays. A queued workflow step will not execute a deleted workflow.

Deleting a folder also deletes all workflows in it, including their histories. If the folder contains workflows, the view asks for a separate confirmation to delete them. Before deleting the folder, move any workflows you want to keep to another folder or clear their folder selection and save.

Deleting a workflow does not delete tasks or other items it has already created, restore previous field values or recall emails already sent. If you only want to stop the automation and preserve its information, use the Out of use status.