Open Source Community Connector requirements

You should first review the Publishing overview to understand the different publishing options as well as their differences in benefits and required level of commitment. This will help you to choose the right publishing option for your connector.

If you want to publish your connector as an Open Source Community Connector, you must meet the following requirements before requesting a pull request.

  1. Add a file to your code. You do not need to include a deployment link. See readme of npm Downloads as an example.
  2. Add JSDoc comments.
  3. Manifest should contain values for shortDescription, authType, supportUrl, and feeType.
    • Note that supportUrl can either be for Data Studio developer relations or your own should you choose to support it yourself.
  4. You should populate the sources property with all the sources your connector connects to. See Sources in Manifest reference for details.
  5. You should limit the number of endpoints called by UrlFetchApp in your connector to those absolutely required for connector functionality. Add the urlFetchWhitelist property to the root level of your manifest. View the urlFetchWhitelist reference for more info.
    • This property should contain all URLs your connector connects to using the UrlFetchApp call.
    • If your connector does not execute a UrlFetchApp call then set the property value to an empty list [].
  6. If you connector has a fixed schema, create a report template for your connector and add it to the manifest.
  7. Provide meaningful and actionable error messages to users when users encounter a Connector internal error. This includes cases when user provides invalid/blank input at configuration.
  8. Ensure you and your connector adhere to the Data Studio Galleries Terms of Service (Submitter).

Once you have met all the requirements, click the following button to request a review for your connector:

Publish your Open Source Community Connector