Introducing The Law Community, the online community just for Clio customers. Sign up now.

How to Use Zapier to Send Lead Generation Emails to the Clio Grow Lead Inbox

Note: This workflow to use Zapier with Clio Grow is currently outside the scope of Clio Support. We will not be able to troubleshoot any issues you may experience using this API endpoint.

Note: The emails that are received by the email parser need to be highly standardized with very little variation in how the lead information is displayed in the email body. If there are too many variations the email parser will not be able to grab the correct data consistently.

Clio Grow provides a “Lead Inbox” API endpoint which can accept leads from various sources in a JSON formatted POST request. The instructions for setting it up are listed below:

  1. Create a new Zap and set up a "Trigger". The trigger App will be "Email Parser by Zapier"mceclip0.png
  2. Connect an email parser account if you have one already or create a new one
  3. Create a Mailbox in the email parser app mceclip1.png
  4. Copy the email address provided and send/forward an email with the lead information to this address
  5. When the email arrives in the parser, highlight and name each individual data point(see step 13 for available fields
  6. mceclip2.png
  7. Save the address and template when complete
  8. Back in the Zap trigger step, select the mailbox name from the dropdownmceclip3.png
  9. Add an "Action" step to the Zap.
  10. Select "Webhooks by Zapier" as the app for the action.
  11. Choose "POST" as the type of request
  12. Input https://grow.clio.com/inbox_leads as the URL
  13. Choose "JSON" as the "Payload Type"
  14. Input all of the following key/value pairs under the "Data" section:

    inbox_lead__from_first <insert data from trigger step>
    inbox_lead__from_last <insert data from trigger step>
    inbox_lead__from_phone <insert data from trigger step>
    inbox_lead__from_email <insert data from trigger step>
    inbox_lead__from_message <insert data from trigger step>
    inbox_lead__from_source <insert data from trigger step or custom value>
    inbox_lead__referring_url <insert data from trigger step or custom value>
    inbox_lead_token <insert Clio Grow Inbox Token>
    Note: The phone and email fields accept blank values, but all other fields must have a valid value. Source and referring url may be the same value.

  15. Leave the default settings for the rest of the fields, ensuring that:
    • "Wrap Request In Array" is set to "No"
    • "Unflatten" is set to "Yes"
  16. "Headers" which should be set to:

    Accept application/json
  17. Save the Zap

Common Errors:

Error Message Potential Cause
"The app returned "Unauthorized" with no further details. Try reconnecting your account. This usually happens when we can't connect to your account for an app or service because your password was changed or Zapier's access was revoked." There may be extra spaces or a new line after the names of one or more of the 'keys' or 'headers'.
"The app returned "....". This can occur if the information entered into a field is not in the correct format. Double-check that you are using the correct format for entering values into a field." This may be due to the 'Email' being sent having already been used within your Grow account in a different Contact.
The app returned "Unprocessable Entity" with no further details. (422 error) 

This error occurs when data sent from a Trigger in Zapier does not match the format requirements of a Lead in Grow. Common causes:

- The Phone Number field is sent as an Integer instead of a String (sent as 12345 instead of "12345") (see here).

- The Phone Number field contains less than 10 characters (aka "555" will fail, where "555 555 5555" will succeed).

Was this article helpful?
This information is confusing or wrong
This isn't the information that I was looking for
I don't like this functionality