Use journeys to describe the interactions you want to observe, then configure the features, rules, and models that inform your decisions.
To build a complete path, start with Build your first decision, then connect the result to an action. For agent traffic, map MCP tool calls into journey steps before adding policy.
A journey defines what to observe and assess. A decision describes the result of that assessment. Your application or an explicitly configured edge action determines what happens to the customer request. Journeys, steps & events explains the terms.
Author a journey
For a website, Record your first journey can discover steps as you browse. Review the generated configuration, then continue in the editor.
Start with Workflow editor & Git workflow, then create a journey and configure its steps.
As your journey grows, review Dependencies & execution order. Use Validate & debug journeys to check the configuration before deployment. The Journey Assistant is another entry point for authoring.
Reuse a Marketplace integration when a step needs bot verification, identity enrichment or a downstream action. Making your own integrations shows how to package calls to your own services.
Build a decision
- Read How decisioning works.
- Follow Build your first decision.
- Add features, rules and signals, and models and scores as needed.
- Review Decision strategy and Apply decisions in your application.
Act on the result
For edge integrations, see Proxy actions and Bot mitigation: Digital Speedbump. Use Labels & feedback to record confirmed outcomes.
When the configuration is ready, continue to Deploy & maintain. Use Investigations to review the resulting events and decisions.