Get started with a free trial today
Already have an account? Sign in
A high-level look at Stitch's Responsys (v1) integration, including release status, useful links, and the features supported in Stitch.
| STITCH | |||
| Release status | Released on January 17, 2019 | Supported by | |
| Stitch plan | Standard | Supported versions | n/a |
| API availability | Available | Singer GitHub repository | |
| CONNECTION METHODS | |||
| SSH connections | Supported | SSL connections | Unsupported |
| REPLICATION SETTINGS | |||
| Anchor Scheduling | Supported | Advanced Scheduling | Supported |
| Table-level reset | Unsupported | Configurable Replication Methods | Unsupported |
| REPLICATION METHODS | |||
| Log-based Replication | Unsupported | Key-based Replication | Supported |
| Full Table Replication | Unsupported | ||
| DATA SELECTION | |||
| Table selection | Supported | Column selection | Unsupported |
| View replication | Unsupported | Select all | Supported |
| TRANSPARENCY | |||
| Extraction Logs | Supported | Loading Reports | Supported |
To set up Responsys in Stitch, you need:
Export files that adhere toStitch’s requirements. Files that aren’t set up correctly may not be replicated successfully, or may cause issues during extraction.
Stitch uses an SSH tunnel to securely connect to your Responsys SFTP server. This means that to connect successfully, you’ll need to add Stitch’s Public Key to your server.
The Stitch public key will be at the top of the page that opens:

Next, you’ll need to add the public key to your SFTP server. The steps for doing this depend on how your SFTP server is hosted:
Contact Oracle and provide them with the public key to complete this step.
If your SFTP server is self-hosted, or not hosted by Oracle, you’ll need to add the public key to theauthorized_keys file. This will allow Stitch to conntect to the server using a trusted user.
Open a new terminal window and log into your SSH server.
Create a group namedstitch:
sudogroupadd stitchCreate a user namedstitch:
sudouseradd-m-g stitch stitchSwitch to thestitch user:
sudosu - stitchCreate the.ssh directory:
mkdir ~/.sshUsingchmod, alter the permissions of the directory to allow access:
chmod700 ~/.sshNavigate to the.ssh directory:
cd ~/.sshUsingtouch, create theauthorized_keys file:
touchauthorized_keysSet the permissions forauthorized_keys:
chmod600 authorized_keysImport theStitch public key intoauthorized_keys, replacing<PUBLIC KEY> with the public key. Verify after replacing the key that it is on one line and doesn’t contain line breaks:
echo"<PUBLIC KEY>">> ~/.ssh/authorized_keysIf you skip this step or the Public Key is added incorrectly, the following error will surface when you save the integration in Stitch:
"Message from SFTP server: Authentication failed. - Please ensure that the server is configured to accept the public key for this integration."
Stitch’s Responsys integration replicates.csv or.txt files created as part of aConnect data export job. In the Responsys app, jobs are created and managed in theManage Connect page, accessed viaData > Connect.
File settings are defined in theDestination Specification step of the Connect data export process, which can be seen in the image to the right.
The settings in theDestination Specification page must match the required values listed in the table below. This will ensure that data is replicated successfully from Responsys.
| Setting in Responsys | Required value |
| File to be created | We recommend using adate/time prefix OR suffix for file names, which will result in Responsys creating multiple files. If a prefix or suffix isn’t used, the export will only ever create a single file. Every new export will replace the entire file, overwriting the data it contains. If this occurs before Stitch runs an extraction job, the overwritten data would be lost and unable to be replicated. |
| File extension | .csv or.txt Stitch’s Responsys integration doesn’t currently support replicating other file types. |
| Character set | Unicode (UTF-8) |
| File delimiter | Comma Stitch’s Responsys integration doesn’t currently support other file delimiters. |
| Field enclosure | Double quotes ( |
| Insert column header as first line | Box must be checked Stitch’s Responsys integration requires that the first row of every export file be a column header. |
| Encryption/compression | Do not encrypt or compress file Stitch’s Responsys does not currently support replicating encrypted or compressed files. |
| Additional ready file at completion of download | SelectCreate file with record count. In theFile extension field, enter |
In this step, you’ll complete the setup by entering the connection details and defining replication settings in Stitch:
The info you need to complete the remaining fields depends on how your SFTP server is hosted:
If your server is hosted by Oracle, you can find its connection details in the Responsys app by navigating toData > Connect > Destination Connectivity. If you have multiple file locations, click the one you want to connect to Stitch.

The image on the right shows an example of the connection details in Responsys.
Fill in the remaining fields in Stitch as follows:
files.responsys.net22.demo_scpdownloadIf your server is hosted by Oracle, you can find its connection details in the Responsys app by navigating toData > Connect > Destination Connectivity. If you have multiple file locations, click the one you want to connect to Stitch.

The image on the right shows an example of the connection details in Responsys.
Fill in the remaining fields in Stitch as follows:
22.stitch_userThe Sync Historical Data setting defines the starting date for your Responsys integration. This means that dataequal to or newer than this date will be replicated to your data warehouse.
Change this setting if you want to replicate data beyond Responsys’s default setting of1 year. For a detailed look at historical replication jobs, check out theSyncing Historical SaaS Data guide.
In theReplication Frequency section, you’ll create the integration’sreplication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
Responsys integrations support the following replication scheduling methods:
Advanced Scheduling using Cron (Advanced or Premium plans only)
To keep your row usage low, consider setting the integration to replicate less frequently. See theUnderstanding and Reducing Your Row Usage guide for tips on reducing your usage.
The last step is to select the tables you want to replicate.
Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.
For Responsys integrations, you can select:
**Individual tables **
All tables and columns
Click the tabs to view instructions for each selection method.
Repeat this process for every table you want to replicate.
Click theTables to Replicate tab.
Navigate to the table level, selecting any databases and/or schemas that contain tables you want to replicate.
In the menu that displays, clickTrack AllTables and Fields (Except Views):

After you finish setting up Responsys, itsSync Status may show asPending on either the Stitch Dashboard or in the Integration Details page.
For a new integration, aPending status indicates that Stitch is in the process of scheduling the initial replication job for the integration.This may take some time to complete.
Initial replication jobs with Anchor Scheduling
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to theAnchor Scheduling documentation for more information.
The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.
While data from Responsys integrations is replicated usingKey-based Incremental Replication, the behavior for this integration differs subtly from other integrations.
The table below compares Key-based Incremental Replication andReplication Key behavior for Responsys to that of other integrations.
| Responsys | Other integrations | |
| What's replicated during a replication job? | The entire contents of a modified file. | Only new or updated rows in a table. |
| What's used as a Replication Key? | The time a file is modified. | A column or columns in a table. |
| Are Replication Keys inclusive? | No. Only files with a modification timestamp value greater than the last saved bookmark are replicated. | Yes. Rows with a Replication Key valuegreater than or equal to the last saved bookmark are replicated. |
Responsys tables will contain the same columns that the source files contains. These tables will also containcommon system columns, as well as columns specific to Responsys integrations:
| _sdc_source_file | Applicable only to Intacct and Responsys integrations, this column contains the file path on the SFTP server of the table’s source file. |
| _sdc_source_lineno | Applicable only to Intacct and Responsys integrations, this column contains the row number for the record in the source file. |
| Related | Troubleshooting |
Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.