Automation and Journey Builder Overview

Overview

OneSuite Automation and Journey Builder help authorized teams turn repeatable customer, marketing, and operational processes into structured workflows. The objective is not to automate everything. The objective is to identify stable, repeatable work, define a clear starting condition, use only released OneSuite actions, and create a journey that staff can understand, test, monitor, and maintain. This guide explains the operating model for Journey Builder, how to plan a journey before building it, how automation relates to CRM and marketing data, and how to verify that a journey is safe before it is used with live customers.

Business Value and Typical Use Cases

Create repeatable follow-up workflows for qualified CRM records.
Move a customer or prospect through a defined marketing sequence using supported production actions.
Standardize routine internal follow-up so staff do not depend entirely on memory.
Build reusable processes for different OneSuite business use cases while keeping ownership and review clear.

Before You Begin

Confirm the user has access to Automation/Journey Builder.
Identify the exact business process to automate and the record type involved.
Verify CRM tags, audience data, campaign data, or other records used by the workflow are accurate.
Decide how the automation will be tested before activation.

Prerequisites and Permissions

Active OneSuite environment with Journey Builder available.
Appropriate user permission.
Accurate source data for the selected trigger.
A defined test record or safe test audience.

Concepts

A journey is a defined automation workflow. It begins from a supported trigger or starting condition and continues through one or more supported actions. The exact triggers and actions available are determined by the installed production release.

Design the business process before opening the builder. Write the desired outcome in plain language, identify the record that enters the journey, decide who owns exceptions, and determine how staff will verify that the journey worked.

Keep journeys intentionally scoped. A narrowly defined automation that is easy to explain and test is safer than a large workflow with many loosely related actions.

How This Feature Fits Into OneSuite

Journeys can connect CRM and marketing workflows by responding to supported triggers and performing the actions available in the current production Journey Builder.

Use task guides and feature documentation together: the feature guide explains the builder, while the task guide explains the business scenario the automation is intended to support.

Screen Orientation

Automation and Journey Builder are used to turn repeatable business processes into controlled workflows. Begin with the business outcome you want, then identify the event or condition that should start the journey and the approved OneSuite actions that should follow.

A journey should be understandable before it is activated. Name it clearly, keep the trigger narrow enough to avoid unintended records, and arrange actions in the order a staff member would expect the business process to happen.

Automation is not a substitute for clean CRM data or clear ownership. Tags, customer identity, campaign information, and other records used by a journey must already be trustworthy for automation results to be trustworthy.

Open the area described in this guide and pause before editing. Identify the page heading, primary action button, search/filter controls, record list or detail panel, status indicators, and any related-record or history areas. This quick orientation prevents users from applying instructions to the wrong record or module.
When the page contains both a list and a record/detail view, use the list for discovery and the detail view for action. Search or filter first, then open the exact record and verify identifying information before making changes.

Role-Specific Guidance

Administrators or authorized marketing/operations users design and activate journeys.
Managers define the business rule, expected outcome, exception handling, and approval requirements before automation is enabled.
Front-line users should understand which actions OneSuite may perform automatically so they can interpret resulting tasks, messages, campaign activity, or record changes correctly.

Step-by-Step Instructions

Open the OneSuite Workspace and open the Journey Builder or Automation area available to your role. Review existing journeys before creating a new one so you do not duplicate an active process.
Choose to create a new journey and give it a business-readable name. The name should describe the outcome or audience, not an internal code that only the creator understands.
Select the supported trigger or starting condition that represents when a record should enter the workflow. Review the trigger carefully because an overly broad trigger can enroll records you did not intend to automate.
Add the supported actions required by the business process. Arrange them in the order the business should experience them and review the configuration for each action before continuing.
Save the journey while it is still being prepared. Reopen it and read the workflow from beginning to end as if you were another administrator reviewing the work.
Test with an approved test record or limited safe audience. Confirm the correct record enters, each supported action occurs in the expected order, and no unrelated customer is affected.
Activate or use the journey only after the test result matches the business process. Document who owns ongoing review and what conditions require the journey to be edited, paused, or retired.

Expected Results

A properly configured journey should have a clear name, a narrow and understandable entry condition, supported actions arranged in the intended order, a successful controlled test, and an identified owner responsible for future review.

Verification Checklist

Confirm the correct OneSuite user is signed in and the expected role/permissions are active.
Confirm the customer, company, invoice, product, message, appointment, employee, or other record shown on screen is the one intended for the task.
After saving or completing the action, refresh or return to the relevant list and verify the new status, history entry, balance, message, appointment, or record appears where expected.

Business Workflow

Define business outcome → identify source record/audience → select supported trigger → configure supported actions → save → test with safe data → verify results → activate → monitor and maintain.

Real-World Business Scenarios

No additional role-specific guidance is required for this topic.

Advanced Operational Guidance

For repeatable business work, standardize naming, ownership, tags/statuses, and staff responsibilities before increasing volume. Consistency makes OneSuite search, reporting, history, and handoffs substantially more useful.
When multiple modules participate in the workflow, verify each handoff. Do not assume that completing one screen automatically proves the customer, payment, communication, or reporting outcome is correct elsewhere.

Screenshots

Production screenshots appear here only after approved OneSuite captures are attached. Written instructions are complete without screenshots.

Best Practices

Build one business outcome per journey where practical.
Use names that another administrator can understand without opening the workflow.
Test every meaningful change before relying on it with live customers.
Review automation whenever CRM structure, tags, campaigns, connected accounts, or related business rules change.

Common Mistakes

Building before defining the business outcome.
Using broad audience or trigger rules without previewing the affected records.
Assuming an automation is correct because it saved successfully.
Leaving old journeys active after the business process has changed.

Troubleshooting

Symptom: the expected record does not enter the journey. Cause: the trigger conditions or source data do not match. Solution: review the record and trigger configuration, then test again with a known matching record. Verification: confirm the test record enters only when the documented condition is true.
Symptom: too many records enter. Cause: the trigger/audience is broader than intended. Solution: pause or stop the workflow if appropriate, narrow the conditions, and retest before live use. Verification: preview the matching population and confirm it reflects the intended business group.
Symptom: an action does not produce the expected result. Cause: required data, permissions, connected service, or action configuration may be incomplete. Solution: review the action and its related feature guide, correct the dependency, and retest. Verification: confirm the action result appears in the expected module or record history.

Frequently Asked Questions

Should every repetitive task be automated?: No. Automate stable, understood processes where the benefit exceeds the complexity of maintaining the workflow.
Can I use actions that are not shown in my Journey Builder?: No. Public documentation should describe only actions available in the released interface.
How should I test a journey?: Use an approved test record or limited test audience and verify every step before broad activation.

Next Steps

Continue with the Related Articles section to follow the workflow into the next OneSuite function instead of returning to the homepage after every task.

Last Updated: August 21, 2026
Version: 0.3.2-Phase2B-SHORTCODE-RENDER-RECOVERY
Verified Public Source Baseline: PASS35H66DN RC1 GOLD R63.97
Documentation Revision: Phase 2B Enterprise Detail Expansion