Skip to content
← Back to documentation
Technical Reference

SiteSpeakAI

Integrate with Sitespeakai to leverage AI-powered chatbots and enhance user interactions on your website.

CategoryArtificial Intelligence
Authenticationcustom
Version0.1.6
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect SiteSpeakAI with Flows360

Integrate with Sitespeakai to leverage AI-powered chatbots and enhance user interactions on your website.

Use the SiteSpeakAI 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 1 trigger.

Available actions

  • Send Query
  • Create Finetune
  • Delete Finetune

Available triggers

  • New 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: SiteSpeakAI
  • Package: @activepieces/piece-sitespeakai@0.1.6
  • Exact artifact digest: sha256:8d3e007594f902d34f9b82cc5bebe7348bb1e516a9072ff52ba4a6eb428661ba
  • 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 Query (sendQuery), Sends a query to the specified chatbot and retrieves a response. Classification: read.
  • Create Finetune (create_finetune), Adds a new fine-tune (question + suggested answer) for the specified chatbot in SiteSpeakAI. Classification: read.
  • Delete Finetune (delete_finetune), Deletes a fine-tune entry from the selected chatbot. Classification: read.

Trigger contracts

  • New 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 objects4
Supported actions3
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • SiteSpeakAI API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Send Query Yes No Sends a query to the specified chatbot and retrieves a response.
Create Finetune Yes No Adds a new fine-tune (question + suggested answer) for the specified chatbot in SiteSpeakAI.
Delete Finetune Yes No Deletes a fine-tune entry from the selected chatbot.
New Lead Yes No polling trigger declared by the pinned package.

Supported actions

Send Query · Read

Sends a query to the specified chatbot and retrieves a response.

send_query · Risk: low · Retry: safe

Inputs

  • chatbotId · string · Optional, Chat bot ID
  • prompt · string · Required, The question or query text you want the chatbot to answer.
  • conversationId · string · Optional, Pick a conversation for context, or leave empty to start a new one.
  • format · string · Optional, Format of the returned response; markdown or html.
Create Finetune · Read

Adds a new fine-tune (question + suggested answer) for the specified chatbot in SiteSpeakAI.

create_finetune · Risk: low · Retry: safe

Inputs

  • chatbotId · string · Optional, Chat bot ID
  • question · string · Required, The question text you want the chatbot to be able to answer.
  • suggestedAnswer · string · Required, The answer you suggest the chatbot use for that question.
Delete Finetune · Read

Deletes a fine-tune entry from the selected chatbot.

delete_finetune · Risk: low · Retry: safe

Inputs

  • chatbotId · string · Optional, Chat bot ID
  • finetuneId · string · Required, Select the finetune entry to delete.

Triggers

New Lead · Poll

Triggers when a new lead with an email address is created in SiteSpeakAI.

Inputs

  • chatbotId · string

Setup

Setup

  1. Add the SiteSpeakAI 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-sitespeakai@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 3 actions and 1 trigger 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 SiteSpeakAI 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-sitespeakai@0.1.6 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.