Automations overview

Spacebrain Automations has two primary tools:

• Workflows react to a trigger and run connected logic such as actions, conditions, delays, and record updates supported by the editor.
• Sequences coordinate an ordered series of touches for enrolled CRM records.

Use a workflow for system orchestration and a sequence for a deliberate contact cadence. A workflow may manage many types of records or actions; a sequence is centered on enrollment and step progression.

Start with an automation contract

Before opening the editor, write down:

• What event or enrollment starts the automation.
• Which records are eligible and explicitly ineligible.
• Required fields and provider connections.
• Actions and branches in execution order.
• The observable success result.
• Idempotency or duplicate-prevention behavior.
• Stop, exit, suppression, and human-handoff conditions.
• Who reviews failures and how quickly.

Build for inspectability

Use descriptive names for automations and nodes. Keep the first version narrow. A builder should be able to explain why a record entered, which branch it followed, what external action occurred, and where the result appears.

Launch progression

1. Validate the draft in the editor.
2. Test with internal records.
3. Inspect executions and downstream systems.
4. Enable for a narrow segment.
5. Monitor at least one complete cycle.
6. Expand only after failure and opt-out behavior are confirmed.

Change control

Before editing a live automation, determine what happens to active runs or enrollments. Duplicate the design or schedule a maintenance window when a change could alter in-flight behavior. Record the reason, effective time, and verification owner.

Continue with workflows and sequences.