tellzm

n8n community nodes for orchestrating the Tellzm platform (tasks, projects, forms, processes, pages, data tables, calendar, routines, …) via OAuth.

Package Information

Released: 4 mo ago
Downloads: 16 weekly / 1,205 monthly
Latest Version: 0.3.2
Author: Tellzm

Available Nodes

Tellzm
Read, create, update, and act on Tellzm entities.
Tellzm Trigger
Fire workflows on Tellzm events (tasks, forms, processes, …).

Documentation

n8n-nodes-tellzm

n8n community nodes for orchestrating Tellzm.

Exposes Tasks, Projects, Forms, Form-Processes, Pages, Data Tables, Calendar, and Routines as first-class n8n actions, plus a polyglot trigger node that fires workflows on platform events.

Install

In your n8n custom-nodes directory (default ~/.n8n/custom/):

cd ~/.n8n/custom
npm install n8n-nodes-tellzm

Restart n8n. You should see Tellzm and Tellzm Trigger in the node search palette.

Connect

  1. In the n8n editor, drop a Tellzm or Tellzm Trigger node onto the canvas.
  2. Click the Credentials dropdown → Create New → Tellzm OAuth2 API.
  3. Optionally trim the Scope field to limit what this credential can do.
  4. Click Sign in with OAuth2 — you'll be redirected to tellzm.com/oauth/authorize.
  5. On the consent screen:
    • Tick the workspaces this credential should be able to reach (multi-select — pick one, several, or all).
    • Optionally enable Auto-include workspaces I create later to grant access to future workspaces by default.
    • Approve the scopes.
  6. You'll be sent back to n8n with a working credential. Click Test Connection to confirm.

On each Tellzm node you can then pick the target Workspace from a dropdown
populated dynamically from your authorized list. The Trigger node listens on
the workspace it's bound to via the credential default.

No CLI, no manual OAuth client registration — the package ships with a shared client_id and the platform accepts any n8n install's /rest/oauth2-credential/callback URL.

What's included

Actions (resource × operation):

  • Task — get / list / search / create / update / delete / complete
  • Project — get / list / create / update / delete
  • Form — get / list / listSubmissions / submit / deleteSubmission
  • Form-Process — listTemplates / getTemplate / listInstances / getInstance / trigger / fireAction / transition / cloneTemplate / archiveTemplate
  • Page — get / list / search / create / update / delete / appendBlocks
  • Data Table — listTables / getTable / listRecords / getRecord / createRecord / updateRecord / upsertRecord / deleteRecord / bulkRecords
  • Calendar — listSubCalendars / getEvent / listEvents / queryRange / createEvent / updateEvent / deleteEvent
  • Routine — get / list / listRuns / submitTaskValue / updateRoutineTask
  • Raw API — escape hatch for any endpoint the wrapper doesn't surface

Triggers (Tellzm Trigger node):

  • task.created / .updated / .completed / .deleted
  • project.created
  • form.submitted
  • page.published
  • record.upserted
  • calendar.event.created
  • comment.added

Each trigger accepts an optional filter tree (AND/OR with comparison operators) so you can subscribe narrowly.

Documentation

Full docs: https://tellzm.com/docs/n8n

No client secret

This package uses OAuth 2.0 with PKCE (a "public client") — there is no
client secret. In the n8n credential form, leave the Client Secret field
blank (or enter any throwaway value if your n8n version refuses an empty
string — the value is never sent during the flow).

Filter tree syntax (Trigger node)

// Single condition
{ "field": "status", "op": "eq", "value": "done" }

// AND group
{ "combinator": "AND", "conditions": [
  { "field": "priority", "op": "in", "value": ["urgent", "high"] },
  { "field": "assignee.id", "op": "eq", "value": "{{$json.userId}}" }
]}

// Operators: eq, neq, in, nin, lt, lte, gt, gte, contains, exists

License

MIT.

Discussion