1. In the Event section, choose the Scheduler by Quickwork app from the drop-down menu in the Apps field present right below the New Trigger button.
2. Select the trigger event as New scheduled event from the drop-down menu in the Triggers field.
3. Set the Interval as per your choice based on how often you want the document to be merged. Let us select 15 seconds.
4. Set the date and time of your choice in the Start At field and keep the Custom Payload field empty.
5. No authorization is required as this is an app created by Quickwork:

Using the Try Catch block

Let us use the Try Catch block to check whether the API endpoint is executing perfectly or not. We must specify an API endpoint in an action under the Try block. Then place the Error data pill under the Catch block such that any exemptions occurring are handled effectively.

Configuring the HTTP action under Try block

1. In the Steps section, click on the Business Logic button and choose Try Catch.
2. Click the Step 2 action bar. Select HTTP from the App drop-down menu.
3. Select Send new request as an action.
4. Enter the name of the API in the Request name field. E.g., User Login API.
5. Select application/json as Request content type.
6. Select POST as the Request HTTP method.
7. Enter the API endpoint in the Request URL field. E.g., https://apim.quickwork.co/hargrid/logon_creds/1/apim. 
   
   
   
   
8. Now, scroll down to the Request headers object. 
9. Enter apiKey as a name in the Header name field.
10. Specify the actual API key in the Header Value field:
    
    

Configuring the Logger action under Catch block

1. Click the Step 4 action bar. Select Logger from the App drop-down menu.
2. Select Log a Message as an action.
3. Drag and drop the Error data pill from the Catch action under Data Tree Output:
   
   
   

Introducing the If Else condition 

The purpose of using the If Else Condition and the actions within is to validate and send the notifications to a user as per the functioning of the API endpoint, respectively.

Configuring the If Condition

1. Click the + icon, click the Business Logic option, and select If Else Condition.
2. The If Else Condition block will appear with the pre-indented action bars.
3. In the Left Value field, drag and drop the Status Code data pill from the HTTP | Send new request response under Data Tree Output.
4. Select the Equals condition from the drop-down menu in the Condition field.

In the Right Value field, enter 200. The status code 200 means the API endpoint is working perfectly:

Configuring the Slack action under If Condition

1. Click on the Please choose an action bar under the If block.
2. Choose the Slack app from the drop-down menu in the App field.
3. Select the action, Send message to a channel, from the drop-down menu in the Action field.
4. Click the Link account button to connect Slack with Quickwork. 
5. In the Channel toggle field, choose the Select from list operation and then select the channel name in which you want the message to appear. E.g., mypersonal.
6. Enter the message in the Message field to be displayed on your Slack channel. E.g., The User Login API is working fine.
7. Leave all the other input fields empty: 

 

Configuring the Slack action under Else Condition

1. Click on the Please choose an action bar under the Else block, Step 8.
2. Choose the Slack app from the drop-down menu in the App field.
3. Select the action, Send message to a channel, from the drop-down menu in the Action field.
4. In the Channel toggle field, choose the Select from list operation and then select the channel name in which you want the message to appear. E.g., mypersonal.
5. Enter the message in the Message field to be displayed on your Slack channel. E.g.,
   
   The User Login API is malfunctioned. It might have stopped functioning due to following three reasons:
1. Incorrect API endpoint.
2. Incorrect API key.
3. Bad gateway.
   
   
6. Leave all the other input fields as empty: 

Executing the journey

The Try Catch journey is now successfully configured. It must look like this:

Save the changes of the journey and click Save & Start. Now go to your Slack channel. You'll see that after every 15 seconds, the status message of the API endpoint pops up:

In case of an invalid API endpoint or API key, the exception is handled by the Catch block resulting in a seamless flow of the journey. As a result, the following error message is obtained in the channel: