Issues with Webhook component when using a Payload Template and Variables

[Bryan]

Anyone else having issues with the Webhook component when using payload templates and setting variables?

 

I have created a very simple payload template with a single variable within it:

 

I then created a job variable that will map to the above payload variable which I called the same name:

I added the webhook component to the canvas and configured it by setting the Incoming webhook URL, selecting the Payload Template I created, and then mapped the payload variable to the job variable. The error comes when I map the payload variable to the job variable.

 

I cannot get this Payload variables to map without validation errors. Unlike other components, the webhook post component will not run at all when there are validation errors.

 

Anyone else experience this? If so, were you able to get around the issue? If you were able to resolve the issue, how did you do it? Thanks for the help in advance!

 

Product: Matillion for Snowflake (Enterprise)

Version: 1.53.8

Cloud Provider: AWS

Instance: Single (non-clustered) Instance as m5.Large

[DirkZ]

Hello,

try "${variable_name}", this should work.

 

Regards,

DIrk

[MichaelBoucht]

Hiya,

 

This issue has probably been day one of Matillion Webhook component.

 

https://matillioncommunity.discourse.group/t/matillion-etl-version-1-48-is-here-featuring-webhook-post-component/1191

 

At least the screenshots looks quite the same as your issue :) Didn't go further with this one at that point. But would be interesting to actually have these pretty formatted Teams-messages popping from Matillion.

 

It might be a bug, due the value field doesn't really accept any values.

 

 

 

[Bryan]

I should have mentioned in my original post but I have already tried what you recommended.

[Bryan]

Thanks for the response @MichaelBoucht (Customer)​. I have had a support case open for a few weeks now. The only response I have received indicates that Matillion can't replicate the issue on their end. I am glad I am not the only one that has had this issue. Thanks again and I will post the results of that case here once it's resolved.

[Bryan]

Hi @MichaelBoucht​ and all others that read this thread. I did in fact find a bug in the Webhook Post component. This affects all versions up to and including 1.54 and likely a few more versions after until this bug is fixed.

The situation is this, when you use a Payload Variable and the variable has a capital anywhere in the variable name, it will appear to work until you go to map the Payload Variable to a Target Value but will fail at that point. Long story short, you can't use a capital any where in the name. Here is an example:

This works:

This doesn't work:

I hope this helps others.

[MichaelBoucht]

Ah nice find @Bryan​!

[ian.funnell]

Good find @Bryan​, confirming it's the capitals which are causing the problem.

[MichaelBoucht]

Had fun playing around with this. Managed to get a giphy gif sent over to our monitoring channel in Teams. My co-workers must hate me with my gifs.

[ian.funnell]

Next challenge @MichaelBoucht​ - or maybe a feature request - try and get a giphy gif into a Payload Template :-)

[MichaelBoucht]

@ian.funnell​ That's giphy is a variable in a Payload Template, was planning on having a massive list of urls stored in Snowflake table that are randomized dependent on the outcome... And maybe have a this whole component as a 'shared job'

Hmm, I think I am using too much time for this ;-)

[Bryan]

Yes, any capital in the Payload Variable name will cause this issue.