Package Information
Available Nodes
Documentation generating…
Documentation
n8n-nodes-totem-studio
Connect n8n workflows and AI tools to the Totem Studio API.
One Totem Studio node uses one reusable Totem Studio Public API credential.
Install
For self-hosted n8n, open Settings → Community nodes → Install and entern8n-nodes-totem-studio. Your n8n administrator must allow community packages.
This package does not claim a verified n8n Cloud catalog listing.
Use Node.js 24.18 or a newer stable Node 24 release on your n8n host. The
integration is tested against n8n's 2.43 execution/loader contracts.
Connect
- In Totem Studio, open Settings → Developers and create an integration key
with the workspaces and permissions this workflow needs. Your account needs
Totem API access. - In n8n, create a Totem Studio Public API credential and paste the
tsk_live_…
key into API Key. The connection test callsGET /v1/me. - Add Totem Studio, select your resource and operation, and choose an
authorized workspace when the operation requires one.
Select that same saved credential on every node that shares the connection.
Updating its key once updates future executions of all nodes referencing its
credential ID. The key is stored in n8n's credential store, never in workflow
parameters or example files. Revoke the integration in Totem to disable it.
Operations
| Resource | Operations |
|---|---|
| Connection | Validate Connection |
| Team | Get, Get Many |
| Lead | Find by Phone, Find by Email, Get, Get Many, Get Activities, Create or Resolve, Update, Archive, Get Notes, Add Note, Update Note, Delete Note |
| Board | Get Many |
| Call | Get, Get Many |
| Conversation | Get, Get Many |
| Booking | Get, Get Many |
| Member | Get Many |
| Booking Service | Get Many |
| Notification | Get, Get Many |
| Sync | Get Changes |
Phone and email searches retain every match. found means at least one match;ambiguous means more than one. lead is populated only for exactly one match.
Resolve ambiguity before choosing a record for a later action.
Lists and the changes feed return one page with data, has_more andnext_cursor. Apply a page durably before saving its next cursor; use the same
endpoint and workspace when requesting the next page. A resync_required
response means the workflow must start a new synchronization bootstrap.
The node uses the fixed https://api.totemstudio.ai/v1 endpoint. Totem checks
your integration's current workspace access, permissions and revocation on
every request. The public API's documented data boundaries still apply.
CRM writes and notes
Enable the CRM write API profile for an integration that needs writes;
existing read connections remain read-only. All CRM writes require crm:write.
Reading note content requires the separate crm:notes:read permission and an
explicit note-content grant. Adding or editing a note returns metadata only.
The changes feed includes note content only when that grant is present.
Use Fields (JSON) for the documented operation fields. For example, Create
or Resolve with an authorized workspace can import a contact without starting
outreach:
{"origin":"import","email":"alex@example.com","name":"Alex"}
origin is required. Use inbound only for a real, authorized inbound intake;
Totem applies the integration's inbound permission, consent and intake guards.validate_only: true validates an upsert without applying it. Pipeline fields
are named board and stage. Archive requires a documented reason and
retains the lead. Notes use {"body":"Customer requested a callback"};
Delete Note removes the selected note and returns deleted: true.
Update, Archive, Update Note and Delete Note require If-Match.
Copy the current response's etag, including its quotes. A lead validator looks
like "lead_Example:7"; a note validator uses that note's ID and version, such
as "note_Example:2". Refresh and review a stale version before making a new
request. A lead ETag cannot authorize a note change.
The node generates an idempotency key per execution item and retains it across
retries of that item and identical request. The result includes idempotencyKey.
For a deliberate retry from another execution, set Idempotency Key to the
original value and send the identical operation and fields. Keep the original
If-Match on that retry. If the result is outcome_unknown, automatic repeats
stop: reconcile the resource or contact support with that key before taking
another action. Changing keys can duplicate a write.
The integration exposes the documented CRM API operations. It does not send
messages, place calls, create bookings or modify assistant runtime settings.
Example
Import examples/find-lead-by-phone.json from the installed package, select your
own credential, and replace team_REPLACE and the example phone number. The
workflow is inactive and contains no credential values or stored credential IDs.examples/import-lead.json is an inactive import example; connect your own
credential and replace its example workspace and contact before executing it.
Support and license
API documentation: totemstudio.ai/developers.
Support: hello@totemstudio.ai.
MIT. See LICENSE.