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.

Best answer

Zap Failing with Error 400: Uptime-Monitor.io to Instatus Error

  • 12 December 2023
  • 14 replies
  • 58 views
C

Goal Zap: GET from uptime-monitor.io → PUSH to instatus.com

I am a novice API user. I am able to retrieve from uptime-monitor.io. However, unable to push to instatus.com , Error 400. I have removed the endpoint URL from the photos. Specific question: how do I structure the header? General question: what am I doing wrong? 

Instatus.com instructions: 

If you want to open a new incident, send a POST request to the URL with the following body. Encode it as JSON with the Content-Type: application/json header.

{ "trigger": "down" }

Thank you for the help.

 

icon

Best answer by Troy Tessalone 13 December 2023, 00:45

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

14 replies

Troy Tessalone
Userlevel 7
Badge +14

Hi @Chunt59 

Please link to the API docs that you are referencing to configure the Zap step.

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

Hi @Chunt59 

Please link to the API docs that you are referencing to configure the Zap step.


This is on our account page. URLs are protected. 

Additional documentation is available here: https://instatus.com/help/integrations/custom-service-webhook

Troy Tessalone
Userlevel 7
Badge +14

@Chunt59 

Make sure to add a Header.

If you want to open a new incident, send a POST request to the URL with the following body Encode it as JSON with the Content-Type: application/json header, and be sure to include the templates.

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

I

@Chunt59

Make sure to add a Header.

If you want to open a new incident, send a POST request to the URL with the following body Encode it as JSON with the Content-Type: application/json header, and be sure to include the templates.

 

Do the data field should remain the same?

{
  "trigger": "down"
}

 

and header should be a single line: 

Content-Type: application/json
 

 

Troy Tessalone
Userlevel 7
Badge +14

@Chunt59 

Headers field description says key/value pairs.

Top: Content-Type

Bottom: application/json

 

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

 

@Chunt59

Headers field description says key/value pairs.

Top: Content-Type

Bottom: application/json

 

 

 

Updated. I had tried that before. Maybe this is trigger related? The trigger is configured to catch hook, no child key, and returns a good test result.

 

Troy Tessalone
Userlevel 7
Badge +14

@Chunt59 

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

Per the provided link:

If you want to open a new incident, send a POST request to the URL with the following body, and be sure to include the template.

Status is optional

{
  "trigger": "down",
  "createTemplate": "cl8hrdsdsasu232441sv26yq",
  "status": "PARTIALOUTAGE"
}

 

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

@Chunt59

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

Per the provided link:

If you want to open a new incident, send a POST request to the URL with the following body, and be sure to include the template.

Status is optional

{
  "trigger": "down",
  "createTemplate": "cl8hrdsdsasu232441sv26yq",
  "status": "PARTIALOUTAGE"
}

 

 

Troy Tessalone
Userlevel 7
Badge +14

@Chunt59 

Is the Template ID being used a Template ID that belongs to your account?

 

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

@Chunt59

Is the Template ID being used a Template ID that belongs to your account?

 

I’m not seeing this anywhere else except for on the API Doc. When adding it appears this isn’t needed: 

 

This is an example photo from the account. 

 

Troy Tessalone
Userlevel 7
Badge +14

@Chunt59 

Ok then revert to this JSON

{
  "trigger": "down"
}

 

Try setting the Payload Type = Form

 

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

@Chunt59

Ok then revert to this JSON

{
  "trigger": "down"
}

 

Try setting the Payload Type = Form

 


“Failed to create a request in Webhooks by Zapier
Invalid trigger type (HTTP Status Code: 400)”

Troy Tessalone
Userlevel 7
Badge +14

@Chunt59 

I see the issue now.

Top: tigger

Bottom: down

 

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

@Chunt59

I see the issue now.

Top: tigger

Bottom: down

 

Thank you so much for the help. I was wondering if it needed a title similar to the header. Worked great! 

Terms & Conditions