Automations
DealJourney's workflow engine runs on the classic trigger, condition, action model. Every run is logged, so you can debug a misbehaving rule and prove the ones you care about are firing.
On this page
How the workflow engine works
Every rule is a trigger, optional conditions, and one or more actions.
A trigger fires when something happens to a record: a new lead is created, an opportunity changes stage, a subscription approaches renewal. Conditions filter that trigger down to cases that actually matter. Actions are what the automation does in response.
Rules are evaluated in the background with a full execution log. Every run, every success, every failure is recorded so you can debug a rule that isn't behaving and confirm the one you care about is actually firing.
What you can trigger on
The record types and events the engine listens to.
Workflow rules can trigger on leads, opportunities, customers, contacts, subscriptions, and invoices. The event set covers creation, updates, status and stage changes, field changes, Won and Lost, and subscription-specific events like renewal coming up or churn.
Conditions can compare fields to literal values, to other fields on the same record, or to fields on related records, so "opportunity amount greater than £10k AND primary owner is on the enterprise team" is expressible in a single rule.
What actions are available
Send email, update fields, assign users, call a webhook.
Out of the box, rules can send an email using a template, update a field on the triggering record or a related one, create a task or activity, reassign an owner, send an in-app notification to a user, or call an external webhook. Email actions merge the record's data into the template, so output is personalised without manual editing.
SMS is available as a workflow action when Link Mobility is connected at the tenant level.
Scheduled and delayed actions
Automations that run later, not immediately.
An action can fire right away or be scheduled for later. "Send a follow-up email three days after the opportunity is created" is a delayed action. Scheduled actions sit in a queue and execute at their due time. If the underlying record has changed in a way that invalidates the rule, for example the opportunity is already Closed Won, the rule can be configured to skip rather than fire redundantly.
The visual builder
Build rules without writing code, see the whole flow at a glance.
The visual workflow builder is a graph editor: trigger on the left, conditions in the middle, actions on the right, connected by arrows. Most teams build every rule in the visual builder; power users can drop into the raw rule configuration for advanced matching logic.