Skip to main content
Best answer

Only absolute URLs are supported? What does this mean?


Why does a Zap which has previously been working for me now not work a presents the error message “Only absolute URLs are supported. This is likely a problem with the app. Please contact support”

 

What is an absolute URL?

Why would this now stop working when the Zap has been working fine till today?

 

Best answer by steph.nBest answer by steph.n

Hi @finansptyltd - Thanks for being patient! We saw that you received an answer from Zapier Support, so we’re going to share it here:

Thanks for reaching out! It should be {{bundle.authData.api_server}} instead of {{bundle.inputData.api_server}}. Looks like your integration used to have an auth field named "api_server" but was removed in a later version. Our conversion process wasn't aware of that and replaced {{api_server}} with {{bundle.inputData.api_server}}. I've gone ahead and manually changed those to {{bundle.authData.api_server}}.

Hopefully that would fix the issue. Thanks!

View original
Did this topic help you find an answer to your question?
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

steph.n
Forum|alt.badge.img+8
  • Builder
  • 899 replies
  • March 25, 2020

Hi @finansptyltd - Thanks for writing today!

To ensure that this isn’t a bigger bug, could you let us know what app(s) you’re using that caused your Zap to show you this error message? This will help us track it down for you.

Thanks!


Liz_Roberts
Forum|alt.badge.img+8
  • Zapier Staff
  • 1366 replies
  • March 30, 2020

Hi @finansptyltd ,

Checking in to see if you are still encountering this error! If you are, could you share which apps you are using so that we can dig deeper? 

Thanks!


steph.n
Forum|alt.badge.img+8
  • Builder
  • 899 replies
  • Answer
  • May 5, 2020

Hi @finansptyltd - Thanks for being patient! We saw that you received an answer from Zapier Support, so we’re going to share it here:

Thanks for reaching out! It should be {{bundle.authData.api_server}} instead of {{bundle.inputData.api_server}}. Looks like your integration used to have an auth field named "api_server" but was removed in a later version. Our conversion process wasn't aware of that and replaced {{api_server}} with {{bundle.inputData.api_server}}. I've gone ahead and manually changed those to {{bundle.authData.api_server}}.

Hopefully that would fix the issue. Thanks!