Start journey session
Start one virtual-agent session and return its state ID.
Connector library
CLEVVA Journeys connector.
Start a CLEVVA journey session, retrieve its prompt and submit a user answer through the legacy journey API contract.
Connector download
Download CLEVVA Journeys
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
- Bearer token
- Connection settings
- API Base URL, Request Budget (ms)
- Package size
- 34 KB
- SHA-256
1a0018321eba7a3f745f683ae7dcc9ebace2cd8d9b7601b35b177f73450bbebf- 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.
Get journey prompt
Read the current state and return prompt/end status with action references.
Submit journey answer
Submit one chat answer for a selected state/action reference.
Vendor API
API and access
Implementation considerations
- Supported scope: Start a CLEVVA journey session, retrieve its prompt and submit a user answer through the legacy journey API contract.
- Select a bearer-token credential containing the deployment API key; it is sent in the apikey header. Set the trusted HTTPS service origin. This adapter implements the /clevva/app/api/journey contract found in the preserved source implementation. Confirm that your deployment exposes that contract before running it.
- Legacy contract adapter, not a claim of compatibility with every CLEVVA release. It supports start, state retrieval and chat input only. Session writes are not automatically retried. No admin APIs, bot training, automatic conversation loop or hidden session persistence. 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 AI & Language
Support
Need help with CLEVVA Journeys?
Tell us what you need to connect or change.