In order to perform a successful connection to your FreshService instance, we just need the following information and that's it!
1. FreshService subdomain name: This is the first part of your FreshService URL for example, if your FreshService URL is customername.freshservice.com the subdomain would be "customername".
2. Access Token: This access token is like an API key and can be found under the settings of the instance using an admin account.
Once we have a successful connection, it will enable us to populate your AlertFind instance with the following information:
- Job Title
- Time Zone
How does our FreshService connector works
The below graphic explains the various nodes involved in the transition of data from your FreshService instance to AlertFind.
Detailed Steps Explaining Above Graphic:
1. FreshService connector fetches the User Information stored in your instance via API.
2. Based on your chosen frequency, our connector running on AWS Lambda, fetches data from FreshService instance.
3. At this stage, data goes through the validation and processing and is finally transformed into a CSV.
4. The CSV is compressed to a ZIP file and sent to AlertFind API via the AlertFind connector running on AWS Lambda.
Data Storage Nodes in Above Graphic:
- Node 5: Refers to Apache Cassandra Cluster which stores the data for execution purposes. It has a TTL of 7 days after workflow execution finished.
- Node 6: Refers to Elastic Search Cluster used for indexing data for 30 days so that it can be searched within the logs interface.
- Data Safety: All Data is encrypted in transit via HTTPS, using TLS 1.3 encryption internally. Sensitive customer data, such as access tokens, usernames, passwords are encrypted at rest using Amazon Key Management Services (KMS), which uses FIPS 140-2 validated hardware security modules.
We encourage you to keep searching the connector that suits your needs in our main AlertFind Connector List under the section System of Records Integrations by clicking the button below.