Implementing handlers and authentication
So, we're now able to add our application to Journey Builder, load our application UI, and both save and initialize our activity data within Journey Builder for further processing and configuration. Now, we need to actually do something on the application side with the payloads configured from Journey Builder. To do this, we'll examine some of the contents of our activity.js file in order to determine how to create the final pieces of functionality.
Before we can begin, we need to complete one final piece of configuration for our application. Since we only want our execute method to process if we've identified that the request is coming from Journey Builder, we'll need to decode and authenticate the JSON Web Token posted to our execute route. To accomplish this, first, we'll navigate back to our installed package within Marketing Cloud.
In the primary package details, we'll want to copy the value of the JWT...