Appearance
Facebook Ads (Meta)
undefined
| Detail | Value |
|---|---|
| Category | Marketing |
| Base URL | https://graph.facebook.com/v19.0 |
| Authentication | OAuth2 |
| Endpoints | 6 |
| Connector key | facebook-ads |
Using Facebook Ads (Meta) in a workflow
- Go to Connections and click New Connection.
- Pick Facebook Ads (Meta) from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET | Campaigns |
GET | Ad Sets |
GET | Ads |
GET | Insights |
GET | Creatives |
GET | Audiences |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Campaigns
| Detail | Value |
|---|---|
| Operation ID | campaigns_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Facebook Ads (Meta) connection from the Connection dropdown.
- In the Operation dropdown, select
campaigns_0. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Facebook Ads (Meta) API reference.
GET
Ad Sets
| Detail | Value |
|---|---|
| Operation ID | ad_sets_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Facebook Ads (Meta) connection from the Connection dropdown.
- In the Operation dropdown, select
ad_sets_1. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Facebook Ads (Meta) API reference.
GET
Ads
| Detail | Value |
|---|---|
| Operation ID | ads_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Facebook Ads (Meta) connection from the Connection dropdown.
- In the Operation dropdown, select
ads_2. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Facebook Ads (Meta) API reference.
GET
Insights
| Detail | Value |
|---|---|
| Operation ID | insights_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Facebook Ads (Meta) connection from the Connection dropdown.
- In the Operation dropdown, select
insights_3. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Facebook Ads (Meta) API reference.
GET
Creatives
| Detail | Value |
|---|---|
| Operation ID | creatives_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Facebook Ads (Meta) connection from the Connection dropdown.
- In the Operation dropdown, select
creatives_4. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Facebook Ads (Meta) API reference.
GET
Audiences
| Detail | Value |
|---|---|
| Operation ID | audiences_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Facebook Ads (Meta) connection from the Connection dropdown.
- In the Operation dropdown, select
audiences_5. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Facebook Ads (Meta) API reference.