Skip to main content

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

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions 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

Trying to integrate takeaway.com orders into getswift

  • April 5, 2020
  • 2 replies
  • 106 views
G

Hi,

i tried all integrations offered with getswift. None is working.

 

Error code:

Got 400 calling POST https://app.getswift.co/api/v2/deliveries, expected 2xx.

 

Please Help

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

2 replies

Danvers
Forum|alt.badge.img+12
  • DanversZapier Staff
  • Zapier Staff
  • April 6, 2020

Hi @giannis88 I’m sorry that you’re having some trouble with your Zap! 

 

Could you please share a few more details so we better understand what the issue might be?

  • What does your Zap look like? What trigger and action(s) are you using?
  • Where you’re seeing that error message? Which action and at what point (eg when you test a step in the Zap editor? When the Zap is turned on?)

 

Thanks!

jesse
Forum|alt.badge.img+9
  • jesseArchitect
  • Architect
  • June 10, 2020

Hey @giannis88, we just wanted to check in on this thread! Were you able to review Danvers’ reply to you? With a bit more information, we can see if we’re able to help out here!

Terms & ConditionsAccessibility statement