Microsoft Advertising (Bing)

undefined

Detail	Value
Category	Marketing
Base URL	https://campaign.api.bingads.microsoft.com/Api/Advertiser/CampaignManagement/v13
Authentication	See connector docs
Endpoints	5
Connector key	bing-ads

Using Microsoft Advertising (Bing) in a workflow

1. Go to Connections and click New Connection.
2. Pick Microsoft Advertising (Bing) from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET	Campaigns
GET	Ad Groups
GET	Ads
GET	Keywords
GET	Budgets

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

1. Add an API Call node to your workflow.
2. Pick your Microsoft Advertising (Bing) connection from the Connection dropdown.
3. In the Operation dropdown, select campaigns_0.
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 Microsoft Advertising (Bing) API reference.

GET

Ad Groups

Detail	Value
Operation ID	ad_groups_1
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Microsoft Advertising (Bing) connection from the Connection dropdown.
3. In the Operation dropdown, select ad_groups_1.
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 Microsoft Advertising (Bing) API reference.

GET

Ads

Detail	Value
Operation ID	ads_2
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Microsoft Advertising (Bing) connection from the Connection dropdown.
3. In the Operation dropdown, select ads_2.
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 Microsoft Advertising (Bing) API reference.

GET

Keywords

Detail	Value
Operation ID	keywords_3
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Microsoft Advertising (Bing) connection from the Connection dropdown.
3. In the Operation dropdown, select keywords_3.
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 Microsoft Advertising (Bing) API reference.

GET

Budgets

Detail	Value
Operation ID	budgets_4
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Microsoft Advertising (Bing) connection from the Connection dropdown.
3. In the Operation dropdown, select budgets_4.
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 Microsoft Advertising (Bing) API reference.