Automations

An automation is a small rule with three parts: a trigger (when it runs), optional conditions (checks that must pass), and one or more actions (what Flantic does). For example: when a message is sent in #showcase, create a discussion thread on it. Or: when someone reacts with a pin emoji, pin the message.

• Message Created, Edited, or Deleted: watch activity in text channels.
• Reaction Added: run when a member reacts to a message, optionally only for specific emojis.
• Member Joined or Left: welcome flows, raid gates, and exit follow-ups.
• Role Added or Removed: react when a member gains or loses a role.
• Voice Channel Joined or Left: respond to voice activity.

Each trigger offers only the conditions and actions that make sense for it. A reaction trigger can check which emoji was used and which channel it happened in; a join trigger can check the account's age, which makes a simple raid gate possible.

Conditions gate the run. Combine them with All (every check must pass) or Any (one passing check is enough). Message triggers can check content (contains, equals, starts or ends with, regex, links, attachments, mentions, length), the channel or category, the author's roles, and the author's account age. Time-of-day and day-of-week checks are available on every trigger.

• Send message: post in a channel, in the source channel, or as a direct reply to the triggering message.
• Send DM: message the triggering member directly.
• React to message: add up to 3 emojis to the triggering message.
• Pin message and Create thread: pin the triggering message, or start a discussion thread on it.
• Add or remove a role, set a nickname.
• Timeout, kick, or ban the member (Administrator only).
• Delete the triggering message, or Wait 1 to 60 seconds between steps for custom pacing.

Role-granting actions can never hand out managed roles or roles with dangerous permissions, and message actions can only target channels in your own server.

Every automation can set two optional cooldowns in the builder's Limits section: a server-wide cooldown (run at most once every N seconds) and a per-member cooldown (run at most once per member every N seconds). New automations start with a sensible per-member default based on what their steps do (60 seconds for punishing steps, 10 seconds for responding steps); adjust or clear it freely. Automations with punishing steps always keep a built-in 30 second per-member spacing even if the cooldown is cleared.

On top of that, Flantic always applies built-in flood protection: rapid-fire events like message spam, reaction spam, or voice hopping are throttled per member, per automation, and per server, and role automations have a loop guard so two rules can never ping-pong a role forever. You do not need to configure any of this.

The Community tab on the Automation page is a shared library of automations published by other servers. Click any automation to see exactly what it does (a plain-English breakdown of its trigger, checks and steps), then install it. Publish your own from the menu on any automation card; its description becomes the public blurb.

1. 1Publishing strips everything server-specific: channels, roles and specific users are blanked, and your custom emojis are converted to plain text. The publish dialog shows exactly what changes.
2. 2Installing creates the automation in your server in a paused state. Anything that needs a re-pick (a channel, role or emoji) is flagged as Needs setup.
3. 3Open it in the builder, pick your channels and roles, then enable it. It cannot be enabled until setup is finished.

Free servers can have 2 automations active at once. Prime raises this to 15. Paused automations do not count toward the limit.