Capstone Project Part 3 - Help

 Hi ​@mr.n,

I found another simple way to handle the webhook response, which may help simplify the implementation.

In my case, I am taking the webhook response directly as a variable ($sResponse$) instead of working with the response as a Record.
 

I then pass this variable directly to a single JSON Parser – JSON to Dictionary action. In the JSON Parser, instead of using the Dictionary output, I selected “Multiple variables” and mapped the JSON keys directly to individual variables.

For example:

• id → $sId$
• datetime → $sDatetime$
• opportunity → $sOpportunity$

This allows the required values from the webhook JSON payload to be extracted using a single JSON Parser action, without needing multiple JSON Parser actions or additional handling of the Record.

I found this approach useful for simplifying the workflow when the JSON structure is known and the required fields need to be mapped directly to variables.

Hope this helps others facing a similar issue!

Hi All

Following up on this, our Control Room team have confirmed that in the .41 release of the product, the incoming webhooks no longer accept application/text content-type headers, which, the form I built in the video, uses.

The simplest fix is to do what ​@mr.n or ​@adhi_V have shown, above.

I’m going to edit the corresponding Capstone video and show users how they can amend their task bot. Expect that to go live next week.

Thanks

Oli

Hi All

The video has been amended and updated in the University.

A special thank you to all for raising this and sharing your fixes for other learners to follow.

Oli