The current workaround to this feature request is

Scheduling runs with Postman monitors

https://learning.postman.com/docs/running-collections/scheduling-collection-runs/

1) Export from a database - ExportList - https://developer.goacoustic.com/acoustic-campaign/reference/export-from-a-database

LIST_ID - Unique identifier for the database, query, or contact list Acoustic Campaign is exporting.

2) Get and configure the API from our Postman Collection - https://developer.goacoustic.com/acoustic-campaign/reference/postman-collection

Setup

• Create Oauth App and Refresh token for Postman - https://help.goacoustic.com/hc/en-us/articles/360043157333-Application-account-access

Configure example collection scripts

• Authentication(Oauth)-->Generate an Access Token

and

• Contact Management-->Bulk Export contact data

Additional notes

Acoustic Campaign SFTP access should be authenticated before setup - https://help.goacoustic.com/hc/en-us/articles/360042859494-SFTP#a1