Actions for Recorded Future #
- Send Data to Recorded Future. Sends a custom set of Lucidum data to Recorded Future.
Use Cases #
Below are the possible use cases for these actions:
-
If you want to run Lucidum “headless”, you can send relevant data to Recorded Future on a regular schedule.
- You can send normalized, enriched Lucidum data to Recorded Future to be indexed, searched, and analyzed.
Prerequisites #
To execute Recorded Future actions, you must configure a Recorded Future API connection beforehand.
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
Recorded Future Configuration #
To create a configuration for Recorded Future actions:
-
Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.
-
URL. The URL of the Recorded Future API. For example, https://api.recordedfuture.com
-
API Token. API token for an account with read and write access to the Recorded Future APIs. For details, see https://support.recordedfuture.com/hc/en-us/articles/11305261649555-Recorded-Future-Sandbox-Obtaining-an-API-Access-key. For details on roles and permissions, see https://sandbox.recordedfuture.com/docs/cloud-api/users/#:~:text=to%20delete%20themselves.-,POST%20/users/%7BuserID%7D/apikeys,present%2C%20it%20is%20returned%20instead.
-
Max # of Records per Payload. The maximum number of records to send to Recorded Future in each action. The default value is “50”.
Create a New Action #
To create an action for Recorded Future, contact Lucidum customer care.
