Server Values
Theerlc_server_value block returns a single piece of metadata about your linked server. Set its FIELD dropdown to the property you want to read.
Time Blocks
Use these value blocks to read the current time, perform arithmetic on timestamps, and format output for logs or Discord messages.erlc_time_unix
Returns the current Unix timestamp as a number. No inputs required.
erlc_time_clock
Returns the current time as a clock string (e.g.
14:35:00). No inputs required.erlc_time_date
Returns the current date as a string (e.g.
2025-06-10). No inputs required.erlc_time_weekday
Returns the current day of the week as a string (e.g.
Tuesday). No inputs required.erlc_time_add
Adds a number of seconds to a timestamp. Inputs: TIME (timestamp), SECONDS (number). Returns a new timestamp.
erlc_time_difference
Returns the number of seconds between two timestamps. Inputs: A, B.
erlc_time_format
Formats a timestamp into a custom string. Input: TIME. Set the FORMAT field to your format pattern (e.g.
YYYY-MM-DD HH:mm).erlc_discord_timestamp
Converts a timestamp into a Discord timestamp markup string. Input: TIME. Set the STYLE field to one of:
t (short time), T (long time), d (short date), D (long date), R (relative).Webhook Input Blocks
When an automation is triggered by an incoming webhook URL, you can use these blocks to read the fields from the incoming payload. They are only available inside webhook-triggered automations.Webhook input blocks are only available inside automations triggered via an incoming webhook URL. Using them in other automation types will produce no output.
Raw Payload
erlc_webhook_text
Returns the raw body text of the incoming webhook request. No inputs required.
erlc_webhook_text_contains
Returns
true if the raw webhook body contains the given string. Input: TEXT.erlc_webhook_text_starts
Returns
true if the raw body starts with the given string. Input: TEXT.erlc_webhook_text_ends
Returns
true if the raw body ends with the given string. Input: TEXT.Structured Fields
Useerlc_webhook_field to read a named field from the parsed webhook payload. Set the FIELD dropdown to one of the following:
Use
erlc_webhook_has_field with the same FIELD dropdown to check whether a field is present before reading it — this prevents empty-value errors in conditional automations.
Command Arguments
If the webhook payload includes a command, use these blocks to work with its arguments:erlc_webhook_command_name
Returns the command name from the webhook payload. No inputs required.
erlc_webhook_argument
Returns the argument at a specific position. Input: INDEX (zero-based number).
erlc_webhook_arguments
Returns all arguments as a list. No inputs required.
erlc_webhook_argument_count
Returns the total number of arguments in the payload. No inputs required.
Custom Event Values
Useerlc_custom_event_value to read a field from a custom event payload. Set the FIELD field to the name of the key you want to extract from the event data.
Example: Reading a Webhook Payload and Acting on It
The following automation checks whether an incoming webhook payload contains aPlayerName field, reads it along with the EventType, and sends an ERLC command using that data.
1
Guard with erlc_webhook_has_field
Before reading
PlayerName, the erlc_webhook_has_field block confirms the field exists in the payload. This prevents the automation from failing on webhook calls that don’t include player data.2
Log the event type
erlc_webhook_field reads the EventType field and erlc_log writes it to the Studio panel so you can trace which event fired.3
Run a command using the player name
A second
erlc_webhook_field block reads the PlayerName and passes it directly to erlc_command, which sends the command to your ERLC server.