AutomationFlowsGeneral › Teamretro: Onboard a User Onto a Team (account Key)

Teamretro: Onboard a User Onto a Team (account Key)

TeamRetro: Onboard a user onto a team (account key). Uses formTrigger, n8n-nodes-teamretro. Event-driven trigger; 4 nodes.

Event trigger★★☆☆☆ complexity4 nodesForm TriggerN8N Nodes Teamretro
General Trigger: Event Nodes: 4 Complexity: ★★☆☆☆ Added:

The workflow JSON

Copy or download the full n8n JSON below. Paste it into a new n8n workflow, add your credentials, activate. Full import guide →

Download .json
{
  "name": "TeamRetro: Onboard a user onto a team (account key)",
  "nodes": [
    {
      "id": "tr0700-0000-0000-0000-000000000001",
      "name": "Account key required",
      "type": "n8n-nodes-base.stickyNote",
      "typeVersion": 1,
      "position": [
        -60,
        40
      ],
      "parameters": {
        "width": 460,
        "height": 340,
        "color": 3,
        "content": "## Account-scoped key required\n\n**Add User** provisions a user in the account, so it needs an **account-scoped key (`tra_`)** from *Account \u2192 Settings \u2192 API & SCIM*. A team-scoped key (`trt_`) is rejected with **403**.\n\n1. Pick your account-scoped TeamRetro credential on **both** TeamRetro nodes.\n2. Open the **Onboarding Form** node and copy its **Production URL** \u2014 that's the link you send to whoever fills it in.\n3. **Activate** the workflow.\n\nAlready-existing users are fine: *Add User* is a PUT, so re-submitting the same email updates rather than duplicates."
      }
    },
    {
      "id": "tr0700-0000-0000-0000-000000000002",
      "name": "Onboarding Form",
      "type": "n8n-nodes-base.formTrigger",
      "typeVersion": 2.2,
      "position": [
        460,
        160
      ],
      "parameters": {
        "path": "teamretro-onboarding",
        "formTitle": "TeamRetro onboarding",
        "formDescription": "Provision a TeamRetro user and add them to a team.",
        "formFields": {
          "values": [
            {
              "fieldLabel": "Full name",
              "requiredField": true
            },
            {
              "fieldLabel": "Email",
              "fieldType": "email",
              "requiredField": true
            },
            {
              "fieldLabel": "Team ID",
              "requiredField": true
            }
          ]
        },
        "options": {}
      }
    },
    {
      "id": "tr0700-0000-0000-0000-000000000003",
      "name": "Add User to Account",
      "type": "n8n-nodes-teamretro.teamRetro",
      "typeVersion": 1,
      "position": [
        700,
        160
      ],
      "parameters": {
        "resource": "user",
        "operation": "add",
        "email": "={{ $json['Email'] }}",
        "additionalFields": {
          "name": "={{ $json['Full name'] }}",
          "active": true
        }
      }
    },
    {
      "id": "tr0700-0000-0000-0000-000000000004",
      "name": "Add Member to Team",
      "type": "n8n-nodes-teamretro.teamRetro",
      "typeVersion": 1,
      "position": [
        940,
        160
      ],
      "parameters": {
        "resource": "teamMember",
        "operation": "add",
        "teamId": "={{ $('Onboarding Form').item.json['Team ID'] }}",
        "email": "={{ $('Onboarding Form').item.json['Email'] }}",
        "additionalFields": {
          "name": "={{ $('Onboarding Form').item.json['Full name'] }}",
          "teamAdmin": false
        }
      }
    }
  ],
  "connections": {
    "Onboarding Form": {
      "main": [
        [
          {
            "node": "Add User to Account",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Add User to Account": {
      "main": [
        [
          {
            "node": "Add Member to Team",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "settings": {
    "executionOrder": "v1"
  }
}
Pro

For the full experience including quality scoring and batch install features for each workflow upgrade to Pro

About this workflow

TeamRetro: Onboard a user onto a team (account key). Uses formTrigger, n8n-nodes-teamretro. Event-driven trigger; 4 nodes.

Source: https://github.com/TeamRetroHQ/n8n-nodes-teamretro/blob/main/examples/07-onboard-user-to-team.json — original creator credit. Request a take-down →

More General workflows → · Browse all categories →

Related workflows

Workflows that share integrations, category, or trigger type with this one. All free to copy and import.

General

⚠️ Important: This workflow uses the Autype community node and requires a self-hosted n8n instance.

Form Trigger, N8N Nodes Autype
General

Let a user load multiple files with a Form node, and process the binary data. A very important workflow for many tools.

Read Write File, Form Trigger
General

Turn a .rvt project into open, analysis-ready data (XLSX + optional DAE/PDF) using the RvtExporter.exe from the DDC Revit toolkit. This n8n template provides a Form UI to set paths and flags, then run

Form Trigger, Execute Command
General

Post on X. Uses airtop, executeWorkflowTrigger, formTrigger, stopAndError. Event-driven trigger; 10 nodes.

Airtop, Execute Workflow Trigger, Form Trigger +1
General

05 – Expense Approval via Email (Send & Wait). Uses formTrigger, n8n-nodes-resend. Event-driven trigger; 8 nodes.

Form Trigger, N8N Nodes Resend