Skip to content
← Back to documentation
Technical Reference

PollyBot AI

Automate lead management with PollyBot AI chatbot integration.

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

Overview

Connect PollyBot AI with Flows360

Automate lead management with PollyBot AI chatbot integration.

Use the PollyBot AI 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 5 actions and 1 trigger.

Available actions

  • Create Lead
  • Get Lead
  • Update Lead
  • Delete Lead
  • List Leads

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: PollyBot AI
  • Package: @activepieces/piece-pollybot-ai@0.2.0
  • Exact artifact digest: sha256:8a0bea660e6d1613eb31858b20b19b7fa034815ec8cd9b9725b35e08cf2b22d5
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

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

Action contracts

  • Create Lead (create_lead), Creates a new lead in your PollyBot chatbot. Classification: read.
  • Get Lead (get_Lead), Retrieves a specific lead by ID. Classification: read.
  • Update Lead (update_lead), Updates an existing lead. Supports partial updates. Classification: read.
  • Delete Lead (delete_lead), Permanently deletes a lead from your PollyBot chatbot. Classification: read.
  • List Leads (list_leads), Retrieves a list of leads with optional filtering. Classification: read.

Trigger contracts

  • New Lead, webhook.

Verification

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

Capability summary

Authenticationcustom
Supported objects6
Supported actionsNot published
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • PollyBot API Key Required · protected credential
  • Chatbot ID Required

Supported objects

ObjectReadWriteNotes
Create Lead Yes No Creates a new lead in your PollyBot chatbot.
Get Lead Yes No Retrieves a specific lead by ID.
Update Lead Yes No Updates an existing lead. Supports partial updates.
Delete Lead Yes No Permanently deletes a lead from your PollyBot chatbot.
List Leads Yes No Retrieves a list of leads with optional filtering.
New Lead Yes No webhook trigger declared by the pinned package.

Triggers

New Lead · Webhook

Triggers when a new lead is created in PollyBot AI chatbot.

Inputs

  • chatbotid · string
  • instruction · string

Setup

Setup

  1. Add the PollyBot AI 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:
  • PollyBot API Key (apiKey), required; stored as a sensitive connection value.
  • Chatbot ID (chatbotId), required.
  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-pollybot-ai@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 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 PollyBot AI 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-pollybot-ai@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.