Connectors

From Memsource
Jump to: navigation, search

Introduction

Users can set up connection between Memsource Cloud and FTP, SFTP, WordPress, Drupal, Zendesk, Dropbox, Google Drive, Microsoft OneDrive, Box, Git and GitHub* (online repositories) in order to be able to manually import content from these online repositories when creating new jobs in projects, or to automatically import new content from these repositories.

* Due to API limitations enforced by GitHub, GitHub connector cannot be used for Automated project creation.

Editions with Access to Connectors

The connectors are available in the following editions:

Connector/Edition Personal 1+Freelancer Team Start Team Ultimate BIZ Start BIZ Team Unlimited
Box × × × × × ×
Dropbox × × × × × × ×
Drupal × × × × × ×
FTP × × ×
Git × × × × × ×
GitHub × × × × × ×
GitLab × × × × × ×
Google Drive × × × × × × ×
Marketo × ×
Microsoft OneDrive × × × × × × ×
SFTP × × ×
Wordpress × × × × × ×
Zendesk × × × ×

Setting up the Connectors

To setup individual connectors, navigate to Setup > Integrations > Connectors. After clicking on New you can choose the connector you wish to create.

Box

The following fields are required to setup Box connector:

  • Name
  • Type (Box)

Click on Connect to Box to open a pop-up window. Insert your Box credentials and click on Authorize. If the credentials are correct, a tick will appear next to the Connect to Box button.

Dropbox

The following fields are required to setup Dropbox connector:

  • Name
  • Type (Dropbox)

Click on Connect to Dropbox to open a pop-up window. Insert your Dropbox credentials and click on Sign in. If the credentials are correct, a tick will appear next to Connect to Dropbox button.

Drupal

The Drupal connector requires a Drupal Plugin that needs to be installed on the site. Please follow the instructions in the link above to setup your Drupal Plugin correctly. The Drupal Connector currently supports the following types of content:

  • Posts
  • Pages

The following fields are required to setup Drupal connector:

  • Name
  • Type (Drupal)
  • Drupal site URL (this URL should be the same as is used to access your site, without the /login endpoint).
  • Memsource Drupal plugin token (generated in Drupal once the plugin is installed).

Click on Test Connection to see if the credentials are correct and if Memsource can reach the site successfully.

FTP

The following fields are required to setup FTP connector:

  • Name
  • Type (FTP)
  • Host
  • Port (21 automatically set by Memsource)
  • User name
  • Password
  • Encryption - you can choose from the following methods:
  * Use explicit FTP over TLS if available (recommended)
  * Require explicit FTP over TLS
  * Require implicit FTP over TLS
  * Only use plain FTP (insecure)

Click on Test Connection to see if the credentials are correct and if Memsource can reach the site successfully.

Git Connectors

There are currently three different connectors to the Git service accounts: Git, Github, GitLab. They refer to the same entity, but in terms of authentication and access, they are different.

Git

Git is the underlying direct repository where documents can be stored. When setting up this connector, the access is allowed only to the specific repository. The following fields are required to setup Git connector:

  • Name
  • Type (Git)
  • Host (please note the URL must lead to the actual Git repository. It will have .git as an endpoint).
  • User name
  • Password
  • SSH key (optional)
  • SSH passphrase (optional)
  • Commit message

GitHub

GitHub serves as a web access point to multiple GIT repositories. Using this connector will allow access to all repositories associated with the GitHub account. This connector operates similarly to Google Drive or Dropbox Connectors (in terms of authentication and establishing the connection). The following fields are required to setup GitHub connector:

  • Name
  • Type (GitHub)
  • Commit message

Click on Connect to GitHub to open a pop-up window. Insert your GitHub credentials and click on Sign in. If the credentials are correct, a tick will appear next to ‘’’Connect to GitHub’’ button.

Note: The GitHub connector cannot be used in Automatic Project Creation due to the API request limit on the GitHub side.

GitLab

GitLab, unlike GitHub, allows for the use of REST APIs and thus requires a more complicated setup. To establish a connection, you first need to create access token in GitLab:

  • Log into your GitLab account and navigate to Settings > Access Tokens
  • Fill in the Name and Expires at (we suggest setting a longer time period to avoid frequent re-creation of tokens).
  • Under Scopes tick api and read_user
  • Clicking on Create personal access token will generate token that needs to be copied (please note this token is visible only at this stage and can not be reached afterwards).

With the access token correctly created and copied, navigate back into Memsource to establish the connector. The following fields are required to setup GitLab connector:

  • Name
  • Type (GitLab)
  • GitLab site URL (the same URL where the Access token was generated)
  • GitLab personal access token
  • Commit message

Google Drive

The following fields are required to setup Google Drive connector:

  • Name
  • Type (Google Drive)

