> For the complete documentation index, see [llms.txt](https://help.meltingspot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.meltingspot.io/english/how-to/add-new-members-of-your-spot-to-a-google-sheet.md). # Add new members of your Spot to a Google Sheet Pass your spot's data to a data table! ## Connecting Make to MeltingSpot Setting up Make with MeltingSpot is very easy. No need to code, just follow these steps: 1. Register with Make (or log in if you already have an account). 2. Click on "Create a new scenario". 3. Click on the "+". 4. Search and select "Webhook" and then "Custom webhook". The event allows you to start a scenario with a specific application. In our case, it is MeltingSpot that manages the tracking of this event, so the scenario must simply listen to what MeltingSpot will send it. 5. Click on "Add" and name your hook, for example "NewLiveParticipant". Click on "Save". 6. Get the URL by clicking on "Copy address to clipboard". Be careful, don't click on "Ok" yet, wait until you have launched a test on the MeltingSpot side!Write a caption {% embed url="" %} Connecting your Make to a MeltingSpot webhook {% endembed %} 7. [Create your webhook](/english/manage-spot/integrations/webhooks.md) on MeltingSpot by selecting "New member created" and using the URL retrieved in the previous point. 8. Do a Test on the MeltingSpot side. 9. Go back to Make and click on Ok. That's it, your scenario is connected with MeltingSpot! ## Define the action Now that your trigger is set up, you can use the information sent by MeltingSpot to Make to trigger "actions". You can perform thousands of different actions with Make. You can add as many actions as you need in a scenario. 1. Add a module by clicking on "Add another module". 2. Choose Google Sheet then "Add a Row". 3. Sign in to your Google account 4. Choose the file and the sheet corresponding to your spreadsheet. 5. Fill in your columns with the data sent by MeltingSpot. {% embed url="" %} 6. Do a test run to make sure your scenario works. To do this, click on "Run once" and then go to MeltingSpot and run a test from your Spot settings. 7. Finally, publish your scenario like this: ![](https://3055204660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrzBxnWaSListMwx3rzKu%2Fuploads%2Ft4qdeW9BqVdceq87dcAS%2Fimage.png?alt=media\&token=53e46292-ca96-4b34-b7e6-1d3f4998e6fa) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.meltingspot.io/english/how-to/add-new-members-of-your-spot-to-a-google-sheet.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.