Honeybadger

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 Projects | list-projects | Get a list of all projects accessible to the authenticated user | | List Faults | list-faults | Get a list of faults (errors) for a project | | List Check-Ins | list-check-ins | Get a list of check-ins for a project | | List Uptime Sites | list-sites | Get a list of uptime monitoring sites for a project | | List Teams | list-teams | Get a list of teams accessible to the authenticated user | | Get Project | get-project | Get details of a specific project by ID | | Get Fault | get-fault | Get details of a specific fault (error) by ID | | Get Check-In | get-check-in | Get details of a specific check-in | | Get Uptime Site | get-site | Get details of a specific uptime monitoring site | | Get Team | get-team | Get details of a specific team by ID | | Create Project | create-project | Create a new project in Honeybadger | | Create Check-In | create-check-in | Create a new check-in (dead-man switch) for scheduled tasks | | Create Uptime Site | create-site | Create a new uptime monitoring site | | Create Team | create-team | Create a new team | | Update Project | update-project | Update an existing project | | Update Fault | update-fault | Update a fault (mark as resolved, ignored, or assign to user) | | Update Check-In | update-check-in | Update an existing check-in | | Update Uptime Site | update-site | Update an existing uptime monitoring site | | Update Team | update-team | Update an existing team | | Delete Project | delete-project | Delete a project from Honeybadger |

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