Zapier integration with Clio Grow API returning 401 error when submitting lead data

I’m struggling with connecting my Google Forms lead data to Clio Grow through Zapier. Every time I try to send the information, I keep getting a 401 unauthorized error.

Here’s my current setup:

request_format: json
array_wrapping: false
flatten_data: false
api_endpoint: https://grow.clio.com/inbox_leads

form_data:
  lead_first_name: Marcus
  lead_last_name: Chen  
  lead_email: [email protected]
  lead_source: DMV
  referral_source: google_ads
  api_token: my_actual_token_hidden_for_security

request_headers:
  Content-Type: application/json

I’ve been working on this for several days and the basic support hasn’t helped me figure out what’s wrong. The lead data should appear in my Clio Grow dashboard but nothing comes through. Has anyone successfully set up this type of integration before?

hey, ive been there too! make sure ur api token is in the headers, not in form data. try adding Authorization: Bearer your_token instead, should resolve the 401 error!

That 401 error indicates an issue with authentication. The API token should be placed in the request headers rather than the form data. Include it as Authorization: Bearer your_token_here in the headers. Additionally, ensure that the token you are using has the proper permissions for lead creation, as they are often set to read-only by default. I faced a similar problem and had to adjust the permissions in the Clio admin panel.

Yes, it seems authentication is the key issue. Make sure to transfer the token to the headers as advised. Additionally, confirm that you’re utilizing the correct format for the endpoint. Certain Clio integrations require a specific user ID or firm ID included in the URL. It’s also important to ensure that your Zapier webhook sends the exact field names that Clio requires, as even minor discrepancies in field names can lead to silent failures even after authentication is confirmed. Start testing with a minimal payload that includes only the required fields to determine whether the problem lies in authentication or data formatting.