In order to perform a successful connection to your Zendesk instance, we just need the following information and that's it!
- Zendesk Subdomain: This represents the first part of your Zendesk URL. For example : If your Zendesk URL is aureademo.zendesk.com, then the subdomain would be aureademo.
- Email Address: Email address belonging to an Admin in your Zendesk account.
- API Key: An API key token for your Zendesk account. API tokens are managed in the Zendesk Admin interface at Admin > Channels > API.
Once we have a successful connection, it will enable us to populate your AlertFind instance with the following information:
- Time Zone
How does our Zendesk Connector works :
The graphic below explains the various nodes involved in the transition of data from your Zendesk instance to AlertFind.
Detailed Steps Explaining Above Graphic:
- Zendesk connector fetches the User Information stored in your Zendesk instance via API.
- Based on your chosen frequency, our connector running on AWS Lambda fetches data from Zendesk.
- At this stage, data goes through validation and processing and is transformed into a CSV.
- The CSV is compressed into 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 has finished.
- Node 6 : Refers to Elastic Search Cluster used for indexing data for 30 days so that it can be searched within the log’s 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 and passwords are encrypted at rest using Amazon Key Management Service (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.