Tuesday Tech Bytes - Workfront 01 - Enhancing Workfront with WalkMe using webhooks

[#1]

While members of this community are certainly familiar with Workfront and Fusion, WalkMe may be a bit misterious. So first few words about this app.

WalkMe is a digital adoption platform designed to simplify the user experience on websites and software applications. It offers on-screen guidance and interactive walkthroughs to help users navigate and utilize digital tools efficiently. Key features include:

1. Guidance and Support: Provides step-by-step tutorials and tooltips to guide users through processes.

2. User Onboarding: Introduces users to the features and functionalities of the platform or application.

3. Behavioral Analytics: Provides insights into how users are using the software, identifying pain points and areas for improvement.

4. Customization: To match business specific needs and branding.

5. Integration: making it versatile for various industries and use cases.

Overall, WalkMe aims to enhance user engagement, reduce training costs, and increase overall productivity by making digital tools more intuitive and accessible.

Today I'm focusing on Integrations.

One of integrations available with WalkMe are webhook integrations. This allows to send a portion of data from one app to another in a very efficient way. In our use case we utilize this feature to trigger an automation in Fusion, collect some of the data from the triggering user and save that Workfront (being our system of record)

Here is step by step guide on how you can build this and similar integrations:

1. Create Fusion scenario with custom webhook module as triggering module

2. Create a webhook, simply by clicking "add". The only required value is webhook name

Created webhook's URL will be visible in module settings

3. Use WalkMe's Insights page to navigate to integrations, choose Webhooks

4. Create New Webhook, by providing it's name (can be anything)

5. Configure Webhook by providing Event details that will trigger the webhook.
In this example webhook will be triggered anytime a user clicks on the Launcher with ID 123456

Launcher - is an object that you can place anywhere in WalkMe, we refer to them as "buttons", because that's how they effectively work, as buttons.

6. Continue webhook configuration by providing Destination details
You can specify request type (we are using POST), in Destination URL you paste the webhook URL that we generated in Fusion. By default no authorization is required, but it can be added (same with additional Header properties).

Once you are set with the configuration and assuming your Fusion webhook is enabled you can run a test and you will receive some sample data

The solution is pretty much ready to use. Previously mentioned launcher can be placed anywhere in the system. We use one of them in documents are to facilitate the delivery process.

The rationale behind this is that we want to capture few more details regarding the task and the user when document is being sent to the requestor. Not all of the required details can be simply saved when user changes task status to Completed. That's why we decided to use this integration to trigger a custom automation in Fusion that collects and saves all the required details. Additionally level of customization for WalkMe launchers allows them to match look and feel of Workfront sometimes making them indistinguishable from native Workfront buttons. This positively influences the user experience.

References:

https://www.walkme.com/technology/

QA: use the thread below to ask questions