Join Tables

Overview

When you send a left table, a right table, and join keys, we combine them with inner, left, right, or full semantics — preserving input order, resolving column name collisions by policy, and capping output before a Cartesian explosion. Keys are compared as-is (no type coercion). Do not use this for fuzzy matching or unbounded cross joins.

Silent cardinality surprises and column collisions break pipelines. You pick the join type and collision policy — we stay predictable.

When to use it

Scope

Non-goals

• Does not coerce key types
• Does not fuzzy-match keys
• Does not produce unbounded Cartesian output
• Does not read files directly

Properties

Capabilities

Cost & billing

Flat rate per invocation

File handling

How we handle your data

Input schema

Output schema

API contract

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"data.join_tables","input":{"leftRows":[{"id":1,"name":"A"}],"rightRows":[{"id":1,"score":9}],"leftKey":["id"],"rightKey":["id"],"joinType":"inner"}}'

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("data.join_tables", {"leftRows":[{"id":1,"name":"A"}],"leftKey":["id"],"rightRows":[{"score":9,"id":1}],"rightKey":["id"],"joinType":"inner"});

Errors

Other limits

Limitations

• Does not coerce key types
• Does not fuzzy-match keys
• Does not produce unbounded Cartesian output
• Does not read files directly
• Fuzzy or approximate key matching
• Streaming joins on unbounded data

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "data.join_tables",
  "input": {
    "leftRows": [
      {
        "id": 1,
        "name": "A"
      }
    ],
    "leftKey": [
      "id"
    ],
    "rightRows": [
      {
        "score": 9,
        "id": 1
      }
    ],
    "rightKey": [
      "id"
    ],
    "joinType": "inner"
  }
}

Examples

{
  "leftRows": [
    {
      "id": 1,
      "name": "A"
    }
  ],
  "leftKey": [
    "id"
  ],
  "rightRows": [
    {
      "score": 9,
      "id": 1
    }
  ],
  "rightKey": [
    "id"
  ],
  "joinType": "inner"
}

{
  "unmatchedLeft": 0,
  "rows": [
    {
      "id": 1,
      "right_id": 1,
      "score": 9,
      "name": "A"
    }
  ],
  "rightRowCount": 1,
  "unmatchedRight": 0,
  "leftRowCount": 1,
  "warnings": [
    {
      "message": "Right columns prefixed with 'right_': [id]",
      "code": "COLUMN_COLLISION"
    }
  ],
  "outputRowCount": 1
}

{
  "leftRows": [
    {
      "id": 1
    },
    {
      "id": 2
    }
  ],
  "leftKey": [
    "id"
  ],
  "rightRows": [
    {
      "score": 9,
      "id": 1
    }
  ],
  "rightKey": [
    "id"
  ],
  "joinType": "left"
}

{
  "unmatchedLeft": 1,
  "rows": [
    {
      "score": 9,
      "id": 1,
      "right_id": 1
    },
    {
      "id": 2
    }
  ],
  "rightRowCount": 1,
  "unmatchedRight": 0,
  "leftRowCount": 2,
  "warnings": [
    {
      "message": "Right columns prefixed with 'right_': [id]",
      "code": "COLUMN_COLLISION"
    }
  ],
  "outputRowCount": 2
}

Recommended use cases

• Combine CSV or API exports by id
• Enrich records with lookup columns
• Left-join facts to a dimension table

Avoid for

• Fuzzy or approximate key matching
• Streaming joins on unbounded data

Related skills

Composable with

Safety & privacy

• Runs without calling any external service.
• Your payloads are never stored permanently.
• Telemetry captures metadata only — never your payload contents.
• We never train models on your payloads.
• No human reviews your payloads.

Tags