This topic was automatically generated from Slack. You can find the original thread here.
I am trying to add use the add single row step on Google Sheets with the Spreadsheet ID being a return path from a previous step (steps.node.$return_value.spreadsheetID). The Google Sheets account is correct, the drive is correct, the ID is correct, I have manually added the Sheet Name custom expression as “Sheet1” – and I am still getting an Error:
Requested entity was not found.
Based on the information you’ve provided, it seems like you’ve correctly set up the “Add Single Row” step in your Google Sheets workflow on Pipedream, including specifying the Spreadsheet ID dynamically from a previous step. However, you’re encountering an “Requested entity was not found” error. This error typically indicates that the Google Sheets API could not locate the spreadsheet with the given ID or access the specified sheet within the spreadsheet. Here are a few things to check and try to resolve this issue: 1. Verify Spreadsheet ID: Ensure that the Spreadsheet ID returned from steps.node.$return_value.spreadsheetID is correct and matches exactly with the ID of the spreadsheet you’re trying to access. You can compare this ID with the one in the spreadsheet URL to confirm. 2. Check Sheet Name: You’ve mentioned setting the Sheet Name to “Sheet1”. Ensure that this matches exactly with the name of the sheet in your spreadsheet, including case sensitivity. If the sheet has been renamed or if there’s a typo, it could lead to this error. 3. Google Sheets API Permissions: The error might also occur if the Google Sheets API does not have the necessary permissions to access the spreadsheet. Ensure that the Google account connected to Pipedream has access to the spreadsheet and that the required OAuth scopes are included. According to the Pipedream documentation, the following scopes are configured for Google Sheets: - https://www.googleapis.com/auth/drive - https://www.googleapis.com/auth/spreadsheets If your workflow requires modifying or accessing spreadsheets, make sure the Google account used has been granted these permissions. 4. Google Drive File Access: Since the spreadsheet is stored in Google Drive, ensure that the Google account connected to Pipedream has the necessary permissions to access the file in Google Drive. Sometimes, the spreadsheet might be in a shared drive or folder with restricted access. If after checking these points the issue persists, you might want to try reconnecting your Google account to Pipedream or using a static Spreadsheet ID and Sheet Name to test if the issue is specifically related to dynamic values. If none of these steps resolve the issue, I recommend reaching out to Pipedream support for further assistance. You can get more support options by visiting Support - Pipedream.
all of these have been checked. All permissions are good. All other steps / operations with google sheets work. The sheet name is correct. The spreadsheet ID is correct.
It seems like you’re experiencing an issue with a specific operation involving Google Sheets, but the details of the problem aren’t clear from your message. Since you’ve confirmed that permissions, sheet name, and spreadsheet ID are correct, and other operations with Google Sheets are working, it might be a specific issue with the operation you’re trying to perform. Could you please provide more details about the operation you’re attempting with Google Sheets? For example, are you trying to read from a sheet, write to it, or perform some other action? Additionally, if you’re encountering an error message, could you share it? This information will help me provide a more accurate solution.
Okay, so I just tested it without the “Does the first row of the sheet have headers” ticket to Yes. I can add rows to my spreadhsheet when this is turned off – but the problem is that it takes the formatting and styling of my header row when it adds the row. For some reason, setting the option to yes prevents this automation from working.
It seems like you’re encountering an issue with adding rows to a spreadsheet where the formatting and styling of the header row are being applied to the new rows. This issue arises when the “Does the first row of the sheet have headers” option is not set correctly. Unfortunately, without more specific details about the platform or tool you’re using to automate the addition of rows to your spreadsheet, it’s challenging to provide a precise solution. However, if you’re working within a Pipedream workflow and interacting with a spreadsheet service (like Google Sheets, Excel, etc.), here are a few general steps you might consider: 1. Review the Integration Documentation: Check the documentation for the specific spreadsheet service you’re using within Pipedream. This might provide insights into how the service handles headers and row formatting. 2. Check the Automation Settings: Ensure that the settings or parameters you’re using in your automation correctly specify how headers should be treated. This might involve setting a specific parameter to indicate whether the first row contains headers. 3. Use Formatting Actions: If you’re facing issues with formatting being copied from the header row, consider using separate steps or actions in your Pipedream workflow to adjust the formatting of newly added rows. While the provided documentation doesn’t directly address spreadsheet formatting, you might find actions within the Formatting app that can help manipulate or reset text formatting as a workaround. 4. Test with Different Configurations: Experiment with different configurations for adding rows to your spreadsheet. This might include manually specifying column names or indices when adding new rows to see if that bypasses the issue with header formatting being applied. 5. Seek Further Assistance: If you continue to encounter issues, consider reaching out for more support. You can visit Support - Pipedream for more help. Without more specific details about the spreadsheet service you’re using or the exact nature of your Pipedream workflow, these suggestions are quite general. If you can provide more information about the services involved and the steps in your workflow, I might be able to offer more targeted advice.