Element451Integrations Guide

Functional Overview

Updated Article

How does it work?#

The Anthology integration is bi-directional, meaning data is synced in two directions:

  • Element451 → Anthology
  • Anthology → Element451

Element451 uses a contact-centric data model, so all integration processing occurs at the contact level rather than the application or opportunity level. When a sync is triggered, the entire contact record is processed.

This includes:

  • Biographic and demographic information
  • Contact details
  • Previous schools
  • Applications

Sync Configuration#

The default and recommended setup is unidirectional syncing, syncing Element to Anthology.  Bi-directional syncing is available for partners who wish to bring back data into Element (be it updating or creating new records)

Element451 → Anthology#

This sync process sends data from Element451 to Anthology.

Element451 uses a combination of:

  • Configurable platform features (labels, rules, webhooks)
  • Managed integration processes maintained by Element451

How the Sync Is Triggered#

By default, the integration is initiated through the following sequence:

  1. A label—Element451 to CampusNexus - Trigger Sync—is applied to a contact record.
  2. This label triggers the rule Element451 → CampusNexus Sync.
  3. The rule calls the webhook Element451 to CampusNexus Sync (), which starts the integration process.
  4. Within a few minutes, the record appears in the Integration Log with a status of In Progress.
  5. The record is processed and sent to the Anthology, typically within 10–15 minutes.
  6. Once complete, the Integration Log will show a status of Success or Error.
    • Error records include detailed messages and, when applicable, the payload sent.

Errors can be reviewed and resolved using internal troubleshooting steps or through Live Support (How to Work with Live Support (Managed Integrations)).

Element451 Delivered Functionality#

The following components are included in all managed integration instances and control how data is sent to Anthology.

Label: Element451 to CampusNexus - Trigger Sync#

  • This label is used to manually trigger a sync for a contact.
  • Once the sync begins, the label is automatically removed, allowing it to be reused for future syncs.

Rule: Element451 → CampusNexus Sync#

  • This rule is triggered when the Element451 to CampusNexus - Trigger Sync label is added.
  • Partners can add additional triggers to automate syncing. Common examples include:
    • Decision release
  • When triggered, the rule:
    • Calls the Element451 to CampusNexus Sync () webhook
    • Removes the trigger label (if present) to allow future reuse

Webhook: Element451 to CampusNexus Sync()#

  • Webhooks are used to send automated notifications to external systems.
  • In this case, the webhook sends the Element451 record ID to the integration process to begin syncing.
  • This webhook is pre-configured and does not require modification.

Integration Process#

  • The integration runs in a cloud-hosted environment managed by Element451.
  • During processing, the system:
    • Extracts data from Element451
    • Transforms it into the format required by Anthology
    • Sends it to the appropriate Anthology endpoints
  • Multiple validation checks occur throughout this process to ensure data accuracy.
  • If an error occurs:
    • It may stop the entire sync, or
    • It may only impact a specific data element while others continue processing

All activity is recorded and surfaced in the Integration Log.

Integration Log#

  • The Integration Log displays the status of each sync attempt.
  • For each record, you can view:
    • Processing status (e.g., In Progress, Success, Error)
    • Error details, when applicable
    • Additional context to support troubleshooting

Anthology→Element451#

This sync process sends data from Anthology (SIS) to Element451, updating or creating records based on changes made in the SIS.

How the Sync Works#

Once configured, the Anthology → Element451 process runs automatically:

  1. On a scheduled cadence (configurable based on a partner’s needs) every x minutes, Element451 checks Anthology for records that were updated in the last x minutes.
  2. For the records pulled, Element451 can be configured in several ways:
    1. Evaluate the school status associated with the pulled Anthology records and only process records with statuses that the partners has indicated they want to process.
    2. Only create records in Element
    3. Create or Update existing records in Element
  3. For the records identified to be processed, Element451 performs a data pull from Anthology.
  4. The data is transformed and loaded into Element451.

Data Sources and Translation Tables#

Data sources in Element451 provide available values for fields (e.g., majors, terms, degrees) and ensure proper alignment with Anthology by storing the corresponding Anthology Codes/IDs required for integration processing.

Additionally, there are several translation tables that are configured behind the scenes that provide a level of translation between Element451 values and Anthology values.

Important Guidelines#

For any data source that is synced with Anthology:

  • Do not add or remove values directly in Element451.
    • Adding values can cause sync errors due to missing translations.
    • Removing values may result in them being automatically re-added during a future sync.
  • If a new value is needed:
    • Add it in the SIS first, then request a data resync through Live Support.
  • If a value needs to be removed:
    • Contact Live Support to determine the appropriate approach.
  • The only fields that can be safely edited in Element451 are:
    • Title / Name / Label
    • Active / Inactive status (if available)

All other synced fields should remain unchanged.

How Data Source Syncing Works#

  • During implementation, Element451:
    • Populates data sources in the platform
    • Builds translation tables required for Anthology integration
  • After implementation:
    • Additional resyncs can be requested as needed

Data Sources Synced#

The following data sources are typically created and synced:

  • Admission Reps
  • Campuses
  • Citizenship Statuses
  • Degrees
  • Genders
  • Majors
  • Marital Statuses
  • Races
  • Suffixes
  • Terms
  • Titles

Translation Tables Synced#

Translation tables map Element451 values to Anthology identifiers and are required for data exchange.

These typically include:

  • Admission Reps
  • Billing Methods
  • Campuses
  • Citizenship Statuses
  • Countries
  • Decisions
  • Degrees
  • Document Types
  • Expected Start Dates
  • Genders
  • Grade Scales
  • Majors
  • Marital Statuses
  • Program Versions
  • Terms
  • Titles
  • Suffixes
  • Races

Requesting a Data Source Re-sync#

If updates are needed to a data source (such as new values need to be added):