r3

What this skill does

# R3

R3 is a platform for building and deploying multi-party workflows. It's used by businesses, governments, and other organizations that need to collaborate on complex processes. Think of it as a blockchain-inspired system for automating agreements and data sharing.

Official docs: https://docs.corda.net/

## R3 Overview

- **Cases**
  - **Case Notes**
- **Contacts**
- **Tasks**
- **Expenses**
- **Time Entries**
- **Calendar Events**
- **Case Types**
- **Users**
- **Companies**
- **Tags**
- **Vendors**
- **Bank Accounts**
- **Invoice**
- **Payment**
- **Trust Request**
- **Ledger Activities**
- **Document**
- **Email**
- **Phone Log**
- **Message**
- **Referral**
- **Product**
- **Purchase Order**
- **Retainer Request**
- **Settlement**
- **Check**
- **Credit Card**
- **Reconciliation**
- **Rule**
- **Subscription**
- **Task List**
- **Tax Rate**
- **Time Off Request**
- **Time Off Policy**
- **Workflow**
- **Integration**
- **Matter Template**
- **Note Template**
- **Product Category**
- **Quickbooks Online**
- **Xero**
- **Lawpay**
- **Google Calendar**
- **Office 365**
- **Box**
- **Dropbox**
- **Google Drive**
- **OneDrive**
- **Sharefile**
- **Netdocuments**
- **iCloud Calendar**
- **Contact Group**
- **Document Category**
- **Expense Category**
- **Firm Setting**
- **Goal**
- **Invoice Theme**
- **Journal Entry**
- **Lexicata**
- **Notification**
- **Office 365 Contact**
- **Office 365 Email**
- **Office 365 Calendar Event**
- **Payment Method**
- **Permission**
- **Pipeline**
- **Report**
- **Role**
- **Salesforce**
- **Smart Advocate**
- **Task Template**
- **Trust Account**
- **Trust Transaction**
- **User Role**
- **Zapier**
- **Clock**
- **Credit Note**
- **Deposit**
- **General Retainer**
- **Operating Account**
- **Recurring Invoice**
- **Task Dependency**
- **Time Activity**
- **User Permission**
- **Client Portal**
- **Contact Type**
- **Credit Card Transaction**
- **Custom Field**
- **Data Import**
- **Email Template**
- **Firm User**
- **Form**
- **Google Contact**
- **Google Email**
- **Invoice Payment**
- **Matter User**
- **Plaid Connection**
- **Product Unit**
- **QuickBooks Online Vendor**
- **Recurring Expense**
- **Recurring Task**
- **Tax Payment**
- **Time Rounding Rule**
- **User Time Entry**
- **Xero Contact**
- **Xero Invoice**
- **Xero Vendor**
- **Billing Contact**
- **Case Custom Field**
- **Case Fee**
- **Case Task**
- **Check Template**
- **Client Request**
- **Contact Custom Field**
- **Contract Template**
- **Credit Card Charge**
- **Custom Report**
- **Deposit Transaction**
- **Document Assembly**
- **Expense Custom Field**
- **Firm Credit Card**
- **Google Group**
- **Invoice Custom Field**
- **Matter Custom Field**
- **Payment Custom Field**
- **Product Custom Field**
- **Task Custom Field**
- **Time Entry Custom Field**
- **Trust Request Custom Field**
- **User Custom Field**
- **Xero Bill**
- **Xero Credit Note**
- **Xero Payment**
- **Xero Purchase Order**
- **Xero Tax Rate**
- **Case Product**
- **Case Referral**
- **Case Task List**
- **Contact Referral**
- **Credit Card Refund**
- **Expense Payment**
- **Firm Bank Account**
- **Firm Expense Category**
- **Firm Task Template**
- **Invoice Credit Note**
- **Matter Subscription**
- **Payment Refund**
- **Product Purchase Order**
- **Recurring Credit Note**
- **Recurring Invoice Payment**
- **Recurring Task List**
- **Retainer Payment**
- **Task List Task**
- **Time Off Request Policy**
- **Trust Request Payment**
- **User Task Template**
- **Xero Bank Account**
- **Xero Journal Entry**
- **Xero Tracking Category**
- **Case Expense**
- **Case Invoice**
- **Case Payment**
- **Case Time Entry**
- **Contact Case**
- **Contact Invoice**
- **Contact Payment**
- **Contact Time Entry**
- **Expense Custom Field Value**
- **Invoice Custom Field Value**
- **Payment Custom Field Value**
- **Product Custom Field Value**
- **Task Custom Field Value**
- **Time Entry Custom Field Value**
- **Trust Request Custom Field Value**
- **User Custom Field Value**
- **Case Task Template**
- **Contact Custom Field Value**
- **Case Custom Field Value**
- **Case Task List Template**

Use action names and parameters as needed.

## Working with R3

This skill uses the Membrane CLI to interact with R3. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

### Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

```bash
npm install -g @membranehq/cli@latest
```

### Authentication

```bash
membrane login --tenant --clientName=<agentType>
```

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

**Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

```bash
membrane login complete <code>
```

Add `--json` to any command for machine-readable JSON output.

**Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

### Connecting to R3

Use `membrane connection ensure` to find or create a connection by app URL or domain:

```bash
membrane connection ensure "https://www.r3.com/" --json
```
The user completes authentication in the browser. The output contains the new connection id.

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:

```bash
npx @membranehq/cli connection get <id> --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:

- **`READY`** — connection is fully set up. Skip to **Step 2**.
- **`CLIENT_ACTION_REQUIRED`** — the user or agent needs to do something. The `clientAction` object describes the required action:
  - `clientAction.type` — the kind of action needed:
    - `"connect"` — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
    - `"provide-input"` — more information is needed (e.g. which app to connect to).
  - `clientAction.description` — human-readable explanation of what's needed.
  - `clientAction.uiUrl` (optional) — URL to a pre-built UI where the user can complete the action. Show this to the user when present.
  - `clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically.

  After the user completes the action (e.g. authenticates in the browser), poll again with `membrane connection get <id> --json` to check if the state moved to `READY`.

- **`CONFIGURATION_ERROR`** or **`SETUP_FAILED`** — something went wrong. Check the `error` field for details.

### Searching for actions

Search using a natural language description of what you want to do:

```bash
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

Use `npx @membranehq/cli@latest action list --intent=QUERY --connectionId=CONNECTION_ID --json` to discover available actions.

### Running actions

```bash
membrane action run <actionId> --connectionId=CONNECTION_ID --json
```

To pass JSON parameters:

```bash
membrane action run <actionId> --connectionId=CONNECTION_ID --input '{"key": "value"}' --json
```

The result is in the `o