Add Ability to Import Clio Field Variables into Hard Field Variables in Workflows#217

I would like the ability to import data from the Clio drop-down matter and contact fields into actual hard variable fields within the Gavel workflow, rather than have it only flow into the documents. Even just having a function to push that information into a separate workflow once the matter and contacts in the dropdowns are selected would be great.

Right now we are trying to set up a client-facing workflow so it auto-populates with the information we already have from a previous file we worked on for them, that way they’re only filling in the questions that we’re missing information on and not re-entering details they already gave us in the past. The only way to do this currently is through Zapier, however we recently discovered that using Zapier to pull information from Clio can be very finiky. For some reason we can’t see our client’s information from their contact details if we set the Zapier activation to something that happens in the Clio matter, and I’m assuming the same thing will happen in reverse if we try to set up the activation to happen in the Clio contact side instead.

Our office is just frustrated that there’s not an easier way to do this. We’ve been told repeatedly by both Clio and Gavel that the integration and data transfer will work for what we want, which is what sold us on migrating over to both products, and this one little hiccup might force us to go back to the drawing board on a major workflow project that we’ve already worked on for half a year.

I haven’t had the issue you’re describing in Zapier, but you need to know that Clio treats the contact and the matter separately, and so in Zapier you may need to lookup the contact or the matter in addition to the trigger in order to have access to all of the fields of data.

In Gavel, Clio integration in the workflow typically requires the user be logged in to a Gavel account to protect the Clio data, which means for this use case you probably want to start the workflow pre-filled from Zapier.

If you want the Clio variables to show up in the Gavel workflow, you can set the default values for the questions to be the Clio variable. Below are some of the default values (including an example for custom fields) that are brought into Gavel via the integration. If you need to reference the variables in Invisible Logic, remove the $ but leave the {}.

“cc” is the Gavel variable name for “Clio Contact”:
${cc.company.first_name}
${cc.company.initials}
${cc.company.last_name}
${cc.company.middle_name}
${cc.company.name}
${cc.company.prefix}
${cc.company.primary_email_address}
${cc.company.primary_phone_number}
${cc.company.secondary_email_address}
${cc.company.secondary_phone_number}
${cc.company.title}
${cc.company.updated_at}
${cc.created_at}
${cc.custom_fields.client_ssn}
${cc.first_name}
${cc.initials}
${cc.last_name}
${cc.ledes_client_id}
${cc.middle_name}
${cc.name}
${cc.prefix}
${cc.primary_address.city}
${cc.primary_address.country}
${cc.primary_address.created_at}
${cc.primary_address.name}
${cc.primary_address.postal_code}
${cc.primary_address.province}
${cc.primary_address.street}
${cc.primary_address.updated_at}
${cc.primary_email_address}
${cc.primary_phone_number}
${cc.primary_work_address.city}
${cc.primary_work_address.country}
${cc.primary_work_address.created_at}
${cc.primary_work_address.name}
${cc.primary_work_address.postal_code}
${cc.primary_work_address.province}
${cc.primary_work_address.street}
${cc.primary_work_address.updated_at}

“cm” is the Gavel variable name for “Clio Matter”:
${cm.billable}
${cm.billing_method}
${cm.client.company.clio_connect_email}
${cm.client.company.created_at}
${cm.client.company.first_name}
${cm.client.company.has_clio_for_clients_permission}
${cm.client.company.initials}
${cm.client.company.is_bill_recipient}
${cm.client.company.is_client}
${cm.client.company.is_co_counsel}
${cm.client.company.last_name}
${cm.client.company.ledes_client_id}
${cm.client.company.locked_clio_connect_email}
${cm.client.company.middle_name}
${cm.client.company.name}
${cm.client.company.prefix}
${cm.client.company.primary_email_address}
${cm.client.company.primary_phone_number}
${cm.client.company.secondary_email_address}
${cm.client.company.secondary_phone_number}
${cm.client.company.title}
${cm.client.company.updated_at}
${cm.client.created_at}
${cm.client.first_name}
${cm.client.id}
${cm.client.initials}
${cm.client.last_name}
${cm.client.ledes_client_id}
${cm.client.middle_name}
${cm.client.name}
${cm.client.prefix}
${cm.client.primary_address.city}
${cm.client.primary_address.country}
${cm.client.primary_address.created_at}
${cm.client.primary_address.name}
${cm.client.primary_address.postal_code}
${cm.client.primary_address.province}
${cm.client.primary_address.street}
${cm.client.primary_address.updated_at}
${cm.client.primary_email_address}
${cm.client.primary_phone_number}
${cm.client.title}
${cm.client.type}
${cm.client.updated_at}
${cm.close_date}
${cm.created_at}${cm.custom_fields.traffic_ticket_qty}
${cm.custom_number}
${cm.description}
${cm.display_number}
${cm.location}
${cm.maildrop_address}
${cm.number}
${cm.open_date}
${cm.status}
${cm.updated_at}
${cm.user.created_at}
${cm.user.email}
${cm.user.first_name}
${cm.user.initials}
${cm.user.last_name}
${cm.user.name}
${cm.user.phone_number}
${cm.user.time_zone}
${cm.user.updated_at}