AI-generated Key Takeaways
-
The
appsscript.jsonmanifest file provides essential information about your Apps Script connector for deployment and usage in Looker Studio. -
It includes required fields like connector name, company details, URLs, description, and optional fields for enhanced functionality and user experience.
-
The manifest supports specifying authentication type, fee type, data sources, and report templates, allowing for customization and integration.
-
You need to whitelist any external URLs your connector accesses using the
urlFetchWhitelistproperty for security purposes. -
All information included in the manifest file is publicly accessible, so avoid including any sensitive data.
The manifest ( appsscript.json
) is a JSON file in your Apps Script connector
project. It contains certain information about your Community Connector
that is required to deploy and use your connector in Looker Studio. Read more
about manifests in Apps Script
.
Your manifest should contain the following information:
dataStudio
property)name
string
Limited to 28 characters
company
string
companyUrl
string (link)
logoUrl
string (image link)
The required dimensions are 40px by 40px.
addOnUrl
string (link)
This page must contain or link to your Terms of Service and Privacy Policy.
supportUrl
string (link)
description
string
Users will see the full description in your connector configuration page. Links will be clickable.
dataStudio
property)shortDescription
string
privacyPolicyUrl
string (link)
termsOfServiceUrl
string (link)
list( Sources
)
templates
Object
default
key. The value should be the report ID for the Looker
Studio report that will be used as the template. See the guide on Providing
report templates
.forceViewersCredentials
boolean
false
. See Data
source credentials
for more details on viewer's credentials.useQueryConfig
boolean
advancedServices.data
boolean
advancedServices.schema
boolean
urlFetchWhitelist
list(string)
AuthType
The values for authentication method type can be one of the following:
| Enum Value | Description |
|---|---|
NONE
|
Indicates there is no authentication required for the connector. |
OAUTH2
|
Indicates the connector uses OAuth 2.0. |
KEY
|
Indicates the connector uses API key. |
USER_PASS
|
Indicates the connector uses username/password. |
USER_TOKEN
|
Indicates the connector uses username/token. |
PATH_USER_PASS
|
Indicates the connector uses path/username/password. |
PATH_KEY
|
Indicates the connector uses path/key. |
FeeType
The values for fee type can be any of the following:
| Enum Value | Description |
|---|---|
FREE
|
Indicates the connector is completely free to use. |
FREE_TRIAL
|
Indicates the connector has a free trial option. |
PAID
|
Indicates the user will need to pay to use the connector. |
Sources
Sources is a list of enums for sources. You can view the existing list of
sources at our Data Registry Repository
. If the source you are connecting to
does not exist in the repository, send a pull request to the Data Registry
Repository
to add the source. The source name can contain only uppercase
characters and underscores (e.g. Google Analytics will be GOOGLE_ANALYTICS
).
In your Community Connector manifest, use the valueof the data source id
property, e.g. GOOGLE_ANALYTICS
.
Example manifest for a Community Connector
The following is an example of a completed manifest:

