Pabbly ↔ Klick-Tipp / 403 Error / Tag Contact Endpoint

[Finding Frodo]

Your Task History ID

IjU3NjUwNTY5MDYzMDA0M2M1MjY0NTUzZDUxM2E1MTYyNTQzMTBmMzAi_pc

Good morning,

there is a minor error in the following integration:

App: Klick-Tipp
Action Event: Tag Contact
Parameter: Tag

The tag parameter can be a Tag-ID (Integer) or an array of Tag-IDs (Array of Integers).

Currently Pabbly Connect offers a selectbox for 1 of the predefined Tags. The selected value seems to be sent as String.

This is the reason, why Klick-Tipp returns a 403 error. (Regardless, the 403 error is confusing and not meaningful, but that's not a Pabbly problem.)

I have contacted Klick-Tipp already and they say this will be fixed soon, to accept also a single Tag-ID as String. However, I think also Pabbly should fix this and send only the appropriate formats (Int or Int[]).

To get a quick fix for myself: If I switch from selectbox-mode to manual input, can I then send the IDs as Int or Array?

like static value: [ 123456 ]

Or will this result in a stringified array? like: "[ 123456 ]"

 

[Preeti Paryani]

Hello @Finding Frodo,

Thank you for bringing this to our attention.

To help us better assist you with your use case, could you please share the official API documentation or reference that confirms Klick-Tipp accepts the tag parameter as an Integer or an array of Integers?

Once we have that, we’ll be able to guide you more accurately regarding how to pass the tag values, whether through static input or in array format, and evaluate if any adjustments are needed on our end.

 

[Finding Frodo]

Thanks for you quick reply.

The only API documentation I could find is this one. You won't like it.

Here is what support told me (translated):

We have now been able to recreate the behavior. The error occurs when the tagids are passed in the JSON body as a string instead of an array – i.e., "tagids": "12345" instead of "tagids": [12345]

In this case, the API responds with a 406 Not Acceptable , but misleadingly returns a 403 in the JSON. This explains the confusion.

A fix is already in progress. We are adapting the endpoint to behave more consistently with this input. The patch will be merged shortly.

The correct format for the tagids parameter for the API endpoint is as follows:

{
"email": "[email protected]",
"tagids": [123, 555]
}

You can pass one or more tag IDs here. Due to an unaddressed side effect, "123" was also possible for individual tag IDs. We have already prepared a fix to restore the old functionality.
Otherwise, you are welcome to use the other Change the format (which allows you to assign multiple tags if needed)

 

[Preeti Paryani]

Hello @Finding Frodo,

Thank you for sharing the details.

Please allow us some time to investigate this further. We’ll get back to you with an update as soon as we have more information.

Appreciate your patience!

 

[Preeti Paryani]

Hello @Finding Frodo,

Upon investigating and reviewing the action configuration, we can confirm that it has been set up as per the recommendations provided by the Klick-Tipp team. Additionally, it appears to be working correctly for other users using the same configuration.

Given this, the issue seems to be specific to your Klick-Tipp account. We recommend reaching out to the Klick-Tipp support team to have this checked further from their end.

Please feel free to share any updates you receive from them