Grafana n8n integrationAutomate Grafana with n8n.

Adds a dashboard to the instance and hands back its UID, the short identifier every later dashboard step asks for.

• Title: the name shown in the Grafana dashboard list, required, often built from the item before it with an expression such as {{ $json.client }}.
• Folder Name or ID: inside Additional Fields, choose the folder from the list or pass an ID through an expression. Left unspecified, the dashboard is saved to the General folder.

Erases one dashboard from Grafana, which is why the workflow should only reach this step once something upstream has confirmed the dashboard is stale.

• Dashboard UID or URL: the alphabetic identifier, cIBgcSjkk style, or the full dashboard URL when that is what the previous node carries.

Reads a single dashboard back, so the workflow can look at what is there before anything changes it.

• Dashboard UID or URL: the same identifier the delete step uses, such as cIBgcSjkk, or the URL copied out of the browser bar.

Lists the dashboards of the instance, one n8n item per dashboard, ready to loop over.

• Return All: on, n8n follows the API pages until the last dashboard is in. Off, Limit caps how many come back, which is plenty for a quick sample.
• Search Query: under Filters, keeps only the dashboards whose name matches the text. Useful the day a naming convention exists.

Edits a dashboard in place: a new name, a different folder, or both, while the UID stays the same.

• Dashboard UID or URL: points at the dashboard to edit, for example cIBgcSjkk.
• Title: in Update Fields, the new title to display.
• Folder Name or ID: also in Update Fields, moves the dashboard into another folder. Unspecified, it goes to the General folder.

Opens a team in Grafana, the group that members are attached to in the operations further down this list.

• Name: the team label, required, something like Engineering.
• Email: inside Additional Fields, the shared address of the team, for example engineering@n8n.io.

Drops a team from the instance, the cleanup step for a group that no longer exists on the org chart.

• Team ID: the identifier of the team to delete, required. Get Many Teams upstream supplies it, so nothing gets typed by hand.

Pulls one team record back, which gives the rest of the workflow something solid to test before it acts.

• Team ID: the identifier of the team to retrieve, required, usually carried over from an earlier node as {{ $json.id }}.

Returns the teams of the instance as separate items, the usual opening move of any bulk team job.

• Return All: enabled, n8n pages through the API until the last team. Disabled, Limit sets the ceiling.
• Name: under Filters, narrows the result to the teams that match that name.

Changes a team that already exists, keeping its identifier stable while the label or the contact address moves.

• Team ID: required, tells Grafana which team receives the edit.
• Name: in Update Fields, the new team name, Engineering Team for instance.
• Email: also in Update Fields, the address the team is reached on, such as engineering@n8n.io.

Places an existing Grafana user inside a team, the access step at the heart of most onboarding flows.

• User Name or ID: pick the person from the list n8n loads, or specify an ID with an expression when the value comes from an earlier node.
• Team Name or ID: the same choice on the team side, selected in the list or resolved through an expression.

Lists who belongs to one given team, one item per member.

• Team Name or ID: required, the team whose members are read, chosen in the list or given as an ID through an expression.
• Return All: on for the whole roster, off to stop at Limit members.

Takes one member out of a team while the team itself stays in place.

• User Name or ID: the person to pull out, selected from the list or supplied as an ID.
• Team Name or ID: the team losing that member, same list or expression choice.

Removes a user from the current organization, the one the credential points at.

• User ID: the identifier of the user to delete, required. A Get Many Users step placed before it hands over the value, so nothing has to be looked up by hand in the admin screens.

Brings back the users of the current organization so the workflow can audit them or loop through them.

• Return All: ticked, every user comes through, page after page. Unticked, Limit decides how many, which is the right setting while you are still shaping the workflow.

Moves the role a user holds in the current organization, which is how permissions change without touching the account itself.

• User ID: required, the account that receives the edit.
• Role: in Update Fields, one of Admin, Editor or Viewer.