Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Chat Aid

AI-powered assistant for your knowledge base.

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

Overview

Connect Chat Aid with Flows360

AI-powered assistant for your knowledge base.

Use the Chat Aid 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 4 actions and no declared triggers.

Available actions

  • Add Custom Sources
  • Ask Questions
  • Get Custom Source by ID
  • Custom API Call

Available triggers

  • No triggers are declared in this pinned package.

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: Chat Aid
  • Package: @activepieces/piece-chat-aid@0.2.0
  • Exact artifact digest: sha256:abf5b4c2be579e9ad893e4336a9cfd17bdbf3c59ae2887e2619c4734243ffd90
  • 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

  • Add Custom Sources (addCustomSources), Upload one or more files as custom sources for training Classification: read.
  • Ask Questions (askQuestions), Query your Chat Aid knowledge base and receive AI-generated answers with source citations Classification: read.
  • Get Custom Source by ID (getCustomSourceById), Retrieve single source details by ID Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

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

Capability summary

Authenticationcustom
Supported objects4
Supported actions4
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Chat Aid API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Add Custom Sources Yes No Upload one or more files as custom sources for training
Ask Questions Yes No Query your Chat Aid knowledge base and receive AI-generated answers with source citations
Get Custom Source by ID Yes No Retrieve single source details by ID
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Add Custom Sources · Read

Upload one or more files as custom sources for training

add_custom_sources · Risk: low · Retry: safe

Inputs

  • files · array · Required, One or more files to upload (PDF, Word, Text, Markdown, HTML, Excel, CSV, PowerPoint, PNG, JPEG, GIF)
  • teamId · string · Optional, Optional team ID (defaults to org-wide)
Ask Questions · Read

Query your Chat Aid knowledge base and receive AI-generated answers with source citations

ask_questions · Risk: low · Retry: safe

Inputs

  • prompt · string · Required, The question to ask the knowledge base
  • parentTs · string · Optional, Optional Unix timestamp for conversation threading. Use the same value for related questions in a conversation.
  • messageTs · string · Optional, Optional Unix timestamp of current message. Use with parentTs for follow-up questions in a conversation.
Get Custom Source by ID · Read

Retrieve single source details by ID

get_custom_source_by_id · Risk: low · Retry: safe

Inputs

  • sourceId · string · Required, The ID of the custom source to retrieve
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.

Setup

Setup

  1. Add the Chat Aid 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-chat-aid@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 actions and 0 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 Chat Aid 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-chat-aid@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