Build and Publish a Lead360 Automation

How Lead360 helps

Lead360 Automations connects a trigger, conditions, and ordered actions into a versioned workflow. Teams can reduce repetitive work while keeping live sends, record changes, financial effects, and external integrations reviewable through validation, publishing, run logs, and confirmation controls.

When to use this area

Use Automations for repeatable business processes with a clear trigger, deterministic conditions, owned actions, and an observable result.

Before you begin

• Define the trigger and final business outcome.
• Map every input, permission, connector, and possible customer-facing effect.
• Plan a controlled test and rollback or recovery path.

How a workflow works

1. A trigger starts an eligible execution. Conditions and audience rules decide whether it continues. Actions update records, wait, notify, message, or call an approved connector.
2. Draft is editable, Published is the immutable version available to run, and Enabled controls whether new eligible events may start it.

Plan the workflow

1. Define one business goal, trigger, exact sub-account audience, exclusions, deduplication rule, timezone, and owner.
2. Order conditions, waits, internal updates, customer messages, and connector actions so retries cannot repeat an irreversible step.
3. Use the minimum contact data, connector access, and channel permissions required.

Test and publish carefully

1. Validate every branch with safe sample data and verify merge fields, timing, quiet hours, consent, and failure handling.
2. Confirm connector tenants and approvers, then review the full version before publishing or enabling it.
3. Monitor the first Automation Runs. Use Manual Runs only for an intentional selected audience and review past side effects before any replay.

Use Ask360 here

Ask360 can explain existing workflows and runs, help design steps, and prepare a reviewed workflow draft when the operation is supported. It never publishes or enables an automation, enrolls contacts, replays a run, sends a message, or calls an external connector from this Help flow.

Confirm the result

A completed Build and Publish a Lead360 Automation workflow should be visible in the product area that owns the final record. Use these checks before relying on the result or moving to the next customer-facing step.

• Validate and publish the intended version.
• Run a controlled example and inspect Automation Runs.
• Confirm each live effect in its owning product or external provider.

Troubleshooting

The automation never starts

Check enabled status, trigger configuration, filters, event timing, target sub-account, and whether the published version is current.

The same effect happens twice

Inspect duplicate triggers, retries, loops, and idempotency before disabling or restarting the workflow.