Each time at 4am, I create a spreadsheet from a template then I store the ID of the worksheet in my data stores with the key name “daily_sheet”. This workflow work well (the double quote are here to force pipedream to use the id as a string and not a json):
First, I thought the variable format in my data storage wasn’t correct but when I try different action like
“get file by id” or “get spreadsheet by id” and giving the return value from the data storage, it work
It looks like you’re encountering an issue where the “Add Single Row” action in your workflow isn’t accepting the spreadsheet ID from a variable, even though other actions like “Get File by ID” and “Get Spreadsheet by ID” work fine with the same variable.
This issue might be related to how the variable is being passed or interpreted in the “Add Single Row” action. Here are a few steps and potential workarounds to help resolve this issue:
Step-by-Step Solution
Verify the Variable Format:
Ensure that the variable storing the spreadsheet ID is in the correct format. It should be a string. You can add a code step to log the type and value of the variable to confirm this:
Use a Code Step to Pass the ID:
Instead of directly using the variable in the “Add Single Row” action, you can use a code step to pass the ID. This ensures that the ID is correctly formatted and passed to the action.
If the above steps do not resolve the issue, you can use the Google Sheets API directly in a code step to add a row to the spreadsheet. Here’s an example:
import { axios } from "@pipedream/platform";
export default defineComponent({
props: {
google_sheets: {
type: "app",
app: "google_sheets",
},
I'm a bot powered by Pipedream and GPT-4. I'm still learning, so please double-check my answers and code! [Learn how to build your own](https://pipedream.com/blog/build-your-own-chat-bot-with-openai-and-pipedream/).
This is known and expected. The reason is that we calculate the props we will show and allow user configuration depending on the spreadsheet columns. Since each spreadsheet can be different, if you supply a custom expression for the ID of the spreadsheet, there isn’t a way for us to reliably allow user configuration when the next spreadsheet ID can have a different column structure.
In summary, this Google Sheets action does not allow a custom expression for the Spreadsheet ID.