{"id":27213,"date":"2022-05-18T07:58:43","date_gmt":"2022-05-18T05:58:43","guid":{"rendered":"https:\/\/www.testify.io\/instructions-how-to-build-workflows-in-testify-including-examples\/"},"modified":"2026-09-09T14:25:48","modified_gmt":"2026-09-09T12:25:48","slug":"instructions-how-to-build-workflows-in-testify-including-examples","status":"publish","type":"post","link":"https:\/\/www.testify.io\/en\/instructions-how-to-build-workflows-in-testify-including-examples\/","title":{"rendered":"Instructions – How to build workflows in Testify (including examples)."},"content":{"rendered":"\n
\"\"<\/figure>\n\n

At Testify, we have developed a modular system that enables you to digitally control, document and analyze all types of mobile testing and quality processes.<\/p>\n\n

Today we would like to present examples of workflows in Testify and take a closer look at the workflow functions of the software, which we have prepared for you in the following. <\/p>\n\n

We present these examples of complete workflows:<\/strong>1) Initiation of a checklist when adding a test object2) Initiation of a checklist when creating a defect3) Initiation of a sequence of related checklists4) PDF generation after checklist execution5) Webhook: Save PDF log to external system6) Timer: Monthly assignment of a defect as a task7) Timer & notification: Periodic notifications to persons\/groups<\/p>\n\n

Automate work processes in Testify.<\/h2>\n\n

Automated workflows ensure efficient workflows in your checklist processes. By using the workflow management feature, you can save time and resources by automating recurring activities. This allows you to fully focus on your core tasks in the future! <\/p>\n\n

Customize your checklist, defect and test object workflows simply and easily to your individual needs. The special feature of Testify is that process flows can be configured – in other words, according to the motto: no-code implementation. This means that you can make quick adjustments to your company workflows. Without any programming knowledge! <\/p>\n\n

Introduction to events, promotions and webhooks.<\/h2>\n\n

Webhooks, events and actions are needed to network process sequences so that you can create digital consistency across multiple systems. But what does that actually mean? <\/p>\n\n

What is the connection between actions <\/strong>and events<\/strong>?<\/p>\n\n

Workflows enable the automation of work processes within Testify by triggering predefined actions through certain events. <\/p>\n\n

What are webhooks<\/strong>?<\/p>\n\n

Webhooks are used to transfer information to external systems in order to trigger actions there. <\/p>\n\n

Examples of actions<\/h3>\n\n

Here we would like to present three examples of actions that can be used in workflow management: Webhook, Generate PDF and Send Notification.<\/p>\n\n

Example: Webhook action<\/strong><\/p>\n\n

Based on events within Testify, webhooks can also be added independently as actions in workflow management. This is possible by selecting the “Webhook” area with the “Trigger” type. A URL must be specified as a parameter; optionally, an identifier, an HTTP request timeout and HTTP status codes that indicate success can be entered. <\/p>\n\n

\"\"<\/figure>\n\n

Example: Generate PDF action<\/strong><\/p>\n\n

The generation of PDF logs can also be automated as an action via a workflow. This process automation<\/a> should start the generation of PDFs for the filtered checklists. Filters can be set based on the events in order to define exactly for which test objects or checklists the automated PDF generation should take place. <\/p>\n\n

\"\"<\/figure>\n\n

As a prerequisite for this automation, it is necessary to define a corresponding event in advance:<\/p>\n\n

Area: ChecklistRemaining filters as requiredThe action can then be defined:<\/p>\n\n

Area: PDFType: generateParameters: Selection of the desired PDF protocol profile and language<\/p>\n\n

Example: Send notification action<\/strong><\/p>\n\n

Notifications can be triggered by checklists, defects, test objects, users or timers. The language, the message, the recipient (user or group) and the notification type (mail, in-app) can be defined. In addition, the user-defined messages can be translated. <\/p>\n\n

Event “Test object created” triggers the “Notification” action:<\/p>\n\n

\"\"<\/figure>\n\n
\"\"<\/figure>\n\n

