Trigix Node SDK (Python)
Write a custom Trigix workflow node as a Python function and serve it over HTTP. No changes to the Trigix executor are required — the executor calls your node like any other.
Quick start
pip install trigix-node-sdk
# or from this repo: pip install -e sdk/python
uvicorn examples.greeter:app --port 9000
from trigix_node_sdk import node, create_app
@node(slug="greet", label="Greeter",
config_schema={"type": "object",
"properties": {"name": {"type": "string"}}})
def greet(config, input, node_outputs):
name = config.get("name") or input.get("name", "world")
return {"greeting": f"Hello, {name}!"}
app = create_app()
Then in Trigix → Custom Nodes, register:
- slug:
greet - endpoint:
http://your-host:9000/nodes/greet - config schema: copy from
GET /manifest
Add a Custom node to a workflow, pick greet, and it runs your code.
The contract
The executor POSTs to /nodes/<slug>:
{ "node_id": "n1", "config": { "name": "Ada" },
"input_json": "{\"...\":\"...\"}", "node_outputs": { "prev": "{...}" } }
Your handler def handler(config, input, node_outputs) -> dict receives the
parsed input and returns a JSON-serializable dict. The server wraps it as:
{ "output_json": "{\"greeting\":\"Hello, Ada!\"}" }
Downstream nodes reference your output via {{node_id.field}}.
Discovery
GET /manifest lists every registered node (slug, label, description,
config schema, endpoint) so it can be registered in Trigix in one step.
Security
Custom nodes run in your own process, isolated from the Trigix core. Run the node service on a trusted network; the executor reaches it by URL. (WASM-based in-process isolation for untrusted nodes is a planned future option.)
Metadata
Release files for trigix-node-sdk 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| trigix_node_sdk-0.1.0.tar.gz | 5.2 kB | Without provenance | Details for trigix_node_sdk-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| trigix_node_sdk-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for trigix_node_sdk-0.1.0-py3-none-any.whl |
Total release size: 10.4 kB
Release files / trigix_node_sdk-0.1.0.tar.gz
| Download URL | trigix_node_sdk-0.1.0.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
52904357b09baf0da9af976693831e713ce50a46a4dd775b9c094bfdbe1dc452
|
|
BLAKE2b-256 checksum How to use checksums |
3d1213c84bff5179456082f151a830027115573f3472499afe07931f041b57c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / trigix_node_sdk-0.1.0-py3-none-any.whl
| Download URL | trigix_node_sdk-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
daabd23b09f66442f9ee73df6e21bea970e6a17f39c1c2439acf87a3b8a29d92
|
|
BLAKE2b-256 checksum How to use checksums |
8f7b51b5266ec90650b7b957cf053041e23e06b5540bc2d53154d43cc8a554d7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for trigix-node-sdk 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.