Clio Manage v2

Provides integration with Clio Manage to query and retrieve practice records, and to create, update, and delete contacts, matters, tasks, and activities using the regional API v4 service.

Revision History

0.0.0.3 - Initial release.

Connection

Use this Connection to store your regional Clio application credentials and OAuth tokens.

Setup Notes

1. Configure a Clio developer application in the same region as your Clio account, with access to the records your Workflow needs.
2. Register the OAuth callback URI https://app.flowgear.net/r/auth.
3. Enter Region, ClientId, and ClientSecret in the Connection.
4. Complete OAuth authorization for the Connection.
5. Test the Connection to confirm that it can retrieve the current user.

The Node runs on cloud Clusters. The region determines the API and OAuth service used. Flowgear renews tokens through the saved Connection when renewal is required, retain the application credentials and refresh token for this purpose.

An authorization attempt expires after ten minutes and can be completed only once. Start a new attempt if it expires or authorization is declined. The Connection can retain at most sixteen unexpired attempts, wait for an attempt to expire if that limit is reached.

Operation templates can be loaded without live account metadata. Select a template to populate OperationId, the supported input fields, and the response structure.

Methods

The Node exposes the following record families. Users are read-only.

Query

Queries contacts, matters, tasks, activities, or users. Select the resource-specific template. The Node follows continuation pages automatically and returns one row per record.

Retrieve

Retrieves a contact, matter, task, activity, or user by ID, or retrieves the authenticated current user.

Create

Creates contacts, matters, tasks, or activities. Each input item creates one record using the selected resource-specific template.

For task creation, assignment requirements depend on the Clio account. If the account rejects unassigned tasks, map an existing user from Query Users or Retrieve Current User to assignee.id and set assignee.type to User. Alternatively, supply assignees containing existing firm user IDs. Do not supply both alternatives or submit the template's sample IDs.

Update

Updates contacts, matters, tasks, or activities using one PATCH request per input item. Include the target ID in each item.

Delete

Deletes contacts, matters, tasks, or activities using one request per input item.

Usage Notes

• Use the exact field names and scalar types shown by the selected template. The Node does not trim strings or coerce incorrectly typed values.
• Use Options.fields to request the fields your Workflow needs. Associations use braces, with at most one expansion level. Unsupported field selections are rejected before provider execution.
• Paging uses 200 records per page and follows Clio's continuation cursor internally. Do not supply limit, page_token, order, or other paging controls.
• String and integer collections advertised as CSV use quoted CSV, including collection filters such as ids[]. Quote values containing commas, newlines, or quotes, and double embedded quotes. String whitespace is preserved; use integers without surrounding spaces. Empty text means an empty collection; "" means one empty string. Invalid integers are rejected. Object collections remain structured arrays.
• Inspect Flowgear.IsSuccess on mutation results. Per-record business failures return failed rows and allow later inputs to continue. Authentication, transport, and malformed-response failures stop processing.
• Invalid first input records fail before a write. Invalid later records return failed rows. The first provider request completes when the Method starts, subsequent pages or items are processed as the response stream is consumed. Multiple writes are not transactional.
• Contact co_counsel_rate is supported only by Update, not by Create.

Examples

Create a Company Contact from a JSON Document

For a document-driven write, use a complete object envelope:

{
  "Items": [
    {
      "name": "Example Company",
      "type": "Company"
    }
  ]
}

1. Parse the document with the JSON Document Node's ParseAsObject Method.
2. Select the Clio Manage Node's Create Contacts template.
3. Define Object.Items on the parser using the selected contact template's item structure.
4. Map the parsed Object.Items array to the Clio Manage Node's Items Parameter.
5. Check Response.Flowgear.IsSuccess before using each returned contact id.

Parsing the complete object validates JSON syntax before any contact is written. A streaming ParseAsArray input can write an earlier record before discovering malformed JSON later in the document. Object parsing does not make the writes transactional or validate every record's business rules in advance.

Known Issues

The Node supports only the record families and Methods listed above. It does not expose financial lifecycle actions, document or binary transfers, webhooks, or other Clio products. Dynamic custom-field query filters are not supported.