Platform basics

Automated Workflow

 Automation workflow is built with many single components connected, these components are called task that accomplishes a specific task, or connects with an outside service. For example, the https://sappersoftware.atlassian.net/wiki/spaces/SD/pages/125009726

The task action allows integrations to download and modify files on the database server. Numerous tasks are connected to form integration. A very simple integration might use the Salesforce task to fetch a file and post the contents of the file to a Slack channel using their component.

Complex integrations might be comprised of dozens of actions. Your configuration details will determine the overall flow and purpose of the automation.

Triggers

Triggers determine the mechanism by which automation can be triggered. Automation can be triggered based on a schedule, manually, or in a real-time process. It can be done by an external system based on the occurrence of a certain condition by using a webhook trigger.

Sapper has three types of triggers that you can incorporate in your automation for a specific type of requirement or actions that they need to perform. They are as follows:

Icon	Triggers	Function

Icon	Triggers	Function
Open	On-Demand	The on-demand trigger is the start node. It helps you to start or manually trigger the automation. It is the default automation trigger.
Open	Scheduled	Scheduled triggers allow you to create a regular schedule to dictate how often the automation should run. This is useful if they need to be triggered consistently at a specific time. You can set up a particular time, date, day, week, month, year, and any combination of it based on the requirements.
	Webhook	Webhook triggers allow you to run a particular instance by making an HTTP POST request to the webhook's URL. It is required if you would like an outside application to invoke an integration.

Universal Integration

Sapper offers a wide array of tasks to accomplish a variety of integration and automation. Primarily, there are three types of universal integration tasks:

1. Application Task

2. Core Task

3. Helper Tasks

For more information: https://sappersoftware.atlassian.net/wiki/spaces/SD/pages/677609531

Task Connections

A connection is a mechanism by which a task authenticates with a third-party app or service. A connection is input and might contain a username/password set, API key, OAuth 2.0 token, or some other proprietary authentication type.

They are the fields that make up a connection.

For more information: https://sappersoftware.atlassian.net/wiki/spaces/SD/pages/63602585

Native Connection

Through native connection, you can create a connection swiftly in a few steps, unlike the traditional way.

Native Apps

Native Apps are the applications that can be incorporated in any automation as per your requirements. There are plenty of apps for all the vivid domains. For example LMS, HCM, Payroll, E-Commerce, etc. Sapper always looks forward to adding more apps to make your work easy and efficient. It is user-friendly and easy to use.

All the possible tasks that an application can perform, are listed in a drop-down menu. You can opt for the desired task based on your automation and integration needs. For the scenario when the particular action is not mentioned in the drop-down menu, they can create a custom action. You can also add formulas based on your specific requirements.

Native Action

Tasks contain one or more actions listed under a drop-down menu, that can be invoked in the integration with a few clicks. For example, the task contains actions to post messages and list all channels in Slack.

You can view the actions of an application task by checking out the task’s configuration or in our documentation. Also, you can create a custom action for an application task as per your requirement.

For more information: