This topic was automatically generated from Slack. You can find the original thread here.
#C04TFD4LB36 is pipedream support facebook and meta ads ?
At this time, there is no direct evidence in the provided documentation that Pipedream has a pre-built integration for Facebook or Meta Ads (such as triggers or actions specifically for Facebook Ads or Meta Ads). What does this mean for you? - You cannot currently use a pre-built Pipedream trigger or action for Facebook Ads or Meta Ads directly from the Pipedream UI. - However, you can still connect to the Facebook or Meta Ads API using custom code steps in Pipedream (Node.js or Python), as long as you have the necessary API credentials and follow Facebook’s API documentation. If you want a native integration: If you’d like to see a direct Facebook Ads or Meta Ads integration in Pipedream, you can submit a request at New Pipedream Integration Request. Summary: - No pre-built Facebook/Meta Ads integration in Pipedream right now. - You can use custom code to connect to their APIs. - Request an official integration if you need it. Let me know if you’d like an example of how to connect to the Facebook Ads API using a code step!
#C04TFD4LB36
The Pipedream Connect picker in my project (proj_xxxxx, environment=production) only shows
"Facebook Pages" and "Facebook Graph API (Beta)" when I search "facebook". It does NOT show
"Meta Ads", but the API at
https://api.pipedream.com/v1/connect/tokens/<token>/validate?app_id=meta_ads
returns a valid record for app_id app_ywheya / name_slug meta_ads.
Why is meta_ads visible via the catalog API but not in my Connect picker? Is it gated by:
(a) my account plan tier,
(b) the project's environment (production vs development),
(c) a Pipedream-managed OAuth app that doesn't exist for my project,
(d) something else?
Tell me concretely what I'd have to do to make meta_ads appear in my picker.
Based on your question and the available documentation, here’s a step-by-step analysis and answer: — ### Why is “Meta Ads” visible via the catalog API but not in my Connect picker? You’re seeing meta_ads as a valid app in the API, but it does not appear in your Connect picker UI. This usually means the app is registered in Pipedream’s backend, but is not enabled or visible in your current workspace/project context. #### Possible gating reasons: 1. Account plan tier (a): - Some apps are classified as Premium Apps and require a paid plan to use in active workflows. - However, “Meta Ads” is not listed in the current Premium Apps list in the documentation, so this is less likely unless it was recently added or is in a private beta. 2. Project environment (b): - Some integrations may be restricted to certain environments (development vs. production), but there’s no public documentation indicating “Meta Ads” is environment-gated. 3. Pipedream-managed OAuth app (c): - If “Meta Ads” requires a Pipedream-managed OAuth client and that client is not configured or available for your workspace/project, the app may not appear in the picker. - This is a common reason for apps to be “hidden” in the UI but present in the backend. 4. Other gating (d): - The app could be in private beta, invite-only, or require manual enablement by Pipedream staff. - Sometimes, new or experimental integrations are only available to specific users or workspaces. — ### What should you do to make “Meta Ads” appear in your picker? Concretely: - Contact Pipedream support to request access or clarification. Since the app is visible in the API but not in your UI, it likely requires manual enablement or is in a restricted state. - Visit Pipedream and submit a ticket explaining your situation, referencing your project and environment, and mentioning that the API returns a valid record for meta_ads but it does not appear in your Connect picker. — #### Summary Table | Gating Reason | Likelihood | Action Needed | |--------------------|------------|------------------------------------------------| | Plan tier | Possible | Upgrade plan if required, but not likely cause | | Environment | Unlikely | No public docs on env gating | | OAuth app missing | Likely | Contact support for enablement | | Private/beta state | Likely | Contact support for access | — ### Apology and Support Sorry for the confusion and inconvenience. For the fastest resolution, please contact Pipedream support with your details—they can clarify the gating and enable “Meta Ads” for your workspace if possible. — In summary: “Meta Ads” is likely hidden due to a gating mechanism (private beta, missing OAuth app, or manual enablement). Contact Pipedream support to request access or clarification.
#C04TFD4LB36
When a user connects the `facebook_graph_api` connector via Pipedream Connect (the in-app iframe),
what is the exact list of OAuth scopes Pipedream requests from Meta?
Specifically: does the default Pipedream-managed OAuth for facebook_graph_api include
`ads_management`, `ads_read`, or `business_management`? If not, which scopes does it include?
If those ad-related scopes are NOT in the default, what's the path to add them?
OAuth Scopes for facebook_graph_api on Pipedream When a user connects the facebook_graph_api connector via Pipedream Connect (the in-app iframe), Pipedream requests the following OAuth scopes from Meta by default: ```
email public_profile pages_manage_engagement pages_manage_posts pages_show_list pages_read_user_content pages_read_engagement business_management
``` #### Does the default include ads_management, ads_read, or business_management? - business_management: Yes, this scope is included by default. - ads_management: No, this scope is not included by default. - ads_read: No, this scope is not included by default. #### How to add ad-related scopes (ads_management, ads_read)? To request additional scopes (like ads_management or ads_read), you need to use a custom OAuth client. Pipedream now supports bringing your own OAuth client, which allows you to define the exact scopes you need. Path to add them: 1. Create your own Facebook App and configure it with the desired scopes. 2. In Pipedream, configure the Facebook Graph API app to use your custom OAuth client (App ID and Secret). 3. Specify the additional scopes (ads_management, ads_read, etc.) in your app’s OAuth configuration. See the Pipedream documentation on custom OAuth clients for more details. — Summary Table | Scope | Included by Default? | |---------------------|---------------------| | business_management | Yes | | ads_management | No | | ads_read | No | — If you need help setting up a custom OAuth client or have more questions, please visit Pipedream for support.
#C04TFD4LB36
My Pipedream project is on plan tier [USER FILLS IN — check at [pipedream.com/billing](http://pipedream.com/billing)].
Is the `meta_ads` connector available on my current plan, or does it require an upgrade?
If it requires an upgrade: which plan tier unlocks meta_ads in production environment, and
roughly what does that tier cost?
You should visit Pipedream for the latest pricing, but I’ll do my best to answer. The meta_ads connector is considered a Premium app on Pipedream. According to the available documentation, access to Premium apps—including meta_ads—requires the Advanced plan or higher to use in a production environment. Plan tier required: - Advanced ($49/month, billed annually at $588/year) Summary: - If you are on the Free or Basic plan, you will need to upgrade to at least the Advanced plan to use meta_ads in production. - The Advanced plan includes Premium apps, unlimited workflows, unlimited connected accounts, and more. For the most accurate and up-to-date information, please check your plan details at Pipedream and see the full pricing breakdown at Pipedream.
#C04TFD4LB36
Currently PIPEDREAM_PROJECT_ENVIRONMENT=production in my .env. If I switch to development:
1. Will meta_ads appear in my Connect picker in the development environment?
2. Will my existing production-env connections (Gmail, etc.) be visible in development env,
or do they live in separate pools?
3. Does Pipedream provide a managed OAuth app for meta_ads in the development environment
(i.e. one that doesn't require me to register my own Meta developer app)?
Here are answers to your questions about switching your Pipedream Connect environment from production to development: — ### 1. Will meta_ads appear in my Connect picker in the development environment? Yes, all connectors—including meta_ads—are available in the Connect picker in the development environment. Development mode gives you access to all Connect features and connectors for testing and building, regardless of your plan. — ### 2. Will my existing production-env connections (Gmail, etc.) be visible in development env, or do they live in separate pools? No, they are not shared. Connections (accounts, credentials) in production and development environments are completely separate. If you connect Gmail, Facebook, or any other app in production, those connections will not appear in development, and vice versa. You must connect accounts separately in each environment. — ### 3. Does Pipedream provide a managed OAuth app for meta_ads in the development environment (i.e. one that doesn’t require me to register my own Meta developer app)? Yes, Pipedream provides a managed OAuth app for supported connectors—including meta_ads—in the development environment. You do not need to register your own Meta developer app for testing and development. You can use Pipedream’s managed OAuth for meta_ads in development. (If you need custom scopes or production use, you may need your own app.) — #### References - Pipedream Connect managed auth environments - Development and production environments keep connections separate. - All connectors are available for testing in development mode, with some user limits. — If you need more details or run into issues, please visit Pipedream.