AlertFind Chargify Connector

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

In order to perform a successful connection to your Chargify instance, we just need the following information and that's it! 

1. API Key: This API Key can be found in the settings of the instance or can be generated with an Admin account.
   
   
2. Subdomain Name: This is the first part of your Chargify url for example, if your Chargify url is customername.chargify.com the subdomain would be “customername”.
   
   

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

1. First Name  
2. Last Name  
3. Email 
4. CCemail  
5. Phone  
6. Country 
7. State 
8. City  
9. Address 1  
10. Address 2  
11. Zip Code  
12. Organization  
13. Reference  
14. ID
    
    

How does our Chargify connector works :

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

Detailed Steps Explaining Above Graphic :

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

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

AlertFind Connector List