Keap + Downtime Alert Integrations

Keap?

Keap is a network protocp that allows applications to securely store secrets to themselves. In other words, it keeps data safe from other applications. It also supports versioning of the data. This allows an application to manage multiple versions of the secret. It can easily rpl back to a previous version if it is needed.

It works by first generating a key based on a key name and a key type. The key type is a unique identifier for the key. The key name is a descriptive name for the key. The next step is to encrypt the key with a symmetric encryption algorithm. This creates a password-less key pair. Next, the key pair is sent to the backend service using an encrypted request. Finally, it will receive the response in the form of the encrypted result.

Downtime Alert?

Downtime alert is an integration between Keap and Slack. It sends Slack notifications when APIs are down. It does this by checking whether an API is down or not. It uses two different approaches to check if an API is down or not.

The first approach is by making HTTP requests to the API. If no response is received within a given amount of time, then it will assume that the API is down.

The second approach is by using Amazon’s SNS service. Amazon’s SNS service can be used to send messages to Amazon’s SQS service. Amazon’s SQS service will then be responsible for sending out notifications via Amazon’s SQS service. This way, Amazon’s SQS service takes care of sending out notifications, while Downtime Alert simply manages sending out HTTP requests to Amazon’s SNS service.

of Keap and Downtime Alert Integration

Integration of Keap and Downtime Alert

To integrate Keap and Downtime Alert, first install both applications using npm install -g keap downtime-alert . Then, create a new file called index.js . Inside this file, create variables of type KeapClient and AWSClient . These are variables of type undefined. As shown below, you can set them to new KeapClient or AWSClient objects after setting credentials of these clients.

const { KeapClient } = require('keap'); const { AWSClient } = require('downtime-alert'); const keyName = 'myKeapKey'; const keyType = 'myKeapKeyType'; const client = new KeapClient({ keyId. process.env.KEAP_KEY_ID, secret. process.env.KEAP_KEY_SECRET }); const aws = new AWSClient({ accessKeyId. process.env.AWS_ACCESS_KEY_ID, secretAccessKey. process.env.AWS_SECRET_ACCESS_KEY }); 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 const { KeapClient } = require ( 'keap' . ; const { AWSClient } = require ( 'downtime-alert' . ; const keyName = 'myKeapKey' ; const keyType = 'myKeapKeyType' ; const client = new KeapClient ( { keyId . process . env . KEAP_KEY_ID , secret . process . env . KEAP_KEY_SECRET } . ; const aws = new AWSClient ( { accessKeyId . process . env . AWS_ACCESS_KEY_ID , secretAccessKey . process . env . AWS_SECRET_ACCESS_KEY } . ;

Next, add a new file called secrets.js to your project directory and add the fplowing code in this file:

exports['myKeapKey'] = { "type". "string", "name". "myKeapKey", "keyId" . "myKeapKeyId", "version". 1, "description". "This is my description" }; 1 2 3 4 5 6 7 export [ 'myKeapKey' ] = { "type" . "string" , "name" . "myKeapKey" , "keyId" . "myKeapKeyId" , "version" . 1 , "description" . "This is my description" } ;

In the above code, we have three properties. type, name, and version. Type is a string data type that represents the type of the data stored in the key. Name represents the name of the key for better understanding purposes. Key id is a unique identifier for the key stored in the Keap system. Version keeps track of how many times data has been modified in the key. In our examples, we have one version, meaning that we only have one piece of information stored in this key. Description represents a description for our specific piece of data stored in this key. In our example, we have a description called “This is my description”.

Next, add a new file called config-example-1a.json to your project directory and add the fplowing code in this file:

{ "auth". { "clientID". "keapplugins", "secret". "z35zkbz9z6z7z4z3z6z9z9z9z6z9z9z9z6z9z9z9z6z9z9z9z6z3z9z9z6z9z9z6z3z9z9z6z3z9z6z3z9z6z3z9z6z3z9z6z3z9z6"} } 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 { "auth" . { "clientID" . "keapplugins" , "secret" . "z35zkbz9z6z7z4z3z6z9z9z9z6z9z9z9z6z9z9z9z6z9z9z6z3z9z9z6z9z6z3z9z9z6z3z9z6z3 zhxPOrfFkLfuXv+HGgWFQtRKcwIq0uEiTy/gNLIYYpCQWUh5L2vT4ykUfjJbVb/Cs5uh3uQ+rq0tlCrDhCwR5GcuQn4H//eFqpVggw=="; }, "path". "/home/admin/secrets", // Path where files are stored in S3 }, "options". { // Optionally define more options for your application here }, "deployment". {} // Optional configuration for deployment on Heroku 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 /* * Your application's configuration * * Place your custom configuration values here so they are available * during runtime of your application on Heroku. */ module . exports = { auth . { clientID . 'keapplugins' , secret . 'thxhxhxhxhxhxhxhxhxhxhxhxhxhxhxhxhxhxhxhxhxhxhxhxhxhxhxhxhh' } , path . '/home/admin/secrets' , options . { region . 'us-east-1' , authMethod . 'apiKey' , domainName . 'example-com' , sslEnabled . true , port . 443 ,

The process to integrate Keap and Downtime Alert may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.