This looks like an error coming from the API you are calling, seemingly complaining about a bad array. Your request doesn’t seem to require an array though, so I am not 100% sure what’s needed here. Perhaps you can check with the team managing the API you are calling how exactly your request should look like?
I’m not sure if you’ve already solved this issue, but the new version of n8n has an option to import a curl command, and it helped me solve this problem.
hi there,
I’m creating GLPI integration with n8n and I’ve map main functions. In the future, I belive to upgrade it to a node for the comunity.
The GLPI’s API request two steps to do anythink.
Use app-key and user-token to get session-key
Use session-key to make your real request such like search or update items.
-- geting session token
curl -X GET \
-H 'Content-Type: application/json' \
-H "Authorization: user_token MyUserTokenGeneratedByGLPI" \
-H "App-Token: MyAppTokenGeneratedByGLPI" \
'https://my-glpi/apirest.php/initSession'
-- making a simple search for a new tickets
curl -X GET \
-H 'Content-Type: application/json' \
-H "Session-Token: SessionTokenReturnedFromINITSESSION" \
-H "App-Token: MyAppTokenGeneratedByGLPI" \
'https://my-glpi/apirest.php/search/Ticket'?\
'criteria\[0\]\[link\]=AND&'\
'criteria\[0\]\[field\]=12&'\
'criteria\[0\]\[searchtype\]=equals&'\
'criteria\[0\]\[value\]=1'
The ‘criteria’ can be found using chrome dev tools. When you click into search button at Tickets page, a http_request are called with the same extructure.
If it works at console, you can copy and paste the curl command into an Http request node and n8n will configure the node for you.
Hi Mauricio, I’m starting to use GLPI and would love to integrate it with n8n… You mentioned that “I belive to upgrade it to a node for the comunity.” - are you still a believer or is there a chance it will materialize and be shared? I’m trully interested!!