Analyze event
Submit one event to one configured entity/analysis pipeline, with explicit enablement.
Connector library
FlowStats Event Analysis connector.
Submit a JSON event to a selected FlowStats analysis pipeline and return its verified analysis output.
Connector download
Download FlowStats Event Analysis
Versioned ZIP for your CXFabric tenant.
Use this connector in a flow
- Register the ZIP in your tenant, or add a new version if the connector is already installed.
- Create or select a credential if the action requires one.
- In a Draft flow, add an available action, choose its version, connect it, and map inputs.
- Test the step and flow; review output and failures before activation.
See readme.md in the ZIP for settings and limitations.
- Version
- 0.1.0.0
- Release
- 2026-10-05
- Package
- Implemented source
- Schema credentials
- Basic auth
- Connection settings
- API Base URL, Request Budget (ms)
- Package size
- 7 KB
- SHA-256
bd6b878b99a3bc58ec3901c63e6c0f6bbbd2f519e175d7a12c45fbb7dc2a5ac2- Notes
- Read release notes
Included in this version
Included actions
Implemented in v0.1.0.0. Use a separate flow trigger; no webhook trigger is included.
Vendor API
API and access
Implementation considerations
- Supported scope: Submit a JSON event to a selected FlowStats analysis pipeline and return its verified analysis output.
- Select a Basic Auth credential with the service username/password. Set the trusted HTTPS origin implementing the /eventAnalysis?analysisPipelines=entityId,analysisId contract from the preserved implementation. Confirm that contract with the deployed service owner.
- One event and one pipeline per request. This is a legacy event-analysis contract adapter; it does not claim a current public FlowStats API standard. No bulk ingestion, query language, automatic retry or deduplication guarantee. A disabled action returns an explicit skipped result. Each HTTP action uses a 1–8 second request budget, a 128 KiB request-body limit and a 1 MiB raw JSON response limit. Redirects, automatic paging and automatic retries are disabled. Responses exceeding these bounds fail rather than being truncated. Configure only trusted HTTPS service origins and map connection settings from flow properties.
- New independent connector registration. Existing legacy flows require deliberate action and credential remapping. Hosted import and live service validation remain pending.
Related connectors
More in APIs, Messaging & Protocols
Support
Need help with FlowStats Event Analysis?
Tell us what you need to connect or change.