Perform the CRUD operation on the apps connected with Quickwork. Quickwork develops actions as per the API endpoints that the apps support. Then, those actions are configured as steps of a workflow.
Actions are responsible for performing the specified task of the app we connect. Acting as a secondary yet most important aspect of a journey, actions support more input fields than triggers allowing CRUD operation to perform in a fine-tuned manner. Apps that Quickwork supports contain a group of the following action features:
Let's take a tour of this guide and study the actions using Google Sheets and Google Calendar as an example.
The Send action allows you to send an email to a person with attachments, clickable buttons, etc. Consider the following Send email action in Gmail:
Figure 1: Send action
The Create/Add action lets you create an object in the account you connect. Consider the Add action example we have discussed here. In Google Sheets, creating or adding data in a row requires input in the Spreadsheet and Sheet field:
Figure 2: Create/Add action
Once executed, the Add row action will add a new row with the data specified in the input fields. In the action output, you can see the data created in the specified sheet of Google Sheets.
The Update action allows you to make changes to the existing data. The input specified in the action fields uniquely identifies the data to be updated. For example, update a row in a specific sheet of Google Sheets:
Figure 3: The update action
On execution, the action will update the data of a row specified and will return the entire object with all the fields in the action output.
The Search action is used to search for data with the help of the inputs specified in the action fields. In Google Sheets, you can search cell(s) in a specific spreadsheet. You just need to define the name of the spreadsheet in which you want to perform the search operation. The Search action will return all the cells matching the specified query condition:
Figure 4: The search action
If no objects are found, the Search action will return an empty list throwing no error. However, the other actions dependent on the search results will fail to execute.
The Get action is similar to the Search action, except for the results obtained. The Get action is more pinpointed and fetches the exact data of the object using unique Identifiers as an input. If the object is not found, the Get action will throw an error:
Figure 5: The search action
In the case of Google sheets, using the Get action on an account will require you to input the Sheet ID and row or column of which data you want to retrieve.
The Delete action lets you delete any object or data from the app connected. Using Google Calendar as an example app, let's see an action to delete a specific event. The input to this action is Calendar ID and Event ID:
Figure 6: The delete action
Upon execution, the journey will delete the specified event from Google Calendar.