This topic was automatically generated from Slack. You can find the original thread here.
Hello, I am getting an error message on the last step of my workflow, which is a Shopify / CRM integration. Can someone help me fix it? Total newbie here and feeling pretty lost! Thanks a lot 
:skin-tone-2:
any idea?
It seems like your question is incomplete. Could you please provide more details or clarify what you need help with? This will help me provide the most accurate and helpful response.
:
âShopify developer appâ step shows the following error message:
Error
Request failed with status code 404
DETAILS
at null.createError (/var/task/node_modules/@lambda-v2/component-runtime/node_modules/axios/lib/core/createError.js:16:15)
at null.settle (/var/task/node_modules/@lambda-v2/component-runtime/node_modules/axios/lib/core/settle.js:17:12)
at IncomingMessage.handleStreamEnd (/var/task/node_modules/@lambda-v2/component-runtime/node_modules/axios/lib/adapters/http.js:269:11)
at IncomingMessage.emit (node:events:530:35)
at null.endReadableNT (node:internal/streams/readable:1696:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
:
âShopify developer appâ step shows the following error message:
Error
Request failed with status code 404
DETAILS
at null.createError (/var/task/node_modules/@lambda-v2/component-runtime/node_modules/axios/lib/core/createError.js:16:15)
at null.settle (/var/task/node_modules/@lambda-v2/component-runtime/node_modules/axios/lib/core/settle.js:17:12)
at IncomingMessage.handleStreamEnd (/var/task/node_modules/@lambda-v2/component-runtime/node_modules/axios/lib/adapters/http.js:269:11)
at IncomingMessage.emit (node:events:530:35)
at null.endReadableNT (node:internal/streams/readable:1696:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Based on the error message youâre encountering with the Shopify Developer App step in Pipedream, it appears that the request is failing due to a 404 Not Found error. This typically indicates that the URL being requested does not exist on the server. Given the context, there are a few potential reasons and solutions for this issue: 1. Incorrect Shop ID or API Version: Ensure that the shop_id and the API version in the URL are correct. Shopify API versions are updated regularly, and using an outdated or incorrect version can lead to a 404 error. The example provided in the documentation uses the API version 2023-07. Double-check that this matches the current API version required for your request and that the shop_id is correctly configured in your Shopify Developer App settings on Pipedream. 2. Access Token Issues: A 404 error can sometimes be related to authentication issues. Verify that the access token being used is valid and has not expired. Ensure that the access token is correctly being passed in the request headers. 3. Endpoint URL: Double-check the endpoint URL structure. The URL should follow the format https://[shop_id].[myshopify.com/admin/api/[version]/[endpoint]](http://myshopify.com/admin/api/[version]/[endpoint]). Ensure that there are no typos or missing segments in the URL. 4. Permissions: Ensure that your Shopify Developer App has the necessary permissions to access the endpoint youâre trying to reach. Lack of permissions can sometimes manifest as a 404 error. Hereâs a revised version of the example code snippet, with comments highlighting areas to check: ``` import { axios } from â@pipedream/platformâ export default defineComponent({ props: { shopify_developer_app: { type: âappâ, app: âshopify_developer_appâ, }, customerEmail: { type: âstringâ, label: âCustomer Emailâ } }, async run({steps, $}) { return await axios($, { // Ensure the shop_id and API version are correct url: https://${this.shopify_developer_app.$auth.shop_id}.[myshopify.com/admin/api/2023-07/customers/search.json](http://myshopify.com/admin/api/2023-07/customers/search.json), headers: { // Verify the access token is valid âX-Shopify-Access-Tokenâ: ${this.shopify_developer_app.$auth.access_token}, âContent-Typeâ: application/json,
does the answer from Pi help?
Iâm still having trouble. Thereâs now an error in node_1 :
TypeError â Cannot read properties of undefined (reading âline_item_global_product_idsâ)
Based on the error message youâve provided, it seems like youâre trying to access a property line_item_global_product_ids of an object that is undefined. This typically happens when youâre trying to access a property of an object that hasnât been initialized or doesnât exist in the context youâre expecting. Hereâs a general approach to troubleshoot and potentially resolve this issue: 1. Check Object Initialization: Ensure that the object youâre trying to access is properly initialized before you try to access its properties. If this object is supposed to come from an external source (like an API response), make sure that the response is being correctly received and parsed. 2. Existence Check: Before accessing the property, you can add a check to see if the object exists. This can prevent the error from occurring by not attempting to access a property on an undefined object. if (yourObject && yourObject.line_item_global_product_ids) { // yourObject exists and has the property line_item_global_product_ids // Safe to access yourObject.line_item_global_product_ids } else { // Handle the case where yourObject or line_item_global_product_ids doesn't exist } 3. Debugging: Add console.log statements before the error occurs to inspect the object youâre trying to access. This can give you insights into why itâs undefined. console.log("Inspecting the object:", yourObject); 4. Review Data Flow: Trace back where yourObject is supposed to be set or modified. There might be a logical flow where itâs not being set as expected. Without specific details about your workflow or the context in which line_item_global_product_ids is being accessed, these are general suggestions. If youâre still facing issues, please provide more context or code snippets related to where and how line_item_global_product_ids is being accessed in your Pipedream workflow. This will help in providing a more targeted solution.
OK thanks , Iâm also getting this error in node2:
TypeError â Cannot read properties of undefined (reading âvariantidsâ)
The error message youâre encountering, TypeError â Cannot read properties of undefined (reading 'variantids'), typically occurs when you try to access a property (variantids in this case) on an object that is undefined. This could happen for a few reasons in your Pipedream workflow, such as: 1. The object from which youâre trying to read variantids hasnât been properly initialized or assigned. 2. The step prior to node2 (where youâre encountering the error) might not be returning the expected data, leading to undefined. 3. There might be a typo or logical error in your code thatâs causing the object to be undefined. Without seeing the specific code or knowing the context of your workflow, itâs difficult to provide a precise solution. However, here are a few general steps you can take to troubleshoot and potentially resolve the issue: 1. Check the Output of the Previous Step: Ensure that the step immediately before node2 is returning data as expected. You can add a console.log statement to log the output of that step and verify that it includes the object with variantids. 2. Validate Object Existence Before Accessing Properties: Before trying to access variantids, check if the object youâre trying to access it from is defined. For example: if (steps.previousStepName.data && steps.previousStepName.data.yourObject) { const variantIds = steps.previousStepName.data.yourObject.variantids; // Proceed with your logic using variantIds } else { console.log('The expected object is undefined.'); } Replace previousStepName with the actual name of the step before node2, and yourObject with the actual object youâre expecting to contain variantids. 3. Review Your Code for Typos: Ensure that there are no typos in the property name variantids and that youâre correctly referencing the step outputs. If after trying these steps youâre still encountering issues, it might be helpful to provide more context or share a snippet of your workflow where the error occurs. This way, I can offer more targeted advice.