How does it work?

The Populi integration is bi-directional, meaning data can be synced in two directions:

• Element451 → Populi
• Populi → Element451

The integration is designed to be reusable and configuration-driven, allowing the workflow to be tailored based on a partner’s needs while still following a standard overall sync pattern .

Sync Configuration

The Populi integration can support either unidirectional or bi-directional syncing, depending on the partner’s implementation.

Element451’s Populi integration supports:

• Element451 → Populi sync
• Populi → Element451 sync
• Document upload workflows???

In practice, not every partner will use every part of the integration. The exact behavior depends on the school’s configured scope.

Element451 → Populi

This sync process sends data from Element451 to Populi.

The standard Element → Populi flow begins by loading the client-specific configuration, translating Element student data into Populi-compatible values, attempting to match the student in Populi, creating a new Populi student if needed, saving the Populi identity back into Element, and then populating the rest of the student-related data .

How the Sync Is Triggered

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

1. A label—Element451 to Populi - Trigger Sync—is applied to a contact record.
2. This label triggers the rule Element451 → Populi Sync.
3. The rule calls the webhook Element451 to Populi Sync(), which starts the integration process.