Skip to main content
Best answer

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


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.

 

Best answer by Troy TessaloneBest answer by Troy Tessalone

@Chunt59 

I see the issue now.

Top: tigger

Bottom: down

 

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.

14 replies

Troy Tessalone
Forum|alt.badge.img+14

Hi @Chunt59 

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


  • Author
  • New
  • 7 replies
  • December 12, 2023
Troy Tessalone wrote:

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
Forum|alt.badge.img+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.


  • Author
  • New
  • 7 replies
  • December 12, 2023

I

Troy Tessalone wrote:

@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
Forum|alt.badge.img+14

@Chunt59 

Headers field description says key/value pairs.

Top: Content-Type

Bottom: application/json

 


  • Author
  • New
  • 7 replies
  • December 12, 2023
Troy Tessalone wrote:

 

@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
Forum|alt.badge.img+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"
}

 


  • Author
  • New
  • 7 replies
  • December 12, 2023
Troy Tessalone wrote:

@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
Forum|alt.badge.img+14

@Chunt59 

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

 


  • Author
  • New
  • 7 replies
  • December 12, 2023
Troy Tessalone wrote:

@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
Forum|alt.badge.img+14

@Chunt59 

Ok then revert to this JSON

{
  "trigger": "down"
}

 

Try setting the Payload Type = Form

 


  • Author
  • New
  • 7 replies
  • December 12, 2023
Troy Tessalone wrote:

@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
Forum|alt.badge.img+14
  • Zapier Expert
  • 30916 replies
  • Answer
  • December 12, 2023

@Chunt59 

I see the issue now.

Top: tigger

Bottom: down

 


  • Author
  • New
  • 7 replies
  • December 12, 2023
Troy Tessalone wrote:

@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!