Workflow telemetry SDKs
Capture the work your agents and automations perform in Fluency. Connect existing OpenTelemetry instrumentation, then add business identifiers and outcomes with the SDK's event helpers.
Install
pip install usefluency-workflow-telemetry
npm install @usefluency/workflow-telemetry
Python requires 3.12 or later and imports as fluency_workflow_telemetry. JavaScript and TypeScript require Node.js 24 or later; ESM and CommonJS are supported.
Get started
Your Fluency contact provides your organization's regional endpoint and ingestion key. Configure them in your server-side environment:
FLUENCY_OTLP_TRACES_ENDPOINT=https://YOUR-REGIONAL-ENDPOINT/ext/otel/v1/traces
FLUENCY_WORKFLOW_API_KEY=YOUR-ORGANIZATION-API-KEY
Choose the guide for your application:
- LangChain and LangGraph: connect a Python agent, capture its tools, and attach business context.
- Vercel AI SDK: capture Node.js model calls, tools, and streaming work.
- OpenAI: connect direct Python API calls or Agents SDK workflows while preserving existing tracing.
- RPA and custom workflows: record steps and outcomes from Python or TypeScript automations.
- Existing OpenTelemetry: add Fluency while keeping your current telemetry destination.
- Business context and capture: enrich an operation or record a business action.
After configure(), use telemetry.events for enrich, capture, and timed operations. Framework integrations capture the operations they instrument; the exporter alone does not discover agent or bot activity.
Exact methods and lifecycle behavior are in the SDK reference. Executable examples accompany the guides. Maintainers use release instructions.
This software is proprietary; see LICENSE.
Metadata
Release files for usefluency-workflow-telemetry 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| usefluency_workflow_telemetry-0.1.1.tar.gz | 21.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| usefluency_workflow_telemetry-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 54.6 kB
Release files / usefluency_workflow_telemetry-0.1.1.tar.gz
| Download URL | usefluency_workflow_telemetry-0.1.1.tar.gz |
|---|---|
| Size | 21.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e424608bb3028ca61fa97bacdaac31b84d406321323da0b3fc081f41544888fa
|
|
BLAKE2b-256 checksum How to use checksums |
277b9e57855e91f31fe8c8e0a6c9d7899bdabebf06a7f77bf856307a4b3e4c33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logRelease files / usefluency_workflow_telemetry-0.1.1-py3-none-any.whl
| Download URL | usefluency_workflow_telemetry-0.1.1-py3-none-any.whl |
|---|---|
| Size | 33.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6b6c46a07bfb9b5d8a97317ab5123b19ef3a28fb3cf23cef3f557390b2b344b4
|
|
BLAKE2b-256 checksum How to use checksums |
3ce002a20ea7ee942c9be42993eb8df904bcde75cf4e798070b77e564c62e7ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency log