TellzmInstall

Summary

Upserts a record in a Tellzm data table by calling the upsert_base_record MCP tool with the table ID and record values. Requires the base.write scope on the credential.

Inputs

• Workspace Name or ID — Workspace to target, chosen from the credential's authorized workspaces. Sent as the X-Tellzm-Workspace-Slug header.
• Table ID (required) — ID of the data table to upsert into.
• Record Values (JSON) (required) — JSON object mapping field keys to values. Sent as values.
• Upsert Key Field (required) — Field name used to find the existing record, which should be unique. The UI requires it, but the source reads a parameter named keyField instead of upsertKeyField. The value entered here is therefore never sent, and the server decides which field to match on. The listed 'upsert by primary field' action suggests it may fall back to the primary field.

Output shape

One output item per input item. Its json is the response from the upsert_base_record tool, parsed from JSON. The tool's response fields aren't visible in the source.

No idempotency key is sent for this operation. It fails before any API call if the credential lacks base.write. API and MCP errors are raised as node errors, and 429/503 responses are retried once.

Examples

Example 1: Sync a customer row by email into a CRM table, creating it or updating it.

Table ID = your table's ID; Record Values = {"email":"{{$json.email}}","name":"{{$json.name}}"}; Upsert Key Field = email. Note that the key field is currently not forwarded to the API.

Links

• n8n community nodes installation guide