Connector library

Implemented source AI & Language

Wit.ai NLP connector.

Analyze text with the Wit.ai message API and return recognized intents, entities and traits.

Connector download

Download Wit.ai NLP

Versioned ZIP for your CXFabric tenant.

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. 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 Version, Request Budget (ms)
Package size
7 KB
SHA-256
d165db247e8a1d2e4daac7c8b80f014c9d8a54225e1a9e244b22c60303de6660
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.

Analyze text

Read recognized text, intents, entities and traits using the documented message endpoint.

Vendor API

API and access

Implementation considerations
  • Supported scope: Analyze text with the Wit.ai message API and return recognized intents, entities and traits.
  • Select a bearer-token credential containing the Wit.ai server access token. Set the API version date supported by the application explicitly. The connector calls https://api.wit.ai/message.
  • Text NLP only; no conversation/session endpoint, speech upload, training, entity administration or generated chatbot reply. Maximum 280 characters. Text is sent as the documented q query parameter; captured network URLs can contain it. This new connector does not preserve the legacy conversation-response shape. 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.

Support

Need help with Wit.ai NLP?

Tell us what you need to connect or change.