Document360

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 | | --- | --- | --- | | Search Drive | search-drive | Search files and folders in Drive | | Get Reader | get-reader | Get a reader by ID | | List Readers | list-readers | Get all available readers from the project | | Get Team Member | get-team-member | Get complete user details by ID | | Delete Team Member | delete-team-member | Delete a team member with the specified ID | | List Team Members | list-team-members | Get all team accounts | | Publish Article | publish-article | Publish an article with the specified ID | | Delete Article | delete-article | Delete an article with the specified ID | | Update Article | update-article | Update an article with the specified ID | | Create Article | create-article | Create a new article in a category | | Get Article By URL | get-article-by-url | Get an article by its URL | | List Articles | list-articles | Get list of articles within a project version | | Update Category | update-category | Update a category with the specified ID | | Delete Category | delete-category | Deletes a category by ID | | Create Category | create-category | Creates a new category in a project version | | Get Category | get-category | Gets details of a specific category by ID | | List Categories | list-categories | Gets a list of categories within a specific project version | | List Project Versions | list-project-versions | Gets a list of all project versions in the Document360 knowledge base |

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