Examples of complete workflows.<\/h2>\n\n

Below we present 7 examples that show how the workflow functions can be used in practice.<\/p>\n\n

1) Initiation of a checklist when adding a test object<\/h3>\n\n

In this example, we will show you how to create a workflow for ‘Publishing a checklist when adding a test object’.<\/p>\n\n

\"\"
Creating a workflow for “Initiating a checklist when adding a test object”<\/figcaption><\/figure>\n\n

Event:<\/strong><\/p>\n\n

When a new test object is added from “Testify Admin” to “Frankfurt Airport”, the action is executed.<\/p>\n\n

Action:<\/strong><\/p>\n\n

A checklist is created by “Testify Admin” for the added test object, which is assigned to the user “Testify Admin” and is due in 7 days at 12:30 pm.<\/p>\n\n

2) Initiation of a checklist when creating a defect<\/h3>\n\n

In this example, we will show you how to put together a workflow for ‘Publishing a checklist when creating a defect’.<\/p>\n\n

\"\"
Creating a workflow for “Initiating a checklist when creating a defect”<\/figcaption><\/figure>\n\n

Event:<\/strong><\/p>\n\n

If a new defect with the category “Logistical error” is added to “Frankfurt Airport”, the action is executed.<\/p>\n\n

Action:<\/strong><\/p>\n\n

A “Logistical Defect – Checklist” checklist is created by “Testify Admin” for the test object where the defect occurred, assigned to the “Engineering” area and is due in 3 days at 12:01.<\/p>\n\n

3) Introduction of a sequence of related checklists<\/h3>\n\n

In this example, we will show you how to put together a workflow for the ‘Initiation of a sequence of related checklists’.<\/p>\n\n

\"\"
Creating a workflow for “initiating a sequence of related checklists”<\/figcaption><\/figure>\n\n

Event:<\/strong><\/p>\n\n

If a checklist is created for an inspection object “Frankfurt Airport”, the action is executed.<\/p>\n\n

Action:<\/strong><\/p>\n\n

    \n
  1. An “Electrician – Checklist” is created for the same test object by “Testify Admin”, assigned to “Testify Admin” and due 7 days in advance at 12:00 noon.<\/li>\n\n\n\n
  2. A “Mechanic – Checklist” is created for the same test object by “Testify Admin”, assigned to “Testify Admin” and due 7 days in advance at 12:00 noon.<\/li>\n<\/ol>\n\n

    4) PDF generation after checklist execution<\/h3>\n\n

    In this example, we show you how to create a workflow for ‘PDF generation after checklist execution’.<\/p>\n\n

    \"\"
    Creating a workflow for “PDF generation after checklist execution”<\/figcaption><\/figure>\n\n

    Event:<\/strong><\/p>\n\n

    If a checklist for a “Construction sites” test object is changed, the action is executed.<\/p>\n\n

    Action:<\/strong><\/p>\n\n

    The standard PDF report is generated after a checklist with the “Construction sites” test object has been changed.<\/p>\n\n

    5) Webhook: Save PDF log to external system<\/h3>\n\n

    PDF logs can also be automatically saved in external systems. For this purpose, an interface can be built by the customer based on our webhook, which stores the generated logs at the desired destination. <\/p>\n\n

    \"\"
    Create a workflow for “Save PDF log to external system”<\/figcaption><\/figure>\n\n

    Event:<\/strong><\/p>\n\n

    If a standard PDF report is created for a checklist with the “Construction sites” test object, the action is executed.<\/p>\n\n

    Action:<\/strong><\/p>\n\n

    The created PDF log is saved in an external system via the interface with the Webhook action.<\/p>\n\n

    6) Timer: Monthly assignment of a defect as a task<\/h3>\n\n

    In this example, we will show you how to set up a workflow for a ‘Monthly assignment of a defect as a task’.<\/p>\n\n

    (In this example, defects are used to map tasks).<\/p>\n\n

    \"\"<\/figure>\n\n

    Event:<\/strong><\/p>\n\n