About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Question

Filevine: Raw request failed. Problem executing your request: Invalid response

  • 6 November 2023
  • 12 replies
  • 256 views
G

Hello, all!

I’ve been having an impossible time getting Zapier to make successful API requests to Filevine using the API Request feature. I’ve been able to make them through Postman without issue, but I always get the following error no matter the endpoint: 

Raw request failed. Problem executing your request: Invalid response

I’ve tried using the base URL listed in their docs as well as my company domain API base URL.

https://api.filevine.io
and https://{myCompanyDomain}.api.filevineapp.com
Both options give me the same error. I’ve also tried adding the “Authorization: Bearer {accessToken}” and “x-fv-sessionid: {refreshToken}” in the additional request headers just to try every possible combination even though the authentication headers are automatically sent. All four combinations produced the same error.
I attached some screenshots of the Zapier requests, the error message and the successful request in Postman. Any help would be greatly appreciated!
 

 

2 Attachments

12 replies

Troy Tessalone
Userlevel 7
Badge +14

Hi @gford 

Good question.

Can you link to the Filevine API endpoint docs you are referencing to configure the Zap step?

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
G

Hello Troy,

Here are the docs: https://developer.filevine.io/docs/v2/45a91cd6e76c6-base-url

I’m using this specific endpoint page in the screenshots, however, I get the same error no matter what endpoint I try.
I’ve tried the Get Project List, Get Contact, Get Contact List and a few others. For each one, I’m able to fetch information in Postman, just not Zapier.

Thanks!

Troy Tessalone
Userlevel 7
Badge +14

@gford 

Try adding Headers:

Content-Type: application/json

Accept: application/json

 

You may only need 1 of the 2.

 

 

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
G

@Troy Tessalone 

I added and tested them with both base URLs. I tested them on their own and with both added to the “Additional Request Headers.” I’m still seeing the same error.

G

Screenshots of what I input:

 

Troy Tessalone
Userlevel 7
Badge +14

@gford 

Can you post updated screenshots with how your Zap step is configured?

Make sure to use the base URL.

 

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
Troy Tessalone
Userlevel 7
Badge +14

@gford 

The API Request Zap action likely only supports the default base URL.

api.filevine.io

 

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
G

@Troy Tessalone 
I’ve tried both URLs. I was only trying my company domain URL because the base URL (api.filevine.io) wasn’t working. It just happened to be the one I took a screenshot of.

Troy Tessalone
Userlevel 7
Badge +14

@gford 

The error seems to indicate an invalid response.

That may indicate the request was fine.

Either the Zap action behind the scenes is not properly handling the response OR perhaps there was no data returned for the request, thus resulting in an error.

 

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
G

@Troy Tessalone 
It seems like it’s leaning towards something behind the scenes in the Zap action because I use the exact same contact id and reach the same endpoints with no issues using Postman. I just wanted to be sure that I had the information entered correctly for the request. I’ll see about possibly opening a ticket with Zapier about it.

Thanks so much for your help, Troy!🙂

Troy Tessalone
Userlevel 7
Badge +14

@gford 

You can try reporting this via a ticket to Zapier Support: https://zapier.com/app/get-help

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
G

I just wanted to update this because it is a bug that has been confirmed by Zapier and Filevine, so currently the only way to make custom requests is by using webhooks.

Reply


Terms & Conditions