Datadog

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 Monitors | list-monitors | Get all monitors with optional filtering | | List Dashboards | list-dashboards | Get all dashboards | | List Events | list-events | Get a list of events from the event stream | | List SLOs | list-slos | Get all Service Level Objectives | | List Incidents | list-incidents | Get a list of incidents (V2 API) | | List Users | list-users | Get a list of all users in the organization | | List Hosts | list-hosts | Get all hosts for your organization | | List Downtimes | list-downtimes | Get all scheduled downtimes | | List Service Definitions | list-service-definitions | Get all service definitions from the Service Catalog | | List Metrics | list-metrics | Get the list of actively reported metrics from a given time | | Get Monitor | get-monitor | Get details of a specific monitor by ID | | Get Dashboard | get-dashboard | Get details of a specific dashboard by ID | | Get Event | get-event | Get details of a specific event by ID | | Get SLO | get-slo | Get details of a specific SLO | | Get Incident | get-incident | Get details of a specific incident | | Get User | get-user | Get details of a specific user | | Create Monitor | create-monitor | Create a new monitor to track metrics, integrations, or other data | | Create Dashboard | create-dashboard | Create a new dashboard | | Create Event | create-event | Post an event to the Datadog event stream | | Update Monitor | update-monitor | Update an existing monitor |

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 Datadog 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