n8n-nodes-strety

n8n community node for Strety — the EOS/Traction platform for goals, scorecards, issues, to-dos, and more. AI-agent ready (usableAsTool: true).

Install

n8n Community Nodes (recommended)

1. Open your n8n instance → Settings → Community Nodes.
2. Search for n8n-nodes-strety and install.

Manual (self-hosted)

npm i n8n-nodes-strety

Then restart n8n.

Credentials & Setup

Strety uses OAuth2 (authorization code flow). You must register your own OAuth app inside Strety before connecting.

1. Register a Strety OAuth app

1. Log in to Strety and go to My Integrations → My Apps (URL: https://2.strety.com → top-right menu → My Apps, or navigate to https://2.strety.com/settings/my-apps).
2. Create a new app. Give it a name (e.g. "n8n Integration").
3. Set the Redirect URI to your n8n OAuth callback:

   https://<your-n8n-host>/rest/oauth2-credential/callback

   Replace <your-n8n-host> with your actual n8n domain (e.g. n8n.example.com).
4. Enable the read and write scopes.
5. Save the app — Strety will display your Client ID and Client Secret.

2. Add the credential in n8n

1. In n8n, go to Credentials → New Credential and search for Strety OAuth2 API.
2. Enter the Client ID and Client Secret from the previous step.
3. Click Connect — n8n will redirect you to Strety to approve the connection.
4. After approval you will be returned to n8n with the credential active.

The credential will be used automatically when you add a Strety node to a workflow.

Resources & Operations

The node exposes 12 resources. Resources with only read operations are marked (read-only).

| Resource | Get Many | Get | Create | Update | Delete | Extra operations | |---|---|---|---|---|---|---| | Todo | yes | yes | yes | yes | yes | — | | Goal (Rock) | yes | yes | yes | yes | yes | Backlog, Unbacklog, List/Get/Create/Update/Delete Check-In | | Headline | yes | yes | yes | yes | yes | — | | Issue | yes | yes | yes | yes | yes | — | | Meeting | yes | yes | — | — | — | (read-only) | | Message | yes | yes | yes | yes | yes | — | | Metric | yes | yes | yes | yes | yes | List/Get/Create/Update/Delete Check-In | | Person | yes | — | — | — | — | (read-only) | | Playbook | yes | yes | yes | yes | yes | — | | Playbook Folder | yes | yes | yes | yes | yes | — | | Project | yes | yes | — | — | — | (read-only) | | Team | yes | yes | — | — | — | (read-only) |

Goal (Rock) — extra operations

| Operation | Description | |---|---| | Backlog | Move a goal/rock to the backlog (POST goals/{id}/backlog) | | Unbacklog | Restore a backlogged goal back to active (DELETE goals/{id}/backlog) | | List Check-Ins | List all progress check-ins for a goal (pagination supported) | | Get Check-In | Retrieve a single check-in by ID | | Create Check-In | Record a new progress check-in (value, note, date) | | Update Check-In | Update an existing check-in — ETag is fetched and sent automatically | | Delete Check-In | Permanently delete a check-in |

Metric — extra operations

| Operation | Description | |---|---| | List Check-Ins | List all scorecard check-ins for a metric (pagination supported) | | Get Check-In | Retrieve a single check-in by ID | | Create Check-In | Record a new scorecard measurement (value, date, note) | | Update Check-In | Update an existing check-in — ETag is fetched and sent automatically | | Delete Check-In | Permanently delete a check-in |

List options

All Get Many operations support:

• Return All — auto-paginate through all pages.
• Limit — return at most N items (default 50).
• Filters — resource-specific filter fields (e.g. Team ID, Owner ID, Assignee ID, Status, Completed).
• Include — request related resources in a single call (e.g. assignee, team, owner).

Notes

Update and ETag

Strety requires an If-Match: <etag> header on all PATCH (Update) requests. The node handles this automatically: before patching, it issues a GET to fetch the current ETag and injects it. You do not need to supply the ETag yourself.

The same automatic ETag handling applies to Update Check-In on both Goals and Metrics.

Rate limit

Strety enforces a rate limit of approximately 10 requests per 10 seconds. The node includes automatic 429 backoff-and-retry.

Field schemas and write-body wrapping

Todo has fully named input fields (Title, Description, Assignee, Due Date, Priority, Completed At).

For all other resources the node exposes the most common named fields per resource (e.g. Title, Description, Owner, Team, Status, Priority), plus a "Fields (JSON)" input. Use the JSON input to pass additional JSON:API attributes as a plain object — they are merged into the request body automatically. This is the recommended path for any attribute not covered by a named field.

The exact named field list and attribute-level write-body wrapping for non-Todo resources was built from the public Strety endpoint map and will be tightened once validated against a live account.

Using with AI Agents

The node has usableAsTool: true, which means it can be attached to an AI agent node in n8n and driven by natural language.

Example prompts you can give an agent:

• "Create a to-do for Alice due this Friday with title 'Review Q2 report'"
• "List all open issues for the Leadership team"
• "Add a goal check-in for rock ID abc123 with value 80 and note 'on track'"
• "Show this week's scorecard metrics for the Sales team"
• "Move goal xyz789 to the backlog"
• "Create a headline titled 'Server migration complete' and assign it to Bob"

Links

• Repository: github.com/Earney-IT/n8n-nodes-strety
• Strety API help center: help.strety.com
• Report an issue: github.com/Earney-IT/n8n-nodes-strety/issues

License

MIT — Tristen Rice / Earney IT