Actions for Freshworks #
- Send Data to Freshworks. Sends a custom set of Lucidum data to Freshworks.
Use Cases #
Below are the possible use cases for these actions:
-
If you want to run Lucidum “headless”, you can send relevant data to Freshworks on a regular schedule.
- You can send normalized, enriched Lucidum data to Freshworks to be indexed, searched, and analyzed.
Prerequisites #
To execute Freshworks actions, you must configure a Freshworks 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
Freshworks Configuration #
To create a configuration for Freshworks actions:
-
Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.
- URL. The URL of the Freshworks API server. For example, https://lucidum.freshservice.com.
-
API Key. The API Key for a user account with read and write access to the Freshworks API. For details on finding the API Key for Freshservice, see https://api.freshservice.com/#authentication. For details on finding the API Key for Freshdesk, see https://developers.freshdesk.com/api/#getting-started.
-
Max # of Records per Payload. The maximum number of records to send to Freshworks in each action. The default value is “50”.
Create a New Action #
To create an action for Freshworks, contact Lucidum customer care.
