Linkedin Ads

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has state: "READY", skip to Step 2.

#### 1b. Wait for the connection to be ready

If the connection is in BUILDING state, poll until it's ready:

npx @membranehq/cli connection get  --wait --json

The --wait flag long-polls (up to --timeout seconds, default 30) until the state changes. Keep polling until state is no longer BUILDING.

The resulting state tells you what to do next:

After the user completes the action (e.g. authenticates in the browser), poll again with membrane connection get --json to check if the state moved to READY.

Searching for actions

Search using a natural language description of what you want to do:

membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json

You should always search for actions in the context of a specific connection.

Each result includes id, name, description, inputSchema (what parameters the action accepts), and outputSchema (what it returns).

Popular actions

| Name | Key | Description | |---|---|---| | List Ad Accounts | list-ad-accounts | Search and list ad accounts with optional filters. | | List Campaign Groups | list-campaign-groups | Search and list campaign groups within an ad account. | | List Campaigns | list-campaigns | Search and list campaigns within an ad account. | | List Creatives | list-creatives | Search and list creatives within an ad account. | | Get Ad Account | get-ad-account | Retrieve details of a specific ad account by ID. | | Get Campaign Group | get-campaign-group | Retrieve details of a specific campaign group. | | Get Campaign | get-campaign | Retrieve details of a specific campaign. | | Get Creative | get-creative | Retrieve details of a specific creative. | | Create Ad Account | create-ad-account | Create a new ad account. | | Create Campaign Group | create-campaign-group | Create a new campaign group within an ad account. | | Create Campaign | create-campaign | Create a new campaign within an ad account. | | Create Creative | create-creative | Create a new creative within an ad account. | | Update Ad Account | update-ad-account | Update an existing ad account. | | Update Campaign Group | update-campaign-group | Update an existing campaign group. | | Update Campaign | update-campaign | Update an existing campaign. | | Update Creative | update-creative | Update an existing creative. | | Delete Campaign Group | delete-campaign-group | Delete a DRAFT campaign group. | | Delete Campaign | delete-campaign | Delete a DRAFT campaign. | | Delete Creative | delete-creative | Delete a creative. | | Get Ad Analytics | get-ad-analytics | Retrieve analytics data for ad campaigns, creatives, or accounts. |

Running actions

membrane action run  --connectionId=CONNECTION_ID --json

To pass JSON parameters:

membrane action run  --connectionId=CONNECTION_ID --input '{"key": "value"}' --json

The result is in the output field of the response.

Proxy requests

When the available actions don't cover your use case, you can send requests directly to the LinkedIn Ads API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.

membrane request CONNECTION_ID /path/to/endpoint

Common options:

| Flag | Description | |------|-------------| | -X, --method | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET | | -H, --header | Add a request header (repeatable), e.g. -H "Accept: application/json" | | -d, --data | Request body (string) | | --json | Shorthand to send a JSON body and set Content-Type: application/json | | --rawData | Send the body as-is without any processing | | --query | Query-string parameter (repeatable), e.g. --query "limit=10" | | --pathParam | Path parameter (repeatable), e.g. --pathParam "id=123" |

Best practices