How to Enable Private Component API on Connect Plan and Alternatives for Running Custom Component Logic?

1

This topic was automatically generated from Slack. You can find the original thread here.

Hey! We’re on the Connect plan and running into the private component API 403 when we try to run our own published components through Connect:

“Private component API not enabled for this organization”

Publishing works fine, it’s just running them that gets blocked — looks like a per-org flag. I’ve seen this flipped for other Connect customers without an upgrade,
so hoping we can do the same :pray:

Two quick things:

  1. Could you enable it for our org?
  2. If that’s not possible — is there any other supported way to run custom component logic through Connect, or is the Proxy really the only route?

Thanks so much!

2

Hi,

Can you open a support ticket for this? pipedream.com/support

Or if you’ve already opened it, let me know

3

yes i just opened a ticket

4

i have one more question why doesnt pipedream have a meta ads mcp?

5

I believe we’ve had this requested before and it’s blocked, but you can follow it here: Meta Ads · Issue #21039 · PipedreamHQ/pipedream