griptape-nodes-e2e-wiki

name	griptape-nodes-e2e-wiki
description	Reference wiki for planning Griptape Nodes test workflows. Use when deciding which nodes to create, how to wire them, and which assertion nodes to use to validate outputs — i.e. the planning phase that precedes code generation. Do NOT use for writing pytest code (use the griptape-nodes-e2e-sdk skill for that).
metadata	{"author":"the-foundry-visionmongers","version":"0.1"}

Griptape Nodes E2E Wiki

This wiki is a planning aid. Consult it when you need to answer questions like:

• "My node under test outputs a float — which assertion node validates that?"
• "I need a string comparison with a regex — what parameters does that node take?"
• "What libraries and node types are available for use as inputs or outputs in a test workflow?"

---

How to Navigate

1. Use the Quick Type Lookup table below to jump from a parameter type to relevant assertion nodes.
2. Use the Catalogue to find the reference page for a specific node.
3. Open a reference page (links are relative to this file) to read the full parameter schema, failure behaviour, and wiring guidance.

---

Quick Type Lookup

Start here when you know the output type of the node under test and need to pick an assertion node.

Output type of node under test	Recommended assertion node(s)	Recommended input provider(s)
str	AssertStrings (rich operators), AssertEqual (exact equality)	TextInput
float / int	AssertNumbers	FloatInput / IntegerInput
bool	AssertTrue, AssertEqual	BoolInput
list	GetListLength, GetFromList + type-specific assertion	CreateList
dict	DictGetValueByKey + type-specific assertion	Dictionary
json	JsonExtractValue + type-specific assertion	JsonInput
ImageUrlArtifact	AssertFileExists	CreateColorBars
VideoUrlArtifact	AssertFileExists	LoadVideo (bundled test asset)
AudioUrlArtifact	AssertFileExists	LoadAudio (bundled test assets)
Tool	—	Calculator (simplest; no external deps)
Ruleset	—	Ruleset
any (unknown / mixed)	AssertEqual, AssertTrue	—
file / path	AssertFileExists	—

---

Catalogue

All reference pages are listed below with direct links. There are no intermediate index pages — every link goes straight to the leaf page.

Assertion Nodes — Griptape Nodes Testing Library

Node	Reference page	One-line summary
AssertEqual	assert-equal.md	Assert actual == expected for any type
AssertTrue	assert-true.md	Assert a value is truthy
AssertStrings	assert-strings.md	String comparison with ==, !=, contains, starts_with, ends_with, regex
AssertNumbers	assert-numbers.md	Numeric comparison with ==, !=, <, >, <=, >=
AssertFileExists	assert-file-exists.md	Assert a file exists at a given path

Error Handling — Griptape Nodes Testing Library

Node	Reference page	One-line summary
TryCatchGroup	try-catch-group.md	Catch child node exceptions; route to Succeeded/Failed with error message output

Input Providers — Griptape Nodes Library

Nodes that furnish literal values to the node under test's input parameters.

Node	Reference page	One-line summary
TextInput	text-input.md	Provides a literal str value
FloatInput	float-input.md	Provides a literal float value
IntegerInput	integer-input.md	Provides a literal int value
BoolInput	bool-input.md	Provides a literal bool value
MergeTexts	merge-texts.md	Merge up to 4 text inputs with a separator
JsonInput	json-input.md	Provides a literal json / dict value via property
CreateColorBars	create-color-bars.md	Generates a test pattern ImageUrlArtifact (no external deps)
CreateList	create-list.md	Build a list from expandable item slots
Dictionary	dictionary.md	Build a multi-key dict by zipping key and value lists
KeyValuePair	key-value-pair.md	Build a single-entry dict from editable key + value props
LoadVideo	load-video.md	Loads a VideoUrlArtifact from file path (bundled test asset)
LoadAudio	load-audio.md	Loads an AudioUrlArtifact from file path (bundled test assets)
Calculator	calculator.md	Provides a Tool (calculator; no external deps)
Ruleset	ruleset.md	Creates a Ruleset from name + rules text

Type Converters — Griptape Nodes Library

Nodes that convert the output of the node under test into a type suitable for assertion.

Node	Reference page	One-line summary
ToText	to-text.md	Convert any → str (for AssertStrings)
ToFloat	to-float.md	Convert any → float (for AssertNumbers)
ToInteger	to-integer.md	Convert any → int
ToBool	to-bool.md	Convert any → bool (for AssertTrue)

Control Flow — Griptape Nodes Library

Nodes that branch or sequence execution in a test workflow.

Node	Reference page	One-line summary
IfElse	if-else.md	Branch workflow on a boolean; optionally pass through a selected value
CancelWorkflow	cancel-workflow.md	Crash the flow unconditionally — sentinel for unexpected control paths

Utility — Griptape Nodes Library

Nodes useful as sinks, probes, or helpers in test workflows.

Node	Reference page	One-line summary
LoggerNode	logger-node.md	Log messages; any-type passthrough for debug probes and generic sinks

Output Extractors — Griptape Nodes Library

Nodes that extract a specific value from a complex output (list, dict, JSON) for assertion.

Node	Reference page	One-line summary
GetListLength	get-list-length.md	List → int length (for AssertNumbers)
GetFromList	get-from-list.md	Extract item at index from a list
DictGetValueByKey	dict-get-value-by-key.md	Extract value by key from a dict
JsonExtractValue	json-extract-value.md	Extract nested value via JMESPath expression

Type Compatibility

Page	One-line summary
parameter-compatibility.md	Cross-reference table: parameter types → assertion nodes that accept them

---

Maintenance: Ingest Workflow

When you discover a new node (e.g. via iterative exploration or by reading source code), add it to the wiki:

1. Create a reference page — follow the Page Template below. Save it at references/nodes/<library-slug>/<node-type-kebab>.md.
2. Add a catalogue entry — add a row to the Catalogue table in this file linking directly to the new page.
3. Update the Quick Type Lookup — if the node accepts or produces types not already covered, add or update rows.
4. Update parameter-compatibility.md — add the node as a column and fill in the type rows.

Keep individual reference pages focused. The runtime is authoritative for parameter schema; this wiki is a planning aid, not a contract.

---

Page Template

Use this structure for every new node reference page:

# <NodeType>

**Library:** <Library display name>
**Class:** `<ClassName>`
**Base class:** `<BaseClassName>`
**Category:** <category>
**Display name:** <display name>

## Description

<One paragraph description.>

## Parameters

| Name | Type | Modes | Default | Description |
| ---- | ---- | ----- | ------- | ----------- |
| `name` | `type` | INPUT, PROPERTY | `default` | Tooltip text |

## Failure Behaviour

<What happens when the assertion fails — exception type, flow impact.>

## Use When

<Guidance on which output types and scenarios this node is suited for. Include wiring advice.>

## Example Wiring

<Short prose or table showing which output parameter of which upstream node connects to which
input parameter of this node.>