suppa-v2

n8n community node package for Suppa 2.0

Package Information

Released: this month
Downloads: 0 weekly / 0 monthly
Latest Version: 0.1.1
Author: Mykola Demchuk

Documentation

n8n-nodes-suppa-v2

n8n community nodes for the Suppa 2.0 platform.

For Suppa 1.0 (API-key auth) use n8n-nodes-suppa.

Installation

In n8n: Settings → Community Nodes → Install and enter n8n-nodes-suppa-v2.

See the community nodes installation guide for other options.

Nodes

Node What it does
SUPPA 2.0 Create, get by ID, get by filter, update by ID and delete by ID records of any Suppa table
SUPPA 2.0 Event Trigger Starts a workflow when a record is created, updated or deleted (webhook subscription managed automatically)

Credentials

Create a Suppa V2 API credential:

Field Description
Base URL Suppa instance API
Username / Password Account the nodes sign in with (POST /auth/accounts/login)
Webhook Secret Key Optional. When set, incoming trigger webhooks must carry a valid HMAC-SHA256 signature

The nodes sign in once, keep the access token in memory until it expires, and sign in again automatically when the API answers 401.

A Suppa account can belong to several tenants, and a password sign-in lands in the account's current tenant whatever host it was sent to. When that is not the tenant of the Base URL, the nodes switch the session to the Base URL's tenant (the same hand-off the tenant switcher in the web app uses). The account must be a member of that tenant; otherwise the node reports which tenants the account can reach.

Migrating from n8n-nodes-suppa ≤ 0.1.10

Up to version 0.1.10 these nodes shipped inside n8n-nodes-suppa. Starting with n8n-nodes-suppa 0.2.0 they live only here.

  1. Update n8n-nodes-suppa to 0.2.0 or later (or uninstall it if you only use Suppa 2.0). Both packages cannot provide the Suppa V2 API credential at the same time.

  2. Install n8n-nodes-suppa-v2.

  3. Existing workflows reference the nodes by their old type and show them as unknown. Fix each workflow in one of two ways:

    • delete the node and add it again from the node panel, or

    • download the workflow as JSON, replace the node types and import it back:

      Old type New type
      n8n-nodes-suppa.suppaV2 n8n-nodes-suppa-v2.suppaV2
      n8n-nodes-suppa.suppaV2Trigger n8n-nodes-suppa-v2.suppaV2Trigger
  4. Deactivate and activate workflows with the trigger node so the webhook subscription is registered again.

Saved Suppa V2 API credentials keep working — the credential type name did not change.

Compatibility

Requires Node.js 20.15 or later. Built against n8n-workflow 1.82.

License

MIT

Discussion