Mainstay Sync for Slate

Overview

Integrations allows institutions to connect their Mainstay data to a third-party platform, such as Slate. Whether you're using the Inbound, Outbound (Contacts), or Outbound (Conversations) sync, this support article can help you navigate the Slate interface.

Inbound (Slate → Mainstay)

1. If an IP Address is needed instead, the Mainstay server's host resolves to a static IP of 34.235.9.62
2. In Slate, use the Schedule Export tool. (See https://knowledge.technolutions.com/hc/en-us/articles/360033654991-Scheduling-Exports.)
   1. Use the Hostname, Username, Password, and Port from the Mainstay SFTP credentials as the Connection for your recurring export. This should generally be in this format:
      • sftp://username:password@hostname:port
   2. Use the default settings - Secure Transfer, Delimited, Comma, Include header row, Unicode, etc.
   3. Select the fields you would like to be exported to Mainstay.
   4. In the Requested Delivery section, select the times and days you would like that data to be exported to Mainstay.
3. In the Mainstay Data Mapping section, type the column headers as they will appear in your Slate export file. For example, the Slate id might be called "ref". 

Outbound (Mainstay → Slate)

1. In Slate, create a new Source Format.
   1. On Mainstay, download the Contacts Report, and upload this CSV.
   2. Map each of the Mainstay fields to the corresponding Slate fields, as desired. This ensures that when Slate receives a file, it is able to ingest the data correctly.

   3. In the Source Format, under the “Import Automation” tab, the Import Path/Mask may have to be added before the import will process the file automatically. This field tells Slate which files to process based on location (folder and file name). If using the default file names that look like “mainstay_contact2026-09-01T235350411Z.csv“, setting the Import Path/Mask to "mainstay*.csv" (with the asterisk as a wild card) should be sufficient to kick off the automation and pull only the Mainstay files.
      
      Under the "Format Definition" tab, the following XML may need to be entered so that Slate knows to parse the file as a csv, with a header row, and double quotes around each element: 

      <layout b="," h="1" t="&quot;" />

2. Navigate to the Slate SFTP Access configuration. You will need this information for authentication.
   • Note that your Slate set-up might require you to specify Allowed Networks. Data exports for this integration should come from 34.197.84.241 and 3.233.244.171.
   • Additionally, if you restrict access to specific folders, be sure to use a leading slash.

Conversations (Mainstay → Slate)

1. Ensure that you are already saving the AdmitHub/Mainstay ID for the Contact records. (See the Outbound section above for more information.) 
   • 
2. Map the Conversation imports to the Interactions record type. Make sure to match the admithub_id column to the same field AdmitHub/Mainstay ID field you're using for contact records.
   • 
3. For the Import Configuration, specify the Import Automation's Path/Mask. Ensure this matches the path entered on the Mainstay configuration above.
   • Note: This field already assumes the path starts with /incoming, so you should not enter that here or else it will incorrectly apply to /incoming/incoming/desired_path_to_file/file_name.csv
   • 
4. In the General tab, match the following configuration:
   •