Union Tables

data.union_tables

ProductionBounded custom (Class B)Deterministicstrictmoderatev1.0.0

No network

Overview

You send two to twenty typed tables. We stack their rows in source order. BY_NAME (default) aligns columns by name and can FILL_NULL or REJECT gaps. STRICT requires the same names in the same order. INTEGER may widen to NUMBER; every other type mix is refused. This is not a join, a dedupe, or a type inference pass.

Appending extracts with silent column reordering or STRING-to-NUMBER coercion is how a ledger stops reconciling. Alignment and promotion stay named.

Reliability

Rows stay in source-table then source-row order. Empty sources contribute schema only. DUPLICATE_COLUMN — trigger: a source table repeats a column name; retryable: no; next: rename the duplicate. SHAPE_INVALID — trigger: a source row is not rectangular; retryable: no; next: fix that row. TYPE_MISMATCH — trigger: a cell does not match its declared type; retryable: no; next: fix the cell. ITEM_LIMIT_EXCEEDED — trigger: the stacked table would exceed 1,000,000 cells; retryable: no; next: union fewer tables. UNION_INCOMPATIBLE — trigger: STRICT order differs, BY_NAME REJECT sees a gap or extra, or types cannot promote; retryable: no; next: choose FILL_NULL or align the schemas.

Context footprint

Stacked rows plus sourceRowCounts. A successful call costs 2 execution credits.

When to use it

When two to twenty already-typed extracts should be stacked, with INTEGER widening to NUMBER and nothing else coerced.

When rows must be matched by key, or when types still need to be inferred from text.

Scope

Note

Stacks 2 to 20 rectangular tables in source order, with STRICT or BY_NAME alignment.

Non-goals

Does not join or match keys
Does not drop duplicate rows
Does not infer types from strings

Properties

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

data-transformation

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call2 credits

File handling

Accepts file_refProduces file_refMax input2 MB

How we handle your data

Sensitive output possible

What this means

This skill may receive sensitive content and may return submitted, transformed, extracted, or reformatted content.

Squillify guarantees

Runs inside Squillify
This skill runs inside Squillify.
Payloads are not sent to an external service by this skill.
Squillify does not permanently store submitted payloads.
Telemetry records metadata only, not submitted content.
Submitted payloads are not used for training.
Submitted payloads are not reviewed by humans.
This skill does not target sensitive data.
The response may contain submitted or transformed content.

Your responsibility

Squillify does not determine whether submitted content is sensitive. Your application is responsible for deciding what data it is allowed to submit. Your application is responsible for securing the response.

Read the Microskill Data Handling Policy

Input schema

Field	Type	Required	Description
tables	array	Yes	From 2 through 20 closed rectangular tables stacked in input order, sharing the 1,000,000-cell ceiling.
columnMode	string	No	STRICT keeps names and order; BY_NAME aligns by name. Omit it for BY_NAME.
missingColumnPolicy	string	No	REJECT fails on gaps; FILL_NULL pads nulls. Omit it for REJECT.

Output schema

Field	Type	Required	Description
columns	array	Yes	Union schema after INTEGER-to-NUMBER promotion, 0 through 256 unique NFC names.
rows	array	Yes	From 0 through 50,000 stacked rows in source-table then source-row order.
columnCount	integer	Yes	Non-negative count for this result.
rowCount	integer	Yes	Non-negative count for this result.
sourceRowCounts	array	Yes	One count per input table, length 2 through 20, in input order.
columnMode	string	Yes	Alignment actually applied.
missingColumnPolicy	string	Yes	Missing-column policy actually applied.

API contract

POST /v1/execute

curl

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"data.union_tables","input":{"tables":[{"columns":[{"name":"id","type":"STRING"}],"rows":[["a"]]},{"columns":[{"name":"id","type":"STRING"}],"rows":[["b"]]}]}}'

Integrations

TypeScript SDK

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

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

const { output } = await sq.execute("data.union_tables", {"tables":[{"rows":[["a",1]],"columns":[{"type":"STRING","name":"id"},{"type":"INTEGER","name":"n"}]},{"rows":[[2.5,"b"]],"columns":[{"type":"NUMBER","name":"n"},{"type":"STRING","name":"id"}]}]});

Errors

Code	HTTP	Retryable	Description
VALIDATION_ERROR	400	No	The request payload failed schema validation.
UNAUTHORIZED	401	No	Missing or invalid API key.
SKILL_NOT_ACCESSIBLE	403	No	The API key is not granted access to this skill.
SKILL_NOT_AVAILABLE_FOR_PLAN	403	No	This skill is not included in your current plan.
PLAN_ELIGIBILITY_UNAVAILABLE	503	Yes	Plan eligibility could not be decided. Retry after backoff.
SKILL_NOT_FOUND	404	No	The requested skill or version does not exist.
TENANT_RATE_LIMITED	429	Yes	Request rate limit exceeded. Retry after backoff.
QUOTA_EXCEEDED	429	Yes	Plan quota exhausted. Retryable once the quota period resets.
EXECUTION_TIMEOUT	504	Yes	Execution exceeded the allowed time budget.
DUPLICATE_COLUMN	400	No	The request payload failed this skill's input validation.
SHAPE_INVALID	400	No	The request payload failed this skill's input validation.
TYPE_MISMATCH	400	No	The request payload failed this skill's input validation.
ITEM_LIMIT_EXCEEDED	429	No	A size, quota, rate, or time limit was exceeded.
UNION_INCOMPATIBLE	400	No	The request payload failed this skill's input validation.

Other limits

Limit	Value
Recommended inline bytes	32 KiB

Limitations

Does not join or match keys
Does not drop duplicate rows
Does not infer types from strings
Matching rows by key (use a join)
Guessing types from text

How to call

POST /v1/execute (requires authentication)

Request bodyjson

{
  "skillKey": "data.union_tables",
  "input": {
    "tables": [
      {
        "rows": [
          [
            "a",
            1
          ]
        ],
        "columns": [
          {
            "type": "STRING",
            "name": "id"
          },
          {
            "type": "INTEGER",
            "name": "n"
          }
        ]
      },
      {
        "rows": [
          [
            2.5,
            "b"
          ]
        ],
        "columns": [
          {
            "type": "NUMBER",
            "name": "n"
          },
          {
            "type": "STRING",
            "name": "id"
          }
        ]
      }
    ]
  }
}

Examples

By name reorders and widens integer

Inputjson

{
  "tables": [
    {
      "rows": [
        [
          "a",
          1
        ]
      ],
      "columns": [
        {
          "type": "STRING",
          "name": "id"
        },
        {
          "type": "INTEGER",
          "name": "n"
        }
      ]
    },
    {
      "rows": [
        [
          2.5,
          "b"
        ]
      ],
      "columns": [
        {
          "type": "NUMBER",
          "name": "n"
        },
        {
          "type": "STRING",
          "name": "id"
        }
      ]
    }
  ]
}

Expected outputjson

{
  "columnCount": 2,
  "missingColumnPolicy": "REJECT",
  "rows": [
    [
      "a",
      1
    ],
    [
      "b",
      2.5
    ]
  ],
  "columns": [
    {
      "type": "STRING",
      "name": "id"
    },
    {
      "type": "NUMBER",
      "name": "n"
    }
  ],
  "sourceRowCounts": [
    1,
    1
  ],
  "rowCount": 2,
  "columnMode": "BY_NAME"
}

Tip

BY_NAME keeps first-seen order and widens INTEGER to NUMBER

Fill null keeps an extra column