I created an automation guide to help you trigger Make.com from Google Sheets without relying on the extension. This method will get your automations back on track swiftly and efficiently.
Many users have faced issues with automations due to the absence of the Make.com extension for Google Sheets. This sudden change has disrupted workflows and left many searching for solutions. Fortunately, there are effective methods to restore functionality without relying on the extension.
Creating a webhook is one of the simplest and quickest ways to re-establish your automations. This approach allows you to trigger Make.com directly from Google Sheets, enabling you to continue working seamlessly.
Creating a Webhook
To start, I created a custom webhook on Make.com. This process is straightforward. First, I navigated to Make.com and selected “New Scenario.” From there, I chose “Webhook.” The next step involved adding a webhook and saving it.
Once I saved the webhook, I copied the generated address to my clipboard. This URL is crucial as it will be used to trigger the webhook from Google Sheets.
Setting Up the Webhook Connection
Now that I have the webhook URL, it’s time to set up the connection in Google Sheets. I typed “hyperlink” in a cell, followed by an opening quotation mark, and pasted the copied URL. This creates a clickable link in the sheet. I also added a label for the link, like “Trigger Make.com,” to make it user-friendly.
After setting up the hyperlink, I saved the changes and ran the function once. This action opened the link in a new tab, where I accepted the request. Once I returned to the Google Sheets document, I confirmed that the webhook had been successfully triggered.
Testing the Webhook
Testing is crucial to ensure that everything works correctly. After successfully triggering the webhook, I needed to pass meaningful data to Make.com. This is where the real power of the webhook comes into play.
I started by considering how to pass data effectively. If a unique identifier is available in the sheet, I could use it to retrieve specific information. This involves adding a question mark to the webhook URL followed by a query parameter, for example, “ID=” followed by the unique identifier.
After modifying the URL, I returned to Make.com and pressed “Run Once.” I selected the button in Google Sheets to send the request again. Now, the ID was successfully received within Make.com.
Passing Data to Make.com
Once the webhook is successfully set up and tested, I focused on how to pass data to Make.com. I went to Google Sheets and selected “Search Rows.” Here, I chose my spreadsheet and specified the sheet name. Limiting the search to one entry is vital to avoid unnecessary data processing.
Next, I set the filter to the ID I passed through the webhook. After saving these settings, I ran the function again. This time, I clicked the button to trigger the webhook, and I was pleased to see that the value was successfully retrieved from Google Sheets.
With the value now available in Make.com, I could perform various actions. I could update the row, trigger another system, or use the data for further processing. Having an ID or some identifier is essential for referencing specific data entries effectively.
In cases where a unique ID isn’t available, I could pass other relevant information, such as an email address or status. To do this, I updated the URL to include parameters for the email and status. After constructing the URL correctly, I ran the function once more to see if the data was accepted.
Ultimately, this approach allows for flexibility in how data is passed to Make.com. Whether using a unique ID or other parameters, you can create a functional link that triggers actions based on the data in your Google Sheets. This method is particularly useful for users who previously relied on the Make.com extension.
Searching Rows in Google Sheets
After setting up the webhook, I focused on how to effectively search for rows in Google Sheets. This step is essential for retrieving the specific data needed for further processing.
I accessed the “Search Rows” feature in Google Sheets. Here, I selected my spreadsheet and specified the sheet name. Limiting the search to one entry is crucial to streamline the process and avoid unnecessary data retrieval.
Next, I set a filter based on the unique ID I previously passed through the webhook. This filter allows me to pinpoint the exact row I want to interact with. After configuring the settings, I saved the changes and ran the function again.
Upon triggering the webhook, I was pleased to see that the correct value was successfully retrieved from Google Sheets. This ability to search for specific rows enhances the overall efficiency of the automation process.
Using Unique IDs
Unique IDs play a vital role in this automation process. They help identify specific rows in Google Sheets, ensuring that the correct data is accessed and manipulated.
By using unique IDs, I could pass relevant information through the webhook directly to Make.com. This method allows for precise targeting of data entries, making the automation more effective.
In my setup, I ensured that each row had a unique identifier. This way, whenever I triggered the webhook, I could easily reference the exact row needed for further actions.
Alternatives to Unique IDs
Sometimes, you might not have a unique ID available. In such cases, there are alternatives to ensure that you can still pass meaningful data to Make.com.
- Email Addresses: If your data includes email addresses, you can use them as identifiers. By passing the email through the webhook, you can filter data based on this criterion.
- Status Fields: Another option is to use status fields. If your rows contain status information, this can also serve as a reference point for data retrieval.
For both options, I updated the webhook URL to include the email or status parameters. After constructing the URL correctly, I ran the function to confirm that the data was accepted.
Creating a Custom Apps Script
If you’re looking for a more advanced setup, creating a custom Google Apps Script is a great option. This approach allows for greater flexibility and sophistication in your automations.
I started by accessing the Apps Script editor from the Extensions menu in Google Sheets. Here, I could write scripts that trigger my Make.com scenario based on specific actions, such as updating a dropdown list.
With a custom script, I could automate various tasks beyond what the webhook offers. For example, I could set triggers to run the script automatically when certain conditions are met, streamlining my workflow even further.
