TeamRetro ✖️ n8n
How to set up the n8n integration
To configure this integration you must be a TeamRetro Team Administrator.
n8n is a workflow automation platform that lets you connect TeamRetro to over 1,000 other tools — including tools we don't offer a native integration for — and build multi-step automations around your retrospectives, health checks and estimation sessions.
With the TeamRetro node for n8n you can:
- Start a workflow the moment something happens in TeamRetro (a retrospective completes, a health check finishes, an action item is created, kudos is given and more)
- Read and manage your TeamRetro data mid-workflow
- Retrospectives, ideas and reports
- Health checks and health trends
- Action items and parked items
- Teams, team members and agreements
Looking for ideas? See our ready-made workflow templates on the TeamRetro n8n page.
Before you start
You will need:
- A TeamRetro account with API access enabled (Enterprise plan)
- An n8n account — either n8n Cloud or a self-hosted n8n instance
- A TeamRetro API key (steps below)
How to create your API key
- In TeamRetro, go to
- Account -> Settings -> API & SCIM
- Team -> Settings -> API
- Select CREATE API KEY
- Choose the scope to be covered by the API key. A team-scoped key (
trt_) can only see one team — this is the safest choice for most workflows. An account-scoped key (tra_) can see every team, and is needed for account-level insights and user management. -
Copy the key somewhere safe. For security reasons, TeamRetro will only show it to you once.
[SCREENSHOT: API & SCIM settings page with the Create API Key button highlighted]
How to install the TeamRetro node
- On n8n Cloud: search for "TeamRetro" in the nodes panel and select Install. (If you can't see it, ask your n8n instance owner — only instance owners and admins can install community nodes.)
-
On self-hosted n8n: go to Settings —> Community Nodes —> Install, enter
n8n-nodes-teamretroand select Install.
[SCREENSHOT: n8n community nodes install dialog with n8n-nodes-teamretro entered]
How to connect your TeamRetro account
- In any workflow, add a TeamRetro node
- Under Credential to connect with, select Create new credential
- Paste in your API key
- Choose your Region — select EU if your TeamRetro account is hosted in the European Union, otherwise select US. (Not sure? Check the address bar when you're logged in to TeamRetro — EU accounts use eu.teamretro.com.)
-
Select Save. n8n will test the connection for you.
[SCREENSHOT: TeamRetro credential dialog in n8n showing the API key field and region selector]
How to start workflows from TeamRetro events
The TeamRetro Trigger node starts a workflow whenever something happens in TeamRetro — no polling, events arrive in real time.
- Add a TeamRetro Trigger node to your workflow
- Tick the events you want to listen for (for example Retrospective Completed)
- Open the node's Webhook URLs tab and copy the Production URL
- In TeamRetro, go to SETTINGS —> Integrations —> Webhooks —> Add webhook
- Paste the URL and tick the same events you selected in n8n
- Copy the signing secret TeamRetro shows you, and paste it into the trigger node's Signing Secret field. This lets n8n verify that every delivery really came from TeamRetro.
-
Activate your workflow, then use Send test on the TeamRetro webhook to confirm everything is connected
[SCREENSHOT: TeamRetro webhook settings with URL field and event checkboxes]
Note: each workflow has its own Production URL. If you import several of our workflow templates, repeat these steps once per workflow. If you duplicate a workflow, the copy gets a new URL — remember to register it.
What events can I listen for?
| Category | Events |
|---|---|
| Meetings | Retrospective created / completed, Health check created / completed, Estimation created / completed |
| Actions | Created, updated, deleted, completed, assignee changed, due date changed |
| Agreements | Created, updated, deleted |
| People | Mention created, kudos created, team member invited / removed |
Troubleshooting
- The trigger never fires — check the workflow is Active (not just saved), and that the events ticked in TeamRetro's webhook match the events ticked in the trigger node.
- Deliveries stopped after I changed the webhook — if you regenerate the signing secret in TeamRetro, paste the new secret into the trigger node.
- 401 or 403 errors on a TeamRetro node — check your API key's scope (team keys can't access account-level operations) and that the credential's region matches your account.
- Submitting an estimate returns 403 — submitting estimates isn't available via API key; all other estimation operations work normally.
Related articles
- TeamRetro API
- How to set up webhooks
- How to set up the Zapier integration