Everyone
Follow one lead from public form to audited outcome
Throughout this manual we use Northstar Services, a fictional company. Avery Morgan submits a request using the public “Automation Consultation” form. The form creates a lead. A workflow checks the budget and service type, asks a manager to approve higher-value work, creates a discovery task, notifies the assigned owner, and sends a signed event to a reporting system.
Before you start
- Read the overview.
- No live provider accounts are needed.
#Use safe, recognizable example data
- Visitor
- Avery Morgan,
avery.morgan@example.test. - Form
- Automation Consultation.
- Qualification rule
- Requested service is Automation and estimated budget is at least $5,000.
- Approval
- The Sales Manager confirms that a discovery call should be scheduled.
- Outcome
- Create an assigned task, notify its owner, and emit
lead.qualified.
#See what each module contributes
- Capture: validates the public form and stores the accepted submission safely.
- CRM-lite: creates the lead, owner, stage, score, and activity timeline.
- Workflow engine: evaluates facts and records the selected path.
- Approval inbox: pauses a guarded action until a named person decides.
- Operations and notifications: create visible work and tell the right person.
- Developer webhooks: sign the outbound event and record delivery attempts.
- Execution history: provides one place to explain the complete result.
#Reuse this story while reading
Each chapter revisits only the part relevant to that screen. Keep the names and values consistent in a demo workspace so screenshots, logs, and explanations line up. When adapting the example, change the business terms but retain the safety pattern: validate the boundary, make rules explicit, require approval for risk, create an observable outcome, and retain evidence.
#Common mistakes
- Using real customer data in a demonstration.
- Assuming a notification proves the external action succeeded.
- Skipping approval because the example looks harmless.
#Verify the result
- I can name the trigger, rule, approval, action, and evidence.
- All example identities use example.test.
- I understand where the process pauses and resumes.