compass custom webhook url

[Phill Pafford]

So I created a customer webhook in compass, and I get the URL, but it doesn't look correct, also changing to my company one also fails

is this URL correct? basically `hello.atlassian-dev.net`

• https://123kjh123-277c-413e0-86f8-b8898db50eb2.hello.atlassian-dev.net/x1/R8asdlkjasldkjlwssaxav93gklFhM

which times out

Changed to 

• https://123kjh123-277c-413e0-86f8-b8898db50eb2.acme.atlassian.net/x1/R8asdlkjasldkjlwssaxav93gklFhM

which errors out

How do I change the base url for it's correct?

[Enrique Serrano Valle]

@Phill Pafford ,

While I'm not sure about reasons behind specific timeouts, this application uses a Forge webtrigger, and the top URL that you're providing (under hello.atlassian-dev.net) is correct for your site as well.

[Phill Pafford]

follow up question: I'm using Bamboo Data Center webhook to post to Compass, but looks like there is a date format issue

Bamboo uses ISO 8601, But Compass requires RFC 3339 

Bamboo example payload: https://confluence.atlassian.com/bamboo/using-webhooks-1018270680.html

My question is, can I override Compass to except the ISO 8601 format as well? 

example error:

{"message":"The webhook could not be processed: Error calling createEvent in graphql gateway. Error(s): Variable 'v0' has an invalid value: Invalid RFC3339 value : ''. because of : 'Text '' could not be parsed at index 0'","success":false,"parameters":{}}%

[Phill Pafford]

@Enrique Serrano Valle posted here as well https://community.atlassian.com/forums/Bamboo-questions/Bamboo-Data-Center-Webhook-Variables/qaq-p/3070909#M35006

[Enrique Serrano Valle]

That's a good point, @Phill Pafford . I don't think we can currently change the format that Compass accepts, but we'll track it in the future roadmap.

I was going to suggest wiring your Bamboo pipeline directly to the Compass API to send events (which is a more powerful integration mechanism) and then I realized that you were already doing that back in the day.