Automations
Bounded triggers, conditions, actions, and execution history.
Start here
Build and test an event-driven automation
PulseOne → Dashboard → select your server → Modules → Automations
Publish a response in Message builder if the automation will send a message.
Open Modules → Automations and create a workflow under Automations.
Choose the event in When, then use Conditions (all must match) to restrict it to the intended audience or context.
Under Actions (run in order, up to 5, stop at the first failure), choose approved actions and required roles/templates.
Save the workflow and test one eligible event in a private channel. Inspect the execution history for skipped conditions or failed actions.
Practical example
On a safe test event, send a staff notification only when its conditions match; avoid automatically triggering the same event again.
Before you begin
- Enable first: messages.
- Discord bot permissions for the operational slice: ViewChannel, SendMessages, EmbedLinks, ManageRoles.
- Review staff roles and channel access in your server before using the feature.
Overview of the setup
Before you begin
Publish a response template and identify a supported event or schedule that should trigger it.
Configure
Build a workflow with typed conditions, bounded delays and an allowlisted action; avoid loops involving the same trigger.
Test and verify
Simulate the flow, publish it, then inspect execution checkpoints for a single triggering event before broad rollout.
Features explained
What each feature does and what to check before publishing or installing the result.
Typed triggers and conditions
Triggers and conditions are typed, not arbitrary scripts; verify an actual event matches the chosen predicate.
Allowlisted actions
Actions are from an allowlist such as sending messages and role changes; each needs the relevant bot permissions.
Dry-run and execution history
Review dry-runs and execution history to locate failures, retries and unexpected duplicate triggers.
If it still does not work
- Nothing happened? Verify the When trigger, Conditions, saved state and each action's Discord permissions.
- If some actions ran and others did not, review the first failed action; the workflow stops on that failure.
Troubleshooting and safety checks
- Automation not firing? Check trigger scope, state, filter conditions, the published template and last run outcome.
- If a capability is unavailable in the UI, check the module's current rollout/availability instead of assuming every roadmap item is live.