Skip to main content

Available Merge Fields for Alerts

Updated today

Merge fields are a powerful way to make your alerts dynamic, personalized, and context-aware. Instead of sending generic notifications, merge fields automatically pull in relevant data, like student names, medication details, or request information, so each message feels tailored and actionable.

This is valuable in a school setting, where clear, specific communication can save time and reduce back-and-forth. Whether you're notifying staff about medication inventory or following up on a form request, merge fields ensure your alerts include the right details at the right time.


How Merge Fields Work

Merge fields are placeholders (e.g. Student_name) that are replaced with real data when an alert is sent. You can include them in alert templates, and the system will automatically populate them based on the context of the alert.

Example:

“{Student name}’s medication {Medication name} is expiring on {Expiration date}.”

Might render as:

“Jordan Smith’s medication Albuterol is expiring on March 15, 2026.”


Available Merge Fields

Below is a complete list of supported merge fields for alerts by alert type.

General

These merge fields are available for all alert types.

  • {Instance name}
    The name of your school or portal as configured in the system.

  • {Viewer full name}
    The full name of the person viewing the message.


Student Information

  • {Student name}
    The student’s first and last name.


Form Requests

Including Form request follow up, Form request, and Form request packet.

  • {Request title}
    The title of the form request or packet.

  • {Recipients}
    A formatted list of recipients for a form request or packet.

  • {Sender}
    The full name of the person who sent the form, packet, or most recent follow-up message in a thread.

  • {Subjects}
    The name of the subject(s) of the request.


Medication & Inventory Alerts

  • {Medication name}
    The name of the medication tied to the alert.

  • {Current inventory quantity}
    The current inventory amount.

  • {Expiration date}
    The medication’s expiration date.


Tips & Best Practices

  • Combine fields for clarity
    Use multiple merge fields together to create complete, informative alerts.

    Example: “{Student name}’s {Medication name} is low {Current inventory quantity}.”

  • Test your alerts
    Before rolling out broadly, send test alerts to confirm that fields populate as expected in your specific workflow.


​Questions or Concerns?

Please do not hesitate to reach out to the August Schools Support Team at via live chat with the "Help" icon or via email at [email protected].

Did this answer your question?