I currently work on an integration that uses the API v2 to get some item fields in a custom action. But the query returns different response depending on the trigger that is used. If I use a trigger that directly calls the action, like ‘when status changes’ or ‘when an update is created’, then the query with the provided itemId is successful. But when a time trigger, like ‘scheduled trigger’ or ‘when date has passed’ fires and calls the same action, then the query with a valid itemId fails with message ‘Variable itemId of type Int! was provided invalid value’.
Any ideas what is going wrong here?
Hi. @Helen and @basdebruin thanks for your hints. And yes, Bas, you are totally right. After I parse the itemId to an int and provide it then to the monday API function, it works for both cases (direct and time based triggers). It is still curious why there is a difference when I use the itemId without parsing (the integration runs as a node.js application), but I think it is hard to find out.
Thanks again and CU, Marcus
It depends how you declare variable in nodeJS. If you don’t declare the variable returned by the API the variable will be of the type returned (which is always as string). Therefore you need to parseInt all boardId, ItemId, personId, TeamId and others. I agree it would be nice if the API allows strings as it also returns strings .
With some further logging of the integration I observed that the payload contains different types for the itemId depending on the performed trigger. As mentioned in my initial post, e.g. the triggers ‘when status changes’ or ‘when an update is created’ provides the itemId as number/integer, and the triggers like ‘scheduled trigger’ or ‘when date has passed’ send the itemId as string. That’s why I stumbled upon, because I did no cast the itemId when using the monday API functions and was wondering about the different behavior. @Helen maybe you want to take that with you if it makes sense to unify the types of ids in the payload for all kind of triggers.
I actually just tested this out and I was able to get the itemId returned as a string when using the “When status changes” trigger. Maybe you’re seeing a different result based on how you’re getting the response?
Hi @Helen
for all recipes I built, I did the same: each of the used trigger have the itemId as output field and I just uses this as the trigger output field key for the itemId field in my custom action. Did you try the same? Could it be that we see different versions of the triggers?
.