Simplicate

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 Organizations | list-organizations | List organizations (companies) from the CRM module with optional filtering and pagination | | List Persons | list-persons | List persons (contacts) from the CRM module with optional filtering and pagination | | List Projects | list-projects | List projects with optional filtering and pagination | | List Sales | list-sales | List sales opportunities with optional filtering and pagination | | List Invoices | list-invoices | List invoices with optional filtering and pagination | | List Employees | list-employees | List employees from the HRM module with optional filtering and pagination | | List Hours | list-hours | List time registrations (hours) with optional filtering and pagination | | Get Organization | get-organization | Get a single organization by ID from the CRM module | | Get Person | get-person | Get a single person by ID from the CRM module | | Get Project | get-project | Get a single project by ID | | Get Sales | get-sales | Get a single sales opportunity by ID | | Get Invoice | get-invoice | Get a single invoice by ID | | Get Employee | get-employee | Get a single employee by ID from the HRM module | | Get Hours Entry | get-hours | Get a single time registration entry by ID | | Create Organization | create-organization | Create a new organization in the CRM module | | Create Person | create-person | Create a new person (contact) in the CRM module | | Create Project | create-project | Create a new project | | Create Sales | create-sales | Create a new sales opportunity | | Create Hours Entry | create-hours | Create a new time registration entry | | Update Organization | update-organization | Update an existing organization in the CRM module |

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