Actions for KnowBe4 #
- Send Data to KnowBe4. Sends a custom set of Lucidum data to KnowBe4.
Use Cases #
Below are the possible use cases for these actions:
-
If you want to run Lucidum “headless”, you can send relevant data to KnowBe4 on a regular schedule.
- You can send normalized, enriched Lucidum data to KnowBe4 to be indexed, searched, and analyzed.
Prerequisites #
To execute KnowBe4 actions, you must
Configure a KnowBe4 API connection beforehand. The required parameters are described in the instructions for creating a KnowBe4 connector in Lucidum https://lucidum.io/docs/knowbe4/.
NOTE. The specified account should have read and write permissions.
Workflows #
- Creating a new Configuration and a new Action
- Cloning an Existing Action
- Creating a new Action from the Location Results page
- Editing a Configuration
- Editing an Action
- Viewing Information about an Action
KnowBe4 Configuration #
To create a configuration for KnowBe4 actions:
-
Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.
- URL. The URL for the KnowBe4 API. For details, see https://developer.knowbe4.com/rest/reporting#tag/Base-URL.
-
API Key. The API Key for an account with read and write access to the users/groups/training data. For details, see https://support.knowbe4.com/hc/en-us/articles/12769050560403-KnowBe4-Console-Account-Settings-Account-Integrations.
-
Max # of Records per Payload. The maximum number of records to send to KnowBe4 in each action. The default value is “50”.
Create a New Action #
To create an action for KnowBe4, contact Lucidum customer care.
