Skip to content

Latest commit

 

History

History
 
 

meetup

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
src
src
 
 
.clasp.json
.clasp.json
 
 
README.md
README.md
 
 
package.json
package.json
 
 
yarn.lock
yarn.lock
 
 

README.md

Meetup Community Connector for Data Studio

This is not an official Google product

This Data Studio Community Connector lets users query data from Meetup.

This connector uses the Meetup API.

Set up the Community Connector for personal use

To use this Community Connector in Data Studio there is a one-time setup to deploy your own personal instance of the connector using Apps Script. The connector also requires additional setup in Meetup to configure OAuth.

1. Deploy the connector

Follow the deployment guide to deploy the Community Connector.

Make a note of the Script ID for the connector, you'll need it for the next step.

  • To find your Script ID, Visit Apps Script, then click on File -> Project Properties, and you'll see the id under the Info tab.

2. Meetup OAuth Configuration

The Meetup connector requires an OAuth 2.0 client. Follow the steps below to complete the connector setup.

  1. In Meetup, go to Your OAuth Consumers page.

  2. Click Create New Consumer.

  3. Complete the form, use the following table for guidance:

    Text Field Response
    Consumer Name Meetup Community Connector
    Application Website https://github.com/googledatastudio/community-connectors
    Redirect URI https://script.google.com/macros/d/{YOUR_SCRIPT_ID}/usercallback

    Note: While you can choose your own values for "Consumer Name" and "Application Website", you must follow the pattern for the "Redirect URI" in the table above.

  4. Visit Apps Script and open your Meetup connector Apps Script project. Click on File -> Project Properties -> Script Properties. Using the information obtained from Meetup, add the following key-value pairs as script properties:

    Key Value
    OAUTH_CLIENT_ID {YOUR CLIENT ID}
    OAUTH_CLIENT_SECRET {YOUR CLIENT SECRET}

Using the connector in Data Studio

Once you've set up and deployed the connector, follow the Use a Community Connector guide to use the connector in Data Studio.

Note: After using the connector in Data Studio, as long as you do not revoke access, it will remain listed in the connector list for easy access when creating a new data source.

Troubleshooting

This app isn't verified

When authorizing the community connector, if you are presented with an "unverified" warning screen see This app isn't verified for details on how to proceed.

Developer examples covered in the connector

  • Manual Defined Semantics Example of how you can manually define the semantics for your schema fields.
  • OAUTH2 Authentication Example of how to authenticate with 3rd party OAUTH2, in this case, Meetup's's OAUTH2 service.
  • Using Project Properties Example of how to use Project Properties (Specifically Script Properties) to save data needed for script execution. Script Properties are useful in situations where values are needed for script execution, but shouldn't be put into source files. In this case, we put an OAUTH2 "client id" and "client secret" into the Script Properties.
  • Testing Your Connector Example of how you can use regular javascript testing strategies for Community Connectors.

Testing

To test the connector run yarn install && yarn test