Integrate Using Amazon S3

ChurnZero can connect to an Amazon S3 bucket to easily import data into your tenant. Using this method, ChurnZero will scan a specified bucket that you have authorized to look for files that will then be imported.

Authorize Your S3 Integration

To configure the Amazon S3 Integration, within ChurnZero navigate to Admin>S3 Imports

If you do not see this in your Admin Section, please reach out to your ChurnZero Representative so they can activate this feature for you.

You will then need to specify your settings and authenticate.

• Region- Dropdown selection of which AWS Region the S3 bucket is in
• Bucket Name- An Amazon S3 bucket name is globally unique, and the namespace is shared by all AWS accounts.
• Access Key- Click here to learn more about AWS Security Credentials
• Secret Key- Click here to learn more about AWS Security Credentials
• File Prefix (optional)-If a prefix is provided, only files within the prefix will be used. Use this option if you want to make sure only specific files in a bucket are included for import.

After authentication, notify your ChurnZero representative that you've completed the process. They will turn on the S3 Import. Then, ChurnZero will begin scanning the S3 bucket for files to import. To avoid re-importing files that have already been processed, only those files with a Last Modified Date later than the last run of the import will qualify for processing. ChurnZero looks for new files hourly.

Permissions

In order to utilize this integration, the AWS S3 IAM User tied to the Access Key/Secret Key needs to have the following access in the specific bucket:

• ListObject
• GetObject

File Formats

ChurnZero has 4 Standard Objects that you can import to:

• Account
• Contact
• Event
• Activity

We also support importing to custom objects. To find the name of the Custom Object, in ChurnZero navigate to Admin>Imports. You will see a dropdown with the list of your entity names.

In order to map the files to the correct objects in ChurnZero, a specific naming convention must be followed.  The name of the file must begin with the name of the entity. 

For example, if you want to import a list of Accounts, Account_Import_7-12-21 would be an acceptable file name. 

Similarly, spaces in the Entity name must remain spaces and should not be replaced with dashes, underscores, or other characters. If you have a custom table called "Custom Object," the file name must be "Custom Object," not "Custom_Object." 

For more information on fields required for importing data, please see our article on Batch Imports via CSV

Once you have set up the import process, you can check the Dev Console to see the status of your imports.