n8n is a tool that connects apps and systems to each other. You build workflows by linking blocks together on a canvas, with no code. You can use n8n in the cloud or run it on your own server. Every workflow starts with a trigger: something that happens, or a set time, such as every Monday at 7am. The actions follow: what should happen next, automatically.
​
With the Oneteam blocks in n8n, Oneteam can be the trigger, the action, or both. That lets you connect Oneteam to tools such as Microsoft Teams, Slack, Outlook, and Google Sheets, or to your own systems, and chain steps inside Oneteam. You can also use n8n to pull data out of Oneteam, such as onboarding and course progress, survey results, and analytics.

Oneteam provides the Oneteam blocks for n8n and a set of templates to get you started. As an admin, you build and manage the workflows yourself in your own n8n environment. That way you decide which processes to automate, and how.
​
The integration costs nothing extra on the Oneteam side. If you use n8n Cloud, you pay n8n for a plan. If you run n8n on your own server, you take care of the hosting.

There are roughly four ways to use Oneteam in a workflow. You can also combine them in a single workflow.

n8n does not replace your HR or payroll integration. Your employee records stay in sync through integrations such as Loket, AFAS, and Nmbrs, and rosters through your scheduling integration. n8n is for everything around that: alerts, tasks, messages, invites, and reports.

Oneteam works with both n8n and Zapier. Zapier is the quickest way to get started, especially if you already use it or do not have a technical background. See Connect Oneteam to Zapier.

n8n is a better fit if you want to run your automations on your own server, expect a high volume, build longer workflows, or also want to pull data out of Oneteam.

n8n talks to Oneteam through an API key. The key belongs to your organisation, not to a person, and it controls what n8n is allowed to do.
​
1. In the dashboard, go to Settings and open API keys.
2. Click Create API key.
3. Give the key a recognisable Name, for example n8n.
4. Under Scopes, select only what your workflows need. The table below shows which scope goes with which step.
5. Click Create and copy the key. It starts with sa_.
​
You only see the key once. Keep it in a password manager and do not share it over chat or email. If you lose it, or it leaks, revoke it under API keys and create a new one.

Any key can list forms and courses. If you still get a permissions error, it tells you which scope is missing.
​
Chat messages are sent on behalf of the admin who created the API key. If you want messages to come from HR or a shared account, create the key with that account.
​
​This is what the page looks like. The keys and the organisation name are hidden.

1. In n8n, open Settings and go to Community nodes.
2. Click Install and enter the package name n8n-nodes-oneteam.
3. Confirm the community nodes notice and install the package.
4. Refresh the page. When you search for a block, you will now see Oneteam and Oneteam Trigger.

1. Open an Oneteam or Oneteam Trigger block.
2. Under Credential to connect with, choose Create new, then Oneteam API.
3. Paste the API key and leave the Base URL set to https://api.oneteam.io.
4. Save. A green tick means the connection works.

Start with a trigger: Oneteam Trigger for an event in Oneteam, a block from another tool such as Google Sheets, or a Schedule block for a set time. Then add the blocks that should do something. In the Oneteam block you first pick a Resource, what it is about, and then an Operation, what should happen. For example Employee with Invite, or Task with Create.
​
Drag data from an earlier step from the left panel into a field, such as a name, an email address, or a form answer. For forms and courses, pick one specific form or course, or leave the field empty to react to all of them.
​
You cannot look up an employee by name. Use the email address or the ID from an earlier step, or fetch a list of employees first.
​
As soon as you set the workflow to Active, n8n sets up the connection with Oneteam itself. Under Settings > Webhooks you will see a row such as n8n: form.submission_created. You do not need to create it yourself. To send events to your own system, read Using webhooks in Oneteam.

These events can start a workflow from the Oneteam Trigger block.​

For privacy reasons, there is no trigger for anonymising an employee.

This is what the Oneteam block can do, after any trigger, whether it comes from Oneteam, another tool, or a schedule.

An employee uses the Maintenance form to report that the fridge has stopped working. The site immediately gets a task, the site manager gets a chat message with all the details, and the report is set to Pending.
​
1. Create a new workflow and start with Oneteam Trigger and the New Form Submission event. Select the maintenance form.
2. Use an API key with the scopes Manage webhooks, View form reports, Create tasks, Send chat messages, and Update form responses.
3. Click Listen for test event and submit the form once, so n8n has a sample.
4. Add an Oneteam block with Task and Create. Choose whether the task is for one employee or for the site team, and put the answers in the title or description.
5. Add an Oneteam block with Chat Message and Send, to the site manager's email address, with the answers in the message.
6. Add an Oneteam block with Form and Update Submission Status. Use the submission ID from the trigger and pick the Pending status.
7. Test the workflow and set it to Active in the top right.
​
Is the form anonymous? Then the submitter stays empty, but the answers still come through. Want the report in Teams or Slack too? Add a Teams or Slack block to the same workflow.

Every week you add new agency and seasonal workers to a Google Sheet, with first name, last name, email address, site, and role. With this workflow they get an Oneteam invite automatically.
​
1. Start with a Google Sheets trigger that reacts to a new row.
2. Add an Oneteam block with Employee and Invite, and map the columns to first name, last name, email address, community, and role.
3. Use an API key with the Create employees scope. If you also assign a community or role, add Manage employees.
4. Test with one row and set the workflow to Active.
​
The community and role must already exist in Oneteam, with exactly the same name as in the sheet. n8n does not create them for you. Want to welcome the new starter too? Create a second workflow with Employee Activated as the trigger and a chat message as the action.

For the Monday operations meeting, you want to see how far new starters at each site are with their onboarding and mandatory courses. No Oneteam event is needed: n8n pulls the data at a set time.
​
1. Start with a Schedule block set to Monday 07:00.
2. Add an Oneteam block with Onboarding and Get Statistics or List User Progress.
3. Add an Oneteam block with Course and Get Statistics or List Progress.
4. Write the results to Google Sheets, per site.
5. Use an API key with the View onboarding statistics scope. If you get a permissions error, it tells you which scope to add.
6. Set the workflow to Active.
​
You can pull survey results, performance evaluations, or analytics the same way. Analytics needs the View analytics scope.

Test workflow or Execute step runs the workflow once while you watch. Only once you set the workflow to Active does it run automatically, even when n8n is closed. If it stays Inactive, nothing happens after the test.