This topic was automatically generated from Slack. You can find the original thread here.
Browserless Integration Using Legacy Endpoint - Causing 403 Errors
Issue Description:
The Browserless integration in Pipedream is routing requests to a legacy endpoint that no longer works, causing 403 errors with the message: “This URL is a legacy endpoint, please use https://production-sfo.browserless.io for REST API calls”
Technical Details:
Integration: Browserless app integration in Pipedream
Error: 403 Forbidden with legacy endpoint message
Expected Behavior: Requests should route to https://production-sfo.browserless.io
Actual Behavior: Requests are being routed to an old/legacy endpoint
Error Message: “This URL is a legacy endpoint, please use https://production-sfo.browserless.io for REST API calls and wss://production-sfo.browserless.io for library and puppeteer usage. See more at https://docs.browserless.io/overview/connection-urlss”
Steps to Reproduce:
Create a workflow with a Browserless step
Use any Browserless action (e.g., _makeRequest with /function endpoint)
Execute the step
Observe 403 error with legacy endpoint message
Impact:
This prevents any Browserless automation from working in Pipedream workflows, making the integration unusable.
Expected Resolution:
Update the Browserless integration to use the current production endpoint: https://production-sfo.browserless.io
Urgency: High - This affects all users trying to use Browserless for browser automation