Understanding Goalify Workflows

Goalify Workflows are an exceptionally useful feature with many different use cases. In its simplest form, a Goalify workflow can be a checklist that clients need to complete. It could also be a multi-day onboarding and training process for new team members, which lets you streamline SOP operations across your business. Using workflows, you can create specific tasks, collect feedback and data, request files, and more. Each step can even be assigned its own deadline. In this document, you'll learn all about Goalify workflows.

Important Terms

We've curated this glossary to provide you with a comprehensive understanding of the specific terms used in Goalify workflows. This resource is designed to guide and support you as you navigate the many features of this powerful tool.

Workflow

A Goalify workflow can be best described as the formal and visual representation of a process or collection of tasks to be completed (your workflow layout). A good example would be an onboarding process for new employees or a questionnaire.

Layout

You use our visual designer to design your Goalify workflows. It gives you access to a workflow's design canvas and its settings.

Roll-out

The process of assigning a specific workflow version to a client. Whenever you roll out a workflow to a client, you create a new cycle.

Cycle

A cycle refers to a specific version of a workflow for a member to work on and complete. A member can only complete each cycle once, but you can create multiple cycles for a client. You can think of a cycle as a blank copy of a form you give a client to fill out. Cycles can be started, stopped, archived, and deleted.

Step

A workflow design usually includes a series of steps. Each step can be an interactive element, a server-side action, or a utility element. The steps can be organized in a specific sequence for completion if needed.

Interactive Element

A task is a specific assignment that must be completed as part of a workflow. It typically includes a title and a description and may involve various interactive input elements such as text, numbers, selections, dates, file uploads, geo-location requests, and timers. For example: Review the attached inspection documentation for the hydraulic pump. Verify the oil pressure and enter the current PSI value below.

Example Groups

Feel free to refer to our examples to see how you can implement specific workflow designs.

Server-Side Actions

You can use server-side actions to perform certain administrative tasks, such as labeling, tagging, stopping, and archiving the current workflow cycle. The "Send Message" step allows you to send an email or push notification to a list of recipients. With the "Call API" feature, you can send data from the specific cycle to an adjacent web service. Server-side actions are carried out on our backend and not on the member's device.

Utilities

Utility elements allow you to pause the workflow at a specific moment or branch the workflow based on specific conditions. Additionally, the junction element is a design feature used when a collection of steps needs to be completed before the next collection of steps becomes available. Utility elements influence the behavior and design of a workflow but are not visible to the person working on the workflow.