Handler
Features
  • Live control and moderation
  • Anticheat and a network of communities
  • Automations
  • Player tickets
  • Stats, weapons and seasons
  • Public pages, votes and Discord
  • Mobile app
  • Migrate
PricingAppDownloadQuestions
FrançaisTry the demoSign in
Connect my server
  • Features
    • Live control and moderation
    • Anticheat and a network of communities
    • Automations
    • Player tickets
    • Stats, weapons and seasons
    • Public pages, votes and Discord
    • Mobile app
    • Migrate
  • Pricing
  • App
  • Guides
  • Download
  • Questions
  • Try the demo
  • Sign in
  • Français
Guides

Your first automation, step by step

We will send a welcome message 15 seconds after a new player joins. Two paths: copy the official example, or build everything yourself. Both end the same way.

10 minutes

On this page

  1. What we are building
  2. Path 1: start from the official example
  3. Path 2: build everything from scratch
  4. When everything is ready: activate it
  5. Going further

What we are building

Why 15 seconds? It gives the player time to pick a team. A message that arrives too early gets lost in the selection screen.

Player joinsFirst visit?trueWait 15 sPrivate messagefalseNothing happens

You need a server already linked to your organization, and a role that lets you manage automations. If a step refuses you, see the “Troubleshooting” guide.

Path 1: start from the official example

  1. In the menu, open Automations.
  2. Scroll down to the Official examples section, Welcome category.
  3. Find the Welcome newcomers card (with the Official badge). Click Preview to look at it read-only: nothing is saved.
  4. Click Use. The editor opens on a copy: Player joins, If, Wait 15 s, Private message, Message to all.
  5. Click the Private message card. On the right, in Node settings, change the text of the Message field.
  6. At the top, name the automation, then pick servers with the Servers: All servers button.
  7. Click Save. You see “Automation saved.” and the switch stays on Paused.

Do not activate it yet: go through the “Test safely” guide first. When you are ready, flip the switch to Active, then click Save again.

Path 2: build everything from scratch

  1. In Automations, click Start from scratch. An empty canvas opens: “An automation starts with a trigger: what sets it off.”
  2. At the top left, type a name, for example “Welcome”.
  3. Click Choose a trigger, then Player joins (“On every connection.”). A first card appears.
  4. On the card, the output has a +. Click it: the Add a step window offers Suggestions. Pick Player condition (or type “If” in Search steps).
  5. In the right panel, under Conditions, click Choose data, pick First visit, then the operator is true. Only new players will get through.
  6. The If card has two outputs. Click the + of the true output, search for Wait, then set Duration (seconds) to 15.
  7. Click the + of the Wait card, pick Private message, then write your text in the Message field.
  8. To drop the player's name into it, click Insert data under the field and pick Player › Name (details in the “Data in your messages” guide).
  9. If a To fix before saving box appears under the canvas, read it: it says which card has a problem. A red dot also marks the card.
  10. Pick your servers with Servers: All servers, then click Save.

The false output of the If card stays unlinked: a player who is not new gets nothing. That is on purpose.

The “Add a step” window with the list of triggers.
Choosing a step: suggestions first, then every step by category. The search box at the top filters the list.

When everything is ready: activate it

  1. Flip the Active switch in the top bar.
  2. Click Save.
  3. In the Automations list, the row shows Active and, once a player has joined, the date of the last run.
  4. To put it to sleep, flip the switch back to Paused and save. Nothing is deleted.

Every run is recorded in the Log, at the bottom of the editor. That is where you check that a real player received their message.

Going further

  • Add a Message to all step so the server welcomes the newcomer.
  • Add a Rate limit so an unstable connection does not resend the message in a loop.
  • When you want the same rule with simple settings to fill in, see the “Packs” guide.
Previous guideUnderstand automationsNext guideTest safely
Handler
FeaturesLive control and moderationAnticheat and a network of communitiesAutomationsPlayer ticketsStats, weapons and seasonsPublic pages, votes and DiscordMobile app

Handler

Try the demoConnect my serverSign inPricingDownloadMigrateGuidesChangelogAPI documentationFrançais

Legal

Legal noticePrivacyTerms of useTerms of saleData processing

Contact

Support[email protected]