Wiresk

Wiresk

General Glossary

Estimated reading time: 6 min

API is the acronym for Application Programming Interface. 

It’s an intermediary software that helps applications to talk with each other. In Wiresk, APIs are used to extract and share data between various applications and services making them work together smoothly. 

APIs are everywhere around us; when you send a mobile payment, when you open a weather app on your phone, when you post a photo on Instagram and share it to Facebook or twitter. APIs are the behind-the-scenes technology that enables different software systems to communicate. 

For a detailed breakdown of the topic refer to: 

Wikipedia: https://en.wikipedia.org/wiki/API 

It’s a unique identifier used to authenticate and authorize access to an application (API). It acts as a secure token for Wiresk to communicate with your connected application and services. 

The back-end is the part in the background of a website, computer system, or software where data is stored and processed. It is in opposition to the front end.

Condition logic in workflow automation is a series of established rules that dictate the sequence of actions depending on specific conditions. It operates in a manner that is like “if-then” statements in programming: if a specific condition is fulfilled, a specific action is activated; if not, a different action is taken or no action is taken at all. This logic enables workflows to adjust in real-time

CRM

CRM (Customer Relationship Management) is a strategy for managing a company’s relationships and interactions with its customers or potential customers. The objective of a CRM system is to improve business relationships.

A database is a set of stored, organized and structured information.

The data warehouse is a database where information is organized in two-dimensional tables, and where the relationships between the data play a determining role in their exploitation.

Data that is dependent on each other. It can therefore change according to the other data.

These are data independent of others, they are generally written and are therefore immobile, they do not change depending on other data.

A collection of entities from which data can be drawn. Sources include manual systems such as databases, spreadsheets, text files, and applications as well as online sources such as web pages and RSS feeds.

The practice of developing an abstract representation of how data should be organized before being loaded into an ETL pipeline or another type of analytics platform. Data modeling helps identify potential flaws in the structure of the underlying database structures before they become issues further downstream in the ETL process.

The process of extracting data from its source, transforming it into a target format, and loading it into a data warehouse or other target system.

The process of retrieving data from one or more sources for use in subsequent operations.

Software specifically designed to automate the ETL process. These tools are typically GUI-based graphical tools with an associated scripting language for customizing extraction, transformation, and loading instructions.

A Flow is our Wiresk terminology to define a workflow automation that you create with our Flow Builder. A Flow can be a single step or a multi-step. 

A Flow is: When something happens, the workflow automation will trigger a series of actions that follow predefined rules and conditions. 

This term corresponds to the elements of a site that we see on the screen and with which we can interact from a browser. The elements visible on a website are a combination of HTML, CSS, and JavaScript.

FTP is a protocol for transferring files from a computer to a server or vice versa. FTP is used to send large files that cannot be compressed and cannot be sent in any other way.

An input field is a designated space(field) where data or information is inserted or given to start or manage the Flow. In Wiresk, the input field refer to the field where you Map can data from the Flow, Step Responses and Meta.

The process of taking extracted and transformed data and transferring it into a target system, such as a data warehouse or other repository.

In simple terms, The Data Mapping is the process of transferring data from point A to a selected point B. 

Refer to:  Field Data Mapping documentation. 

It is an action that your automation will do after the Trigger. The Methods are like mini programs that do one thing, it will perform a specific task on a particular app or service you’ve connected to Wiresk like get info or send emails. 

After setting up your Trigger in your Flow (define the starting event), you must choose what Method (action) your flow will perform. Multiple Methods can be used for complex Flows. 

A standard established by Microsoft to provide a consistent means of moving data between different database formats. ODBC enables software applications to talk directly to databases without intermediary action by people or complex code being written.

A technology for analyzing multidimensional information stored in a database using advanced mathematical techniques like aggregation and drill down etc. OLAP is intended for fairly sophisticated users who need quick access to large amounts of historical data stored in a cube-like structure.

A no-code query builder is a tool that allows users to create complex SQL queries without having to write any code. This makes it possible for non-technical users to access and analyze data without having to learn SQL. 

No-code query builders are typically graphical user interfaces (GUIs) that allow users to select and filter data. They also often provide pre-built templates for common queries. 

A routing key is a parameter used to direct data or tasks to specific workflows based on defined conditions. It acts as a filter, ensuring that the right information triggers the proper action within a Flow. You will need a routing key to do a ‘Run once” for testing your Flows. In a Flow creation, you can set up an HTTP Trigger with a generated API, this will be your Routing key. 

When setting up your Flow, you can use “Run Once” for a run test. It will use a data set sample retrieved during your Trigger parameter with the “Get Sample” step. 

A “Get sample” is as its name suggests, a sample of data. The data will be used to MAP (refer to FIELD MAPPING documentation) your Method parameters depending on your Flow. 

It’s a feature that allows you to run your Flow at a Specific time or intervals automatically instead of being triggered by events like Webhooks. 

In Wiresk you can set up your recurrence such as: 

  • Regular intervals will monitor your Trigger by intervals in minute 
  • Daily recurrence will monitor your Trigger by day and hour  
  • Monthly recurrence will monitor your Trigger every month on a defined date and hour 
  • Yearly recurrence will monitor your Trigger on a specific date and hour every year 
  • Specific dates will start your Trigger on specific dates 

A step in Wiresk refers to an individual action or task within a Flow. Each step represents a specific process, such as sending an email, updating a record, or triggering another app. Steps are executed in the order defined by the workflow, with data passing from one step to the next. 

A language commonly used in relational databases for defining relationships, creating tables, inserting records, manipulating tables, and retrieving data stored on them.

Synchronous execution means that tasks are executed one after the other. Each task must be completed before the next one starts. 

Imagine you have a workflow where you first send an email, then update a database, and finally notify a user. If these steps are synchronous: 

  • The platform sends the email and waits for it to be sent. 
  • Once the email is sent, it updates the database. 
  • After the database is updated, it notifies the user. 

Asynchronous execution means that tasks can be started without waiting for the previous ones to be completed. Wiresk can run multiple Steps or Methods simultaneously. 

Using the same workflow (sending an email, updating a database, notifying a user), if these steps are asynchronous: 

  • The platform starts sending the email and moves on to update the database without waiting for the email to be sent. 
  • It then notifies the user while the email is still being sent and the database update is in progress. 

The template is a model from which you can draw inspiration. Here, the template gives an example of Flow, and thus of possible connection between the different integrations.

It is a Wiresk feature that enables users to perform specific actions within a workflow. These tools can include pre-built actions like sending emails, updating databases, generating reports, or integrating with third-party applications. Tools help you automate tasks without needing to write code, offering a way to build Flows through simple, customizable components. 

Every Flow starts with a Trigger, it’s the event that will initiate your Flows. 

There are 2 types of Triggers: 

  • Scheduled Triggers which you can set up a recurrence rule and based on specific event and conditions. 
  • Instant Triggers, also called Webhooks, will activate your Flow automatically by a spontaneous event from your applications. This means, the Flow is automated without a scheduler and will run until you deactivate the Flow manually. 

Depending on your Flow scenario, you can set up multiple Triggers. 

The process of modifying the structure or contents of data to suit the requirements of downstream processes or systems.

In the context of an automation workflow, a webhook is a function that allows one application to send real-time data to another application. 

Characteristics of a Webhook: 

  • Real time data transfer 
  • Trigger-based 
  • Simple integration 

Webhook documentation.