Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Chatling

Build AI chatbots trained on your data.

CategoryArtificial Intelligence
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Chatling with Flows360

Build AI chatbots trained on your data.

Use the Chatling connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 3 actions and 2 triggers.

Available actions

  • Send Message
  • Create Chatbot
  • Custom API Call

Available triggers

  • New Conversation
  • New Contact/Lead

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Chatling
  • Package: @activepieces/piece-chatling@0.2.0
  • Exact artifact digest: sha256:984b0df99e4f4b7b2fc7e18e2d47f278aee29b76404d29d7e48c7123b912ea40
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Send Message (send_message), Send a message to the chatbot and receive an AI response. Classification: read.
  • Create Chatbot (create_chatbot), Create a new chatbot using a template or from scratch. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Conversation, polling.
  • New Contact/Lead, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects5
Supported actions3
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Send Message Yes No Send a message to the chatbot and receive an AI response.
Create Chatbot Yes No Create a new chatbot using a template or from scratch.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Conversation Yes No polling trigger declared by the pinned package.
New Contact/Lead Yes No polling trigger declared by the pinned package.

Supported actions

Send Message · Read

Send a message to the chatbot and receive an AI response.

send_message · Risk: low · Retry: safe

Inputs

  • chatbotId · string · Required, Select a chatbot
  • message · string · Required, The message to send to the AI
  • ai_model_id · string · Required, Select the AI model to use
  • conversation_id · string · Optional, Continue an existing conversation
  • contact_id · string · Optional, Associate the conversation with a contact
  • language_id · string · Optional, Select the language for the AI response
  • temperature · number · Optional, Controls randomness (0 = focused, 1 = creative). Default is 0.
  • instructions · array · Optional, Additional instructions to tailor the AI response
Create Chatbot · Read

Create a new chatbot using a template or from scratch.

create_chatbot · Risk: low · Retry: safe

Inputs

  • name · string · Required, The name of the chatbot
  • template_id · string · Optional, Use a template to create the chatbot
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Conversation · Poll

Triggers when a new conversation is started by a customer.

Inputs

  • chatbotId · string
New Contact/Lead · Poll

Triggers when a new contact or lead is collected by the chatbot.

Inputs

  • chatbotId · string

Setup

Setup

  1. Add the Chatling connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-chatling@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 3 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Chatling connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-chatling@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com