This topic was automatically generated from Slack. You can find the original thread here.
I’m having trouble with using pipedream connect auth in a workflow. I’ve verified that im passing in the external id and development status, I’ve verified the external id matches what i have in my user database in the pipedream project. I’m not sure what else I should be trying to debug. The error from klaviyo is **Message:GoneTotal Duration:4,190 msExecution Start:2025-01-06T00:49:30.046ZExecution End:2025-01-06T00:49:34.236ZSteps Executed:1 / 1credits:1Version:**3 (d_qjsdPz7P)
I’m sorry to hear you’re having trouble with Pipedream Connect and Klaviyo. The error message you’re encountering, “Message: Gone,” typically indicates that the resource you’re trying to access is no longer available at the specified endpoint. Here are a few steps you can take to troubleshoot this issue: 1. Verify Endpoint URL: Double-check the URL you’re using in your API request to ensure it’s correct and still valid. Sometimes, endpoints can change or be deprecated. 2. Check API Key: Ensure that the API key you’re using is correct and has the necessary permissions to access the endpoint. 3. Review Klaviyo Documentation: Consult the Klaviyo API documentation to ensure you’re using the correct endpoint and request format. 4. Debugging with Pipedream Connect: Since you’re using Pipedream Connect, make sure that the external_user_id and other parameters are correctly set. You can enable verbose error messages by configuring the HTTP trigger to “Return a custom response from your workflow.” This might give you more insight into what’s going wrong. 5. Contact Support: If you’re still experiencing issues, you can reach out to Pipedream support for further assistance. Visit Support - Pipedream for more support options. If you have any additional details or need further assistance, feel free to provide more information!
ah so that’s the issue - I was using the prebuilt “get lists” node to test the auth, and the node must be depreciated because once I tested the “create list” node it worked perfectly.
