This article describes how you can leverage Okta Workflows to push visitors and their metadata into Pendo. Okta Workflows allow you to automatically update visitor metadata on a scheduled basis.
This method is specific to collecting employee metadata. While this typically involves a browser extension (Pendo Launcher) implementation, you can also use this method for a direct implementation using the install script, as long as the metadata you're collecting is employee metadata.
Workflow Template files, which you can download here.
Pendo Admin user permissions.
Okta Workflows Super Admin user permissions.
Create Okta and Pendo connections
You need to set up two Connection applications, one for Okta and one for the Pendo Launcher.
- In Okta, navigate to the Connections tab.
- Select + New Connection and then select the pink Pendo connector.
- Name the connector in the Connection Nickname field. The integration key is generated in Pendo.
- In Pendo, navigate to Settings > Integrations > Integration Keys.
- Select + Add Integration Key. Add a meaningful name for the key, select Allow Write Access, then select Create and copy the new integration key.
- Return to Okta Workflows and paste the integration key into the Integration Key field, then select Create. This completes adding the Pendo connector. The Pendo application displays a green check mark to indicate that the connection to the application is working.
- Select + New Connection to add the Okta connector. Select the blue Okta connector.
- Complete the Connection Nickname, Domain, Client ID, and Client Secret fields according to Okta's Connect your applications article. This creates the Okta connector. The Okta connector appears as an application in your Connections tab. The new application displays a green check mark to indicate that the connection to the application is working.
Create a new folder
- In Okta Workflows, select the blue plus button to create a new folder and name it.
- Select the gear (settings) icon next to the new folder and import the workflow template files.
- Download workflow template files.
- Turn on each of the Helper flows (flows that begin with the label SubFlow)
- Open the Load Temp Table into Pendo subflow.
- In this subflow, confirm the Pendo connection points to the connection that you set up, as outlined in the Create Okta and Pendo connections section.
- Select the Options dropdown underneath the Connections field.
- Email is the default key for identifying your visitors in Pendo. If you use a field other than email to identify your users in Pendo, change this value to match that field. The key passed into this field is passed into Pendo as the Visitor ID, not as a metadata field.
- Optionally, create users in Pendo who exist in Okta but haven't installed the Pendo Launcher extension. Select the Create Non-existing User dropdown in the Push User List with Metadata card and select Yes. When Yes is selected, Okta adds the visitor into Pendo if the user doesn't already exist as a visitor in the subscription. The newly created visitor's metadata is visible in the Visitor's agent block.
- Open the flow titled Event-Triggered Load - User Creation.
- In both the User Created and the List Users with Filter cards, confirm your Okta connection has been selected. No other configuration is necessary.
- In the Push Okta User List with Metadata card, confirm your Pendo connection is selected. Configure the same Visitor ID Key and Create Non-existing Users settings as the Load Temp Table into Pendo subflow.
- Repeat steps 7 and 8 for the Event-Triggered Load - User Update flow.
- Select Bulk Load - Read All Okta Users and Sync to Pendo.
- Navigate to the List Users with Filter card and confirm your Okta connection has been selected. No other configuration is necessary.
Configure Custom Metadata Fields
- Select the SubFlow - Get User Keys flow.
- Navigate to the List Users with Filter card and confirm your Okta connection is selected.
- Select the play button labeled Test this card and run the test.
- In the Raw Output box, there is a field called profile. The fields inside the profile object are the Okta fields that can be pushed to Pendo. Take note of which fields you want to import. The names are case-sensitive.
- Add the fields you took note of in the previous step by adding a new item field in the List Construct card. Keys passed into the item field are the keys passed into Pendo.
- Select Save in the top-left corner of the screen.
Activate data flow
Important: The following steps begin pushing metadata from Okta to Pendo. Verify all previous steps are completed correctly before continuing.
- Turn on both the Event-Triggered Load - User Creation and Event-Triggered Load - User Update cards using the toggle in the ON/OFF column.
- Select the Bulk Load - Read All Okta Users to Pendo and Sync to Pendo card.
- Select the Test button to execute this flow. This is not actually a test. This action loads all of your users into Pendo. It takes 30 to 60 seconds for every batch of 500 users.
Note: If you expect to load more than 50,000 users into Pendo, you might encounter timeout or memory overflow issues on Okta. If you do encounter this issue, contact your Pendo representative for support batch-loading your users.
Configure metadata types
The metadata fields you've configured in Okta appear in the Metadata table in Data Mappings. Navigate to Settings > Data Mappings > Visitor Level Data and configure the Type for each metadata field. In the example, below, okta_email has the Type set to Text.
It can take 15 minutes after your first batch completes for new fields to populate.
Each metadata field configured in Okta has an "okta" prefix so it's easily identifiable. You can rename these fields. After they're configured, you can use them in custom segments, which you can use throughout Pendo.