Bitly

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 | | --- | --- | --- | | Get Bitlink Clicks by Country | get-bitlink-countries | Gets click statistics for a Bitlink broken down by country | | Get Bitlink Clicks Over Time | get-bitlink-clicks | Gets click statistics over time for a Bitlink, broken down by time intervals | | List Bitlinks by Group | list-bitlinks-by-group | Retrieves all Bitlinks for a specific group with optional filtering | | Get Current User | get-user | Retrieves information about the authenticated user | | List Groups | list-groups | Retrieves all groups the authenticated user belongs to | | Create Bitlink | create-bitlink | Creates a new Bitlink with full customization options including title, tags, and custom keyword | | Get Bitlink Clicks Summary | get-bitlink-clicks-summary | Gets a summary of click statistics for a Bitlink | | Delete Bitlink | delete-bitlink | Deletes a Bitlink permanently | | Update Bitlink | update-bitlink | Updates properties of an existing Bitlink | | Get Bitlink | get-bitlink | Retrieves information about a specific Bitlink | | Expand Bitlink | expand-bitlink | Expands a Bitlink to get the original long URL | | Shorten Link | shorten-link | Converts a long URL to a shortened Bitlink |

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