AlertFind MySQL Connector

Looking to automate AlertFind Data Import? Yes! this is the place to be. Our MySQL Connector will make automation a breeze! 

In order to perform a successful connection to you MySQL database, we just need the following information and that's it!

  1. Host: This is the name or the IP address of the server where the database is located.

  2. Port: This is the port we use to connect and communicate with the Database.

  3. Database: This is the name of the database we are going to use to fetch the data.

  4. Table: The name of the table or tables we are going to use in order to fetch the data

  5. Username and password: Valid username and password to connect to the database.

  6. SSL certificate, SSL key and SSL certificate authority: please provide this certificates and key in order to perform a secure connection to the database.

Once we have a successful connection, it will enable us to populate your AlertFind instance with information such as:

  • ID
  • First Name
  • Middle Name
  • Last Name
  • Email
  • Personal Email
  • Cell Phone
  • Home Phone
  • Alternate Phone
  • Phone Extension
  • Company
  • Job Title
  • Department
  • Country
  • State
  • City
  • Address
  • Zip Code

How does our MySQL connector works.

The below graphic explains the various nodes involved in the transition of data from your MySQL database to AlertFind.

Detailed Steps Explaining Above Graphic:

  1. MySQL connector fetches the user information stored in your MySQL database via API.

  2. Based on your chosen frequency, our connector running on AWS Lambda fetches data from MySQL database.

  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 into AlertFind API via the AlertFind connector running on AWS Lambda.

Data Storage Nodes in the Graph Above:

  1. 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.

  2. Node 6: Refers to Elastic Search Cluster used for indexing data for 30 days so that it can be searched within the logs interface.

  3. Data Safety: All Data is encrypted in transit using HTTPS, using TLS 1.3 encryption internally. Sensitive customer data, such as access tokens, usernames, passwords are encrypted at rest using Amazon Key Management Service (KMS), which uses FIPS 140-2 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.

AlertFind Connector List