Workflow Builder: Learn More Using AI

What is Learn More Using AI?

Key Benefits of Learn More Using AI

Learn More Button

Workflow AI Assistant Sidebar

Learn Mode 2.0 Learn Mode streams answers in real time and suggests follow-up questions at the end of each response. Continue in Build Mode When you ask a build question in Learn Mode, you can switch to Build Mode using the Continue in Build Mode button. This keeps your request and submits it in Build Mode without retyping.

How To Use Learn More Using AI in Workflows

Access Workflow Builder

From the left-hand menu, click Automation, then select the Workflows tab. Click + Create Workflow in the top-right to start building from a recipe, template, or scratch.

Open a Trigger or Action

To activate the Learn More feature, click into any trigger or action configuration panel. In this example, we’re starting by selecting + Add New Trigger.

Select a Trigger Type

After opening the configuration panel, choose a trigger from the list. In this example, we’re selecting Contact Tag, but any standard trigger or action will display the Learn More button.

Click the Learn More Button

In the upper-right corner of the configuration panel, click the blue Learn More button with the lightbulb icon. This launches the Workflow AI Assistant with contextual guidance.

View Contextual Guidance

After clicking the Learn More button, the Workflow AI Assistant sidebar opens on the left. This panel gives you detailed, contextual information based on the exact trigger or action you’re configuring.

You’ll see explanations of what the feature does, how it works, step-by-step configuration guidance, and real-world use cases. You can also type follow-up questions directly into the chat box to get personalized answers — making it easy to troubleshoot, learn, and configure workflows correctly without leaving the page.

Frequently Asked Questions

Before you begin

“Workflow Builder: Learn More Using AI” is part of the Automation → Workflows area in Adaptive AI. Create and manage active, inactive, and draft workflows. Automation changes can affect many records at once, so the safest approach is to define the intended entry condition, action, and stopping point before publishing anything. The objective is not merely to save a setting; it is to confirm the result works for the staff member or customer who will depend on it.

• Write down the exact trigger, filters, expected action, and condition that should stop or bypass the automation.
• Use an internal test contact with complete sample data, a valid communication channel, and consent appropriate to the test.
• Confirm that every connected account, custom field, pipeline, calendar, or template referenced by the automation still exists and is available.
• Record the current published status and settings so you can compare behavior or restore the earlier configuration if necessary.
• Choose a quiet test window when a controlled enrollment cannot interfere with active customer communication.

Verify the result

After completing the instructions in this guide, use a controlled test before treating the setup as finished. A saved screen or success message confirms configuration, but only an end-to-end test confirms the business outcome.

1. 1Save the configuration, review every branch from top to bottom, and publish only after required fields and warnings are resolved.
2. 2Run one controlled test using known inputs and note the exact time the test record entered the automation.
3. 3Open execution history and confirm that the record followed the expected branch in the correct order.
4. 4Verify the intended message, task, field update, or status change occurred once and contains the correct merged information.
5. 5Run a negative test that should not qualify; it should remain outside the automation without producing side effects.

Troubleshooting checklist

If the result differs from what you expected, preserve the current state and isolate one variable at a time. Start with the checks below before deleting the configuration or rebuilding it from scratch.

• Confirm the automation is published and that the trigger filters match the test record exactly, including capitalization and date conditions.
• Review re-entry settings to determine whether the same record is allowed to enter again or is being correctly excluded.
• Check the first failed or skipped step in execution history instead of changing several steps at the same time.
• Verify wait steps, account time zone, business-hour windows, and scheduled-send rules when an action appears delayed.
• Reconnect or reauthorize any external service that reports an expired credential, missing scope, or unavailable resource.

Best practices

• Use names that state the audience, trigger, and outcome so another administrator can understand the automation without opening it.
• Keep entry filters narrow and add explicit stop conditions to prevent duplicate messages, tasks, or opportunity changes.
• Respect contact consent, do-not-disturb status, quiet hours, and channel-specific opt-out requirements in every communication path.
• Change one behavior at a time, test it, and document the result before expanding the automation to more records.
• Review execution errors and unexpected enrollments after launch, then again after any connected integration or template changes.