Actions for Cyderes #
- Send Data to Cyderes. Sends a custom set of Lucidum data to Cyderes.
Use Cases #
Below are the possible use cases for these actions:
-
If you want to run Lucidum “headless”, you can send relevant data to Cyderes on a regular schedule.
- You can send normalized, enriched Lucidum data to Cyderes to be indexed, searched, and analyzed.
Prerequisites #
To execute Cyderes actions, you must configure a Cyderes 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
Cyderes Configuration #
To create a configuration for Cyderes actions:
-
Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.
- URL. URL of the Cyderes API endpoint.
-
API Token. Token for a Cyderes account with read and write access to the API.
-
Max # of Records per Payload. The maximum number of records to send to Cyderes in each action. The default value is “50”.
Create a New Action #
To create an action for Cyderes, contact Lucidum customer care.
