CDK Global

CDK Global dealer management systems produce file exports that a dealership group can use for reporting, warehouse loads, and exchange with other systems. Files.com receives or collects those exports, decrypts them when required, and delivers them to the locations each consumer reads. CDK continues to own the source data and the export configuration.

CDK's Data Export and Import Tools support scheduled predefined data sets delivered to SFTP, with PGP protection. This file-transfer arrangement uses the export service available to the dealer. CDK's separate API products provide other ways to access records; configuring Files.com does not enable those products or replace their access requirements.

Export Destination

Establish the receiving location with the team administering the CDK export. The connection depends on where that approved export already lands:

For direct delivery, create a dedicated machine account with SFTP enabled and upload permission to the receiving folder. Supply the SFTP hostname, port, and host key, and register the export client's SSH public key if it uses key authentication. Use the directory as it appears to that account, including any configured client root.

For an existing receiving server, use its operator-provided hostname, port, credentials, and host key in an SFTP Remote Server. This preserves the CDK delivery arrangement while Files.com handles the next transfer.

Collection From an Internal Server

Run the Files.com Agent on a machine that can reach the internal SFTP service and connect outward to Files.com. Enable SFTP routing, then select that Agent as the route on the Remote Server. The existing SFTP host remains internal; the Agent makes the connection from its network.

An Agent route does not replace the SFTP account. The Remote Server still needs credentials permitted to list and download the export folder, and the internal service must allow the connection from the Agent host.

Use a Sync to collect a separate copy, or a Mount when a Files.com workflow needs to work against the remote files. Keep the source exports until their collection and any required recovery copy have been verified. A Sync's option to delete after copying removes the source; it does not wait for a warehouse to accept the data.

Decryption and Warehouse Staging

Import the private key for encrypted exports into the GPG Key Manager. The CDK export uses the matching public key. Collect the encrypted source into an intake folder, then use an Automations v2 Decrypt With GPG node before delivering its output to the loader's ready location. The node retains the encrypted original and passes the decrypted file to the next node; configure a failed item to stay off the delivery path.

For Snowflake, files can be made available through the Files.com S3-Compatible Endpoint or delivered to the storage used by an existing ingestion process. For example, a group that already loads Snowflake from Azure Blob can keep that arrangement and use Files.com to collect, decrypt, and deliver each CDK export to the Azure staging location. The warehouse still owns loading and table updates.

Use separate locations for dealership or data-set exports when their consumers or permissions differ. Giving a vendor a pickup folder grants access to the files placed there; it does not select the records that vendor is entitled to receive. Produce that subset in the export or an explicit transformation before delivery.

Delivery and Load Evidence

Verify the complete path with one representative export: CDK creates it, Files.com collects it, decryption succeeds, and the intended staging location receives it. Then confirm the loader accepted it. Compare the expected reporting period and dealership with the loaded result before making the run recurring.

Expectations can detect a missing scheduled export. Sync run and file-event records identify collection or delivery failures. Use the warehouse's ingestion history to diagnose a delivered file that did not become usable data.