Gravity Forms Clio Integration Setup & Usage Guide

The Gravity Forms Clio Integration Add-on sends your form entries to Clio. A Clio Manage feed creates a Person or Company contact (name, email, phone, address and custom fields), can update the existing contact with the same email address instead of creating a duplicate, and can also create a matter for the contact and add a note with the entry summary. A Clio Grow feed creates an inbox lead. This guide covers version 1.1.0.

Clio Manage vs Clio Grow: what each feed does

Each feed sends to one product. To send the same form to both, add two feeds (one Clio Manage feed and one Clio Grow feed).

Connecting Clio Manage (OAuth 2.0)

1. In Clio Manage, create a developer application for your account (the Clio developer documentation explains how). Give it the permissions for the data your feeds use: contacts and custom fields for every Clio Manage feed; matters, notes, practice areas and users (for the attorney list) if your feeds create matters or notes.
2. In WordPress, go to Forms → Settings → Clio Add-On and copy the Redirect URI shown there (it ends with admin-post.php?action=clio_oauth_callback) into your Clio application.
3. Paste the application’s App Key into Client ID (App Key) and its App Secret into Client Secret (App Secret).
4. Choose the Clio Region of your account: United States (app.clio.com), Canada (ca.app.clio.com), Europe (eu.app.clio.com) or Australia (au.app.clio.com). The same region is used for Clio Grow (grow.clio.com, ca.grow.clio.com, eu.grow.clio.com, au.grow.clio.com).
5. Click Save Settings, then Connect to Clio. Log in to Clio and allow access. You come back to the settings page with the message “Clio Manage is connected.” and the status Connected to Clio Manage as <your Clio user> (region <region>).

Connecting Clio Grow (Lead Inbox token)

Clio Grow feeds do not use OAuth. Copy the Lead Inbox token from your Clio Grow account into Lead capture token and click Save Settings. Choose the Clio Region above if your account is not in the United States.

Phone numbers (E.164)

Default country calling code (default 1 = USA/Canada) is used to convert phone numbers that were typed without a + prefix to the E.164 format, for example (555) 123-4567 becomes +15551234567. Numbers that start with + or 00 keep their own country code; for other country codes one leading 0 is removed (with 44, 07700 900123 becomes +447700900123). A number that cannot be converted (fewer than 8 or more than 15 digits) is sent as entered and the entry gets a warning note. Each feed chooses E.164 or As entered in the form.

Creating a feed

1. Open your form and go to Settings → Clio Add-On.
2. Click Add New and give the feed a name.
3. In Send to, choose Clio Manage: contact (+ optional matter and note) or Clio Grow: inbox lead. The feed list shows what each feed sends (for example “Clio Manage contact + matter + note”).

Clio Manage contact

Custom fields, practice areas and attorneys are read from Clio and kept for 12 hours. Click Refresh lists from Clio on the feed page after you change them in Clio.

Clio Manage matter (optional)

Tick Create a matter for the contact to create a matter whose client is the new or updated contact.

• Matter Description (required by Clio): text and merge tags, for example {Case type:5} - {Name (Last):1.6}. Saving the feed without a description shows “Clio requires a matter description.”
• Practice Area and Responsible Attorney: chosen from the practice areas and the enabled attorneys of your Clio account, or None.
• Matter Status: Pending (default), Open or Closed.
• Open Date: tick to set it to the submission date.

Clio Manage note (optional)

Tick Add a note with the entry summary. Choose where it goes (the matter, or the contact when no matter is created; or always the contact), the Note Subject (default “Web form: {form_title}”) and the Note Text (plain text, default {all_fields} = every answer of the entry). The note date is the submission date.

Clio Grow inbox lead

• Map Fields: First Name, Last Name and Message are required; Email and Phone are optional.
• Referring URL (optional): when it is not mapped or empty, the address of the page with the form is sent.
• Lead Source: text and merge tags (default “Gravity Forms: {form_title}”).
• Phone Format: E.164 (default for new feeds) or as entered. Feeds created with version 1.0.x keep sending the phone as entered until you change this setting.

Conditions and WP E-Signature

Tick Enable Condition to send the entry only when your rules match (Gravity Forms conditional logic). If the WP E-Signature add-on for Gravity Forms is active, the feed option WP E-Signature: Enabled sends the entry after the document is signed instead of at submission; the feed condition is checked then as well.

Entry notes: what was sent

Every feed adds a note to the entry with the Clio record ids, for example Clio Manage: contact 1003 created. Matter 1007 (01007-Client) created. Note 1008 added to the matter. or Clio Grow: inbox lead 512 created.

The ids are also stored as entry meta: clio_contact_id_<feed id> and clio_matter_id_<feed id>.

Developer filters

Each filter receives the request body and $feed, $entry, $form and must return the body:

• gf_clio_contact_payload: Clio Manage contact (create or update)
• gf_clio_matter_payload: Clio Manage matter
• gf_clio_note_payload: Clio Manage note
• gf_clio_grow_payload: Clio Grow inbox lead
• gf_clio_debug_log: return true to write short debug lines (HTTP status codes, endpoints and Clio ids, never form data) to the PHP error log; only works when WP_DEBUG is on.

add_filter( 'gf_clio_contact_payload', function ( $body, $feed, $entry, $form ) {
    $body['data']['title'] = rgar( $entry, '12' ); // Clio contact title from form field 12.
    return $body;
}, 10, 4 );

Upgrading from version 1.0.x

• Your feeds, settings, license and Clio connection keep working; you do not need to reconnect. The saved tokens are moved out of the settings form into their own database option.
• Clio Manage feeds send the same contact data as before (picklist and date custom field values are now converted to the format Clio expects). New options (phone, address, existing contacts, matter, note) are off until you set them.
• Clio Grow feeds keep their mapping and send the phone as entered. They now also send the Lead Inbox token in the field named in Clio’s documentation and a lead source (“Gravity Forms: <form title>”).
• The feed setting “Please Select Grow Platform” is now called Send to.
• Errors now add a red error note with Clio’s message instead of a success note.

Frequently asked questions

Does it create matters?

Yes, from version 1.1.0, when you tick “Create a matter for the contact” in a Clio Manage feed. Matter custom fields are not mapped.

Will it create duplicate contacts?

With the default “Always create a new contact” every entry creates a contact, as in 1.0.x. Choose “Update the existing contact with the same email address” to update the contact whose email is exactly the submitted address.

Do I need to re-authorize Clio every 30 days?

No. The add-on renews the access token with the refresh token. You only reconnect if Clio refuses the renewal, and the add-on tells you on every admin page.

Can one form send to Clio Manage and Clio Grow?

Yes, with two feeds on the same form.

Which regions are supported?

United States, Canada, Europe and Australia, for both Clio Manage and Clio Grow.

What is not included?

Tasks, calendar entries, documents and file uploads, time entries and billing, matter custom fields, and Clio Grow custom fields are not sent by this add-on.