module / Automation

Limited / in development

Follow-up starts
with a clear boundary.

Repeated follow-up should be explicit about what starts work and what it is allowed to create.

AUTOMATION / BOUNDED FOLLOW-UP
01 / Event

Deal created

Context
Organization + user
Record
Deal + stage
Trace
Request identity
02 / Configuration

An explicit boundary

Enabled module and configured edge

→
03 / Permitted reactions

Create a task

Title, description and date

Create an invoice

Contact and catalog line items

Task or invoice follow-up starts with a specific event and explicit configuration. General triggers, approval flows and a workflow designer remain in development; customer availability is unconfirmed.

01 / BOUNDED FOLLOW-THROUGH

One event. Explicit reactions.

Existing source contains bounded deal-created hooks for task or invoice creation. A configured hook is not a general automation engine, and the current scaffold does not establish an active customer workflow.

Teams exploring carefully bounded operational follow-through.

01

Start with the event

Define the qualifying deal-created event and the permitted downstream operation.

02

Choose the permitted work

A configured hook can target task creation or invoice creation within that bounded contract.

03

Keep the limit visible

Broader triggers, approval flows, and general workflow design remain development work.

Configuration before execution

The intended bounded workflow starts with a configured deal-created event and a permitted task or invoice operation. Configuration and availability require separate evidence.

02 / CONNECTIONS

Follow the work across its boundary.

Automation is intentionally limited to explicit deal-created hooks rather than a general-purpose workflow engine.

The current implementation is limited to these two reactions. Customer configuration and availability still need confirmation; the illustration does not represent a completed execution.

Pricing relationship

Automation is in the current base pricing catalog. Its limited development status does not establish customer availability; use the composer to review current options and rates.