Click on Connect to Google Drive to open a pop-up window. Insert your Google Drive credentials (or select the account you wish to link) and click on Sign in. You will be asked if you want to allow Memsource to access the files on your google Drive. Click on Allow to establish a connection. Once the connection has been established correctly, a tick will appear next to Connect to GitHub button.

Google Drive Troubleshooting

It may happen that the validation in your Google account expires (you will see a red exclamation mark next to the connector). You may need to re-open the connector and click on Connect to Google Drive again. If this does not help establish connection either, log in to your Google Drive, and click on My Account - Connected apps & sites (under Sign-in & security) - MANAGE APPS, and REMOVE your Memsource Connector app from the list. The next attempt to re-authenticate your connection will be successful.

Marketo

To enable the communication between Memsource and Marketo, REST APIs need to be enabled in the Marketo account. In order to do this, please refer to the Marketo documentation. Marketo Connector currently supports the following type of content:

  • Emails
  • Files
  • Forms
  • Landing pages

Marketo Client ID, Client Secret and Identity

Once the REST API is enabled, follow the steps below to obtain necessary information to acquire information needed in Memsource Connector:

  • In your Marketo account, navigate to Admin > Integration > LaunchPoint > View Details
  • Copy the Client ID and Client Secret (preferably to a text document for easier reference later)
  • Close the dialog and navigate to Integration > Web Services
  • In the REST API section, find the Identity row. It will have a value like http://000-ABC-111.mktorest.com/identity.
  • Copy the Host Prefix (in this case 000-ABC-111) preferably into a text document for easier reference later

Memsource Connector

The following fields are required to setup Marketo connector:

  • Name
  • Type (Marketo)
  • Marketo API key (Client ID in Marketo)
  • Marketo API secret (Client Secret in Marketo)
  • Marketo API identity URL (http:// and .mktorest.com/identity are filled automatically by Memsource)

Microsoft OneDrive

The following fields are required to setup Microsoft OneDrive connector:

  • Name
  • Type (Microsoft OneDrive)

Click on Connect to Microsoft OneDrive to open a pop-up window. Insert your Microsoft OneDrive credentials and click on Sign in. After you Allow Memsource to connect to your OneDrive and the connection was established correctly, you will see a tick next to the Connect to OneDrive button.

SFTP

The following fields are required to setup SFTP connector:

  • Name
  • Type (SFTP)
  • Host
  • Port (22 automatically set by Memsource)
  • User name
  • Password

Click on Test connection to see if the credentials are correct and if Memsource can reach the site successfully.

WordPress

The WordPress connector requires the WordPress Plugin to be installed on the website as well as WPML, so that multilingual sites can be created. (The multilingual CMS version of WPML is required). To set up the WordPress plugin, please see our WordPress Plugin page. The Wordpress Connector currently supports the following types of content:

  • Posts
  • Pages
  • Tags
  • Categories

The following fields are required to setup WordPress connector in Memsource:

  • Name
  • Type (WordPress)
  • WordPress site URL (general URL used to access the site, without /wp-admin endpoint)
  • Memsource WordPress plugin token

Click on Test connection to see if the credentials are correct and if Memsource can reach the site successfully.

Zendesk

To establish a connection to Zendesk, languages first need to be set in the Zendesk account. To do so, log into your Zendesk account and navigate to Settings > Account > Localization. Once the languages are set, you can go back to the Memsource account and navigate to Setup > Integrations > Connectors. The following fields are required to setup Zendesk connector:

  • Name
  • Type (Zendesk)
  • Host prefix (the https:// and .zendesk.com parts of the URL are automatically inserted by Memsource, only the prefix needs to be prefilled - e.g. mysupportsite for https://mysupportsite.zendesk.com)

Creating New Jobs from Online Repositories

Adding Job from Online Repository
  1. Go to the New Job page
  2. Click on Add from Online Repository
  3. Choose the online repository you want to use
  4. Select the file/files in the same way as when selecting from your local disk
  5. Click on Create to create a new job

Exporting Completed Jobs to Online Repositories

Adding Job from Online Repository

For jobs imported from an online repository, there will be a new command available under Download - Export to Online Repository

  1. Select the files you want to export
  2. Click on Export to Online Repository
  3. The completed files will be sent back to the online repository from which they were imported, renamed according to the syntax you select under File Renaming.

Please note that FTP does not provide auto-rename. If the File Renaming is turned off, the exported document will overwrite the source file.

Troubleshooting

A connector can sometimes become invalid (marked by a red exclamation mark icon) due to various reasons:

  • The authorization token expires after a long inactivity
  • Users revoke the access
  • Users change their credentials for a remote service (Dropbox, Google, ...)

If this is the case, the connector edit dialog will show a Re-authenticate button with which users will be able to re-establish their connection to the online repository in question.