Mattermost - cannot get teams parameter with "invite a user to team" action

Questions
1

Describe the problem/error/question

Hello, I would like to add users to a team with Mattermost Node. I’m trying to use the “Invite a user” action in the User module, but the Team Name or ID field doesn’t populate the list of teams :

image
image363×340 8.2 KB

In the Mattermost logs, i see the query looping with the correct status code :

 s_code":"200"}
{"timestamp":"2025-11-17 11:22:17.860 +01:00","level":"debug","msg":"Received HTTP request","caller":"web/handlers.go:175","method":"GET","url":"/api/v4/users/me/teams","request_id":"zf61yzye43dcuxqmwb8c5duh5h","user_id":"123456","statu                       s_code":"200"}
{"timestamp":"2025-11-17 11:22:17.880 +01:00","level":"debug","msg":"Received HTTP request","caller":"web/handlers.go:175","method":"GET","url":"/api/v4/users/me/teams","request_id":"91jn48en9jrzfy9s8ifx63bhkc","user_id":"123456","statu                       s_code":"200"}

What is the error message (if any)?

Here are the n8n logs :

2025-11-17 11:26:46.434 | 2025-11-17T10:26:46.434Z | debug | Execution added {"executionId":"337","file":"active-executions.js","function":"add"}
2025-11-17 11:26:46.435 | 2025-11-17T10:26:46.435Z | debug | Execution for workflow My workflow was assigned id 337 {"executionId":"337","file":"workflow-runner.js","function":"runMainProcess"}
2025-11-17 11:26:46.445 | 2025-11-17T10:26:46.444Z | debug | Execution ID 337 will run executing all nodes. {"executionId":"337","file":"manual-execution.service.js","function":"runManually"}
2025-11-17 11:26:46.445 | 2025-11-17T10:26:46.445Z | debug | Workflow execution started {"workflowId":"aSFyNu4hXAVVFZrV","file":"logger-proxy.js","function":"exports.debug"}
2025-11-17 11:26:46.445 | 2025-11-17T10:26:46.445Z | error | Problem with execution 337: The workflow has issues and cannot be executed for that reason. Please fix them first.. Aborting. {"file":"workflow-runner.js","function":"processError"}
2025-11-17 11:26:46.445 | 2025-11-17T10:26:46.445Z | error | The workflow has issues and cannot be executed for that reason. Please fix them first. (execution 337) {"file":"error-reporter.js","function":"defaultReport"}
2025-11-17 11:26:46.445 | 2025-11-17T10:26:46.445Z | debug | Execution finalized {"executionId":"337","file":"active-executions.js","function":"finalizeExecution"}
2025-11-17 11:26:46.447 | 2025-11-17T10:26:46.446Z | debug | Execution removed {"executionId":"337","file":"active-executions.js"}
2025-11-17 11:26:46.447 | 2025-11-17T10:26:46.447Z | debug | Executing hook (hookFunctionsSave) {"executionId":"337","workflowId":"aSFyNu4hXAVVFZrV","file":"execution-lifecycle-hooks.js"}
2025-11-17 11:26:46.447 | 2025-11-17T10:26:46.447Z | debug | Save execution data to database for execution ID 337 {"executionId":"337","workflowId":"aSFyNu4hXAVVFZrV","finished":false,"stoppedAt":
"2025-11-17T10:26:46.445Z","file":"shared-hook-functions.js","function":"updateExistingExecution"}
2025-11-17 11:26:46.464 | 2025-11-17T10:26:46.463Z [Rudder] debug: no existing flush timer, creating new one
2025-11-17 11:26:46.465 | 2025-11-17T10:26:46.465Z | debug | Executing hook (hookFunctionsPush) {"executionId":"337","pushRef":"xycdheiuci","workflowId":"aSFyNu4hXAVVFZrV","file":"execution-lifecycle-hooks.js"}
2025-11-17 11:26:46.465 | 2025-11-17T10:26:46.465Z | debug | Pushed to frontend: executionFinished {"dataType":"executionFinished","pushRefs":"xycdheiuci","file":"abstract.push.js","function":"sendTo"}
2025-11-17 11:26:46.466 | 2025-11-17T10:26:46.466Z | error | The workflow has issues and cannot be executed for that reason. Please fix them first. {"file":"error-reporter.js","function":"defaultReport"}
2025-11-17 11:26:56.463 | 2025-11-17T10:26:56.463Z [Rudder] debug: in flush
2025-11-17 11:26:56.463 | 2025-11-17T10:26:56.463Z [Rudder] debug: cancelling existing flushTimer...
2025-11-17 11:27:15.239 | 2025-11-17T10:27:15.238Z | debug | Querying database for waiting executions {"scopes":["waiting-executions"],"file":"wait-tracker.js","function":"getWaitingExecutions"}

I tried with different access tokens (both admin and non-admin users) with no effect. Other Mattermost actions are working fine (Get Users, Create User, etc.).

Has anyone already successfully used this node?

Thanks in advance for your help !

Information on your n8n setup

  • n8n version: 1.119.1
  • Database (default: SQLite): SQlite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system:
2

It looks like the Mattermost node is trying to fetch your teams but the dropdown isn’t populating properly, even though the API calls are successful (status 200). Here are a few things to try:

• **Check your Mattermost credentials** - Make sure the user account has proper permissions to view and invite users to teams

• **Verify team membership** - The API call `/api/v4/users/me/teams` only returns teams the authenticated user is a member of, so ensure your credential user belongs to the teams you want to see

• **Try refreshing the connection** - Sometimes re-selecting the credential or refreshing the node can help reload the team options

• **Manual entry workaround** - If the dropdown still doesn’t work, you can try entering the team ID directly instead of using the dropdown (you can get team IDs from your Mattermost admin panel or API)

The looping requests in your logs suggest the node might be having trouble processing the API response, so double-checking permissions is likely your best first step.