Skip to CRM content
121 CRM

121 CRM feature · Workflow triggers

Make the beginning of every workflow explainable.

Start automation from a clear, testable event and protect against duplicates, loops and accidental entry. The capability is described from official product evidence; its availability, configuration and any usage charges for a particular 121 account still need to be confirmed before reliance.

Subscribe to 121 CRMSeller, billing and cancellationExplore all CRM features

Fictional product demonstration

See workflow triggers in the context of real customer work.

This coded interface uses realistic fictional data to explain the operating pattern; it is not a screenshot of a live customer account.

121

Northstar Joinery

Follow up consistently, with people in control

AR
OverviewContactsInboxPipelineAutomation

Follow up consistently, with people in control

Build the sequence, review each decision and test an exception before activation.

Draft v0.4

This example stays on this page and does not send messages or change CRM data.

Illustrative 121 interfaceAll people, organisations, dates and activity are fictional. Any figures are illustrative. Controls demonstrate interaction patterns, not enabled account features.

How it helps

See how the feature supports the work.

Each part has a clear job. It becomes useful when it fits the way customers already move through the business and your team knows when to step in.

Capability 01

Triggers

Starts a workflow after configured contact, event, appointment, opportunity, course or other supported activity.

How it works
Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it
Lets follow-up begin from a business event instead of waiting for someone to remember.
Plan for
Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service.
Your team owns
A process owner must approve, test, monitor and pause or correct faulty automation.
Capability 02

Actions

Performs supported steps such as sending a message, updating a record, assigning work or calling a connected service.

How it works
Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it
Coordinates routine execution across the customer journey.
Plan for
Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service.
Your team owns
A process owner must approve, test, monitor and pause or correct faulty automation.
Capability 03

Testing and execution logs

Supports test runs and operational evidence used to diagnose why a record did or did not follow a path.

How it works
Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it
Gives a human a way to verify automation and investigate exceptions.
Plan for
Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service.
Your team owns
A process owner must approve, test, monitor and pause or correct faulty automation.
Capability 04

Contacts

Stores a person or lead with contact details, activity, ownership and related records.

How it works
Stores or organises supported business data under configured fields, permissions and record rules.
Why use it
Gives a team one place to understand who a customer is and what has happened.
Plan for
The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns
A data owner must define the record model and resolve quality, ownership and access exceptions.

Use it with purpose

What good workflow triggers looks like

A fictional consultancy starts an acknowledgement only after a valid enquiry form is submitted, not whenever an existing contact is edited. The useful outcome is a record that another person can understand and continue, not simply another automated event.

Name the exact event

Describe what must happen and which record or channel supplies the event.

Add eligibility rules

Exclude tests, duplicates and records that lack consent or required context.

Make entry visible

Record enough detail for a person to understand why the workflow started.

Configuration decisions

Decide the operating rules before switching workflow triggers on

A credible setup begins with ownership, eligibility and exception decisions. Those choices should be written in plain English and tested with realistic fictional data.

Choose one primary trigger

Avoid several overlapping entry events unless their interaction is deliberately tested.

Set re-entry behaviour

Decide whether the same record may enter again and after what change or interval.

Human review point

Plan a safe test

Use fictional or test records across expected and unexpected scenarios before activation.

From configuration to daily use

Keep the rule, the owner and the exception visible

The second view shows how the capability connects to work a person can review and continue.

121 CRM · Connected operations

Book discovery

October · illustrative availability

MTWTFSS1234567891011121314
11:3014:00

Appointment sequence

Booked

Calendar entry created

1 day before

Reminder scheduled

Exception

Owner reviews a reply

Journey summary

New

24

Illustrative

Owned

21

Illustrative

Due

4

Illustrative

Website
Referral
Direct
Illustrative exampleAll dates, counts and workflow states are fictional. Availability and behaviour depend on the agreed setup.

Practical example

Follow one example from signal to next action

A fictional consultancy starts an acknowledgement only after a valid enquiry form is submitted, not whenever an existing contact is edited. The example shows the role of the CRM while keeping the consequential decision with a person.

Form submitted

A valid fictional enquiry is received.

Eligibility checked

Consent, service area and test flags are evaluated.

Human judgement

Workflow starts

The reason and timestamp are recorded.

Owner alerted

An exception is sent to a person if required data is missing.

Boundaries and checks

Plan for the limits of workflow triggers

Product capability is only one part of a dependable process. Data quality, provider configuration, consent, permissions and staff cover still matter.

Data and context

Events can fire more than once or arrive out of order.

Account and provider setup

A trigger does not prove the underlying data is accurate.

Keep a person accountable

Human responsibility

Connected systems and premium actions may have separate availability or charges.

Questions about this page

Useful answers, without the sales fog.

1. Is workflow triggers confirmed as included in every 121 CRM account?

No. The underlying capability is evidenced in official product documentation, but 121 plan entitlement, sub-account configuration, connected providers and usage charges have not been assumed. Confirm the intended setup before relying on it.

2. What should we decide before configuring workflow triggers?

Start with three decisions: choose one primary trigger, set re-entry behaviour, plan a safe test. Then test ordinary, missing-data and exception cases with fictional records.

3. What is a practical way to measure whether workflow triggers is helping?

Measure whether the intended customer work becomes visible and owned. For this page, review name the exact event, add eligibility rules, make entry visible rather than treating clicks, sends or record counts as proof of business value.

4. Can workflow triggers be fully automated?

No. Connected systems and premium actions may have separate availability or charges. Automation can coordinate repeatable steps, while people remain responsible for judgement, exceptions, consent and correcting the record.

Read all CRM questions

Continue the journey

AutomationWorkflow conditionsWorkflow exception handling

Delegate the work. Keep the human.

Ready to organise the customer journey?

Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.

Subscribe to 121 CRMSeller, billing and cancellationCompare pricing

121 CRM

Your customers. Your conversations. Your business. Organised around clear ownership and human decisions.