Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Returning AI

Returning AI integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.2.4
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect Returning AI with Flows360

Returning AI integration for Flows360 workflows.

Use the Returning 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 3 actions and no declared triggers.

Available actions

  • Send Channel Message
  • Reply Message
  • React to Message

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: Returning AI
  • Package: @activepieces/piece-returning-ai@0.2.4
  • Exact artifact digest: sha256:670d2cc70883c73bbd16e9e636d28697f4bebfb353b21df5ae2882310be86157
  • 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 Channel Message (sendMessage), Posts a message to a specified channel as a chosen user Classification: read.
  • Reply Message (replyMessage), Reply to a specific message as a chosen user in a channel. Classification: read.
  • React to Message (reactMessage), Add an emoji reaction to a specific message as a chosen user. Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects3
Supported actions3
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Send Channel Message Yes No Posts a message to a specified channel as a chosen user
Reply Message Yes No Reply to a specific message as a chosen user in a channel.
React to Message Yes No Add an emoji reaction to a specific message as a chosen user.

Supported actions

Send Channel Message · Read

Posts a message to a specified channel as a chosen user

send_message · Risk: low · Retry: safe

Inputs

  • description · string · Optional, This action allows you to send messages to any accessible channel as a specific user. The message will appear as if the selected user posted it directly.
  • user · string · Required, The user account that will send the message
  • channel · string · Required, The channel where the message will be posted
  • dynamicFields · object · Required, Additional fields based on channel type
  • message · string · Optional, The message to be posted (optional if images are provided)
  • images · array · Optional, Add one image URL per entry (e.g., https://example.com/image1.png)
Reply Message · Read

Reply to a specific message as a chosen user in a channel.

reply_message · Risk: low · Retry: safe

Inputs

  • description · string · Optional, This action allows you to reply to a message in any accessible channel on behalf of a specific user. The reply will appear as if the selected user posted it directly in response to the original message.
  • user · string · Required, The user account that will send the message
  • messageId · string · Required, The ID of the message to reply to.
  • message · string · Required, The content of the reply to be posted.
React to Message · Read

Add an emoji reaction to a specific message as a chosen user.

react_message · Risk: low · Retry: safe

Inputs

  • description · string · Optional, This action allows you to add an emoji reaction to a message in any accessible channel on behalf of a specific user. The reaction will appear as if the selected user added it directly to the message.
  • user · string · Required, The user account that will add the reaction
  • messageId · string · Required, The ID of the message to react to
  • emoji · string · Required, The emoji to react with (e.g. :sparkling_heart:)

Setup

Setup

  1. Add the Returning 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:
  • 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-returning-ai@0.2.4; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 3 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.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Returning 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-returning-ai@0.2.4 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