Schedule Flow doesn't work in Collections Request

Hello community!

I did the following procedure and it is not working:

  • I created a flow with, and placed the start block with “Takes input of any type”.
  • I created a Webhook and published it.
  • I created an HTTP POST request with the WebHook URL

When I try to send a manual POST request, or schedule it via Monitor, it doesn’t work. It returns 200 and the message below, but my flow is not executed.

{
    "event": "6786c64e213e7357e532e853",
    "timestamp": 1736885837900,
    "state": "processing",
    "message": "A flow run has started for this webhook call"
}

If I send it via WebHook Preview, it works perfectly.

Hi @rfbento

Welcome to the forums!

The 200 response code just indicates that the flow has been triggered successfully. The flow runs as an asynchronous process after that point. The preview runs the flow locally as opposed to on our cloud, so if you need to be on a VPN for your APIs or refreshing OAuth tokens via the authorization tab, your flow will fail in the cloud.

If you press the three dots next to the publish button below your flow url, you can view the published version, then trigger your flow and it should show you the live logs of your flow including any errors.

Let me know if you run into any trouble finding the issue.

Hi Daniel!

I trigged my flow, after click on “View the published version”, and that is the return log:

@rfbento

Looks like your flow is running, but hitting a 403 on a couple of your API calls, are you using OAuth for those requests?

i’m using a basic auth:


And have this error in the response body:
Access denied | ******** used Cloudflare to restrict access

@rfbento

Looks like the endpoints have some restrictions that are fine when being run from your computer, but not the Postman Cloud. Are these private endpoints?

@flows-daniel
The endpoints are private, can i do anything to get around this?
Are blocked by Cloudfire firewall.

Hi @rfbento

Unfortunately, we don’t have a way around it today, but you can still run the flows locally.

This is something on our roadmap. I can update the thread here once we have a solution for it.