Chat channel fields and workflow handoff
Chat channel fields and workflow handoff in AI Flowi Workflow use 2 components to update subscriber fields, then trigger a chat channel sub-flow after a successful update. Ai Flowi also provides inbox controls to edit contact fields and switch a conversation between AI and human handling, subject to workspace permissions.
Published · Updated
Product: AI Flowi Workflow by Ai Flowi · Task: Update subscriber fields and trigger a sub-flow · Components: Chat Channel User Fields Setter; Chat Channel Sub-Flow Trigger
When to use this
Use the component pair when a chat channel sub-flow needs subscriber fields updated before it runs. Use the inbox contact panel when an account with permission needs to inspect or change contact fields.
Related: UChat integration for AI Flowi Workflow.
Before you start
- Prepare the Chat Channel Token, Chat Channel User ID and Chat Channel Sub-Flow ID for your configured messaging account.
- Prepare a non-empty top-level array of field objects for JSON Data.
- For inbox edits, use the conversation’s workspace and an account with inbox.reply permission. Reading fields requires inbox.view.
- Configure channels with your messaging provider. The dashboard’s Connect channel control is disabled.
Steps
1. Chat Channel User Fields Setter
Add: Add Chat Channel User Fields Setter to your workflow.
Set: Fill Chat Channel Token and Chat Channel User ID. Supply JSON Data as a top-level array; do not wrap it in a data property.
Example: Use a test field name recognised by your messaging account; the following values are illustrative.
[{"name": "support_topic", "value": "billing"}]Test: Run the setter with a test subscriber and inspect Field Update Status.
Expected: A successful request returns FIELDS_READY. Missing credentials or a request failure returns an error message; invalid JSON Data fails the component build.
2. Chat Channel Sub-Flow Trigger
Add: Add Chat Channel Sub-Flow Trigger.
Set: Fill Chat Channel Token, Chat Channel User ID and Chat Channel Sub-Flow ID for the intended subscriber and sub-flow.
Connect: Connect Field Update Status from the setter to Wait Signal on the trigger.
Test: Run the connected components with your test subscriber and inspect Flow Trigger Status.
Expected: Wait Signal must contain exactly FIELDS_READY. The trigger returns FLOW_SENT after a successful request; any other signal aborts the trigger before it sends the sub-flow.
3. Custom fields
Add: Open a conversation in Conversations and locate Custom fields in the contact panel.
Set: Edit an existing value, or enter New field name and New field value. Select Save fields to submit the changes.
Test: Select Refresh fields to read the subscriber’s fields from the messaging service. Check the refreshed values against the values you intended to save.
Expected: Save fields updates the named subscriber fields and merges the changes into the stored contact fields. Refresh fields replaces the stored fields with the returned field data.
4. Take Over and Return to AI
Set: Select Take Over when the conversation is AI-handled or waiting for a person. A successful takeover pauses the bot and assigns the mapped messaging agent.
Test: Review your reply, then select Send. Human replies are blocked while the conversation is bot-handled.
Expected: Select Return to AI to resume the bot and clear the agent assignment. Check the updated conversation status.
5. ✦ AI Assist and Insert Reply
Add: In a human-handled conversation, open ✦ AI Assist to request a suggested reply. The drawer displays the charged tokens when the response reports a charge.
Set: Select Insert Reply to place the suggestion in the reply box. Review and edit it before selecting Send; inserting a suggestion does not send it to the customer.
Test: Check that the reply box contains the intended text. Regenerate requests another suggestion.
Common mistakes
- Wrapping the JSON Data array inside a data property instead of supplying the array itself.
- Typing a substitute Wait Signal instead of connecting the setter’s Field Update Status.
- Treating FLOW_SENT as proof of the customer’s final reply rather than a successful sub-flow request.
- Expecting Open in Workflow to navigate from the contact panel: the control is disabled and the panel does not show the running workflow or its current step.
- Treating Insert Reply as a sent message.
Troubleshooting
| Message / symptom | Next check |
|---|---|
JSON Data must be a top-level array. | Supply an array directly to JSON Data. |
JSON Data array must not be empty. | Add the field objects you intend to update. |
Trigger Aborted: expected FIELDS_READY | Check Field Update Status and its connection to Wait Signal; the full message includes the received signal. |
Each field needs name and value | Use a non-empty field name and a string value for an inbox edit. |
Chat user_fields response unsupported | Ask the messaging administrator to check the returned field data format. |
Take over before replying | Select Take Over before replying to a bot-handled conversation. |
| Missing editing controls | Check inbox.reply permission; a forbidden action removes the controls. |
| Chat channel request timeout or error | Check the credentials, subscriber and sub-flow identifiers, and messaging service before retrying. |
Related
Ai Flowi documentation · AI Flowi Workflow · Language and display settings · API Hub · Publish a workflow guide · Publishing features · Pricing · Book a demo.