Zephyr Squad Legacy

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 | | --- | --- | --- | | ZQL Search | zql-search | Search executions using Zephyr Query Language (ZQL) | | Get Execution Statuses | get-execution-statuses | Get all available execution statuses | | Update Step Result | update-step-result | Update the result/status of an execution step | | Create Folder | create-folder | Create a new folder in a test cycle | | List Folders | list-folders | Get all folders in a test cycle | | Delete Test Step | delete-test-step | Delete a test step | | Update Test Step | update-test-step | Update an existing test step | | Create Test Step | create-test-step | Create a new test step for a test issue | | Get Test Step | get-test-step | Get a specific test step | | List Test Steps | list-test-steps | Get all test steps for a test issue | | Delete Execution | delete-execution | Delete a test execution | | Update Execution | update-execution | Update a test execution (e.g., change status) | | Create Execution | create-execution | Create a new test execution | | Get Execution | get-execution | Get details of a specific test execution | | List Executions by Cycle | list-executions-by-cycle | Get a list of test executions for a specific cycle | | Delete Test Cycle | delete-test-cycle | Delete a test cycle | | Update Test Cycle | update-test-cycle | Update an existing test cycle | | Create Test Cycle | create-test-cycle | Create a new test cycle | | Get Test Cycle | get-test-cycle | Get details of a specific test cycle | | List Test Cycles | list-test-cycles | Get a list of test cycles for a project and version |

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 Zephyr Squad (Legacy) 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