Element451
Education & LMSConnect AI agents to Element451, a higher education enrollment CRM. Agents update person profiles, create tasks and notes, register event attendees, and enroll people in journeys so admissions teams keep every prospect moving.
What This Integration Enables
Element451 is an enrollment CRM, which means its records are prospective students rather than accounts, and its journeys are outbound communication sequences aimed at teenagers and their families. FlowRunner agents work the whole object model: find people by a filter definition, read and update profiles, write notes onto a timeline, apply labels for segmentation, create and reassign counselor tasks, register attendees for open houses and information sessions, enroll people into journeys, and manage the outbound webhook configurations that push Element451 activity to other systems.
The interesting design decision in this API is that Find People is described as returning a preview. The vendor built a way to see who a filter matches before acting on them, and an agent that skips it is throwing away the only dry run available. FlowRunner uses that preview as the checkpoint. Routine work runs unattended: writing inquiry data onto profiles, opening follow-up tasks, registering an attendee who signed up for a tour. The step that reaches an applicant's inbox goes through a person first. That is the digital andon cord applied to admissions, where the cost of a wrong send is measured in trust with a family, not in a bounced email.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Inquiry capture to counselor follow-up
A prospective student completes a form in Typeform. The agent calls Update Person to write the program of interest and the inquiry source onto the profile, calls Add Person Labels to tag the record, and calls Create Person Note with the free-text responses so the counselor sees what the student actually said. It then calls Create Task assigned to the counselor who owns that program, with a due date set by the response-time policy. The counselor opens the task and the whole context is already there.
Open house registration and reminders
An event registration arrives from a landing page or a partner list. The agent calls List Events and Get Event Details to resolve the right occurrence, then calls Register Attendee for Event with the student's name and email and the number of guests. It posts a confirmation through Twilio or email, and creates a follow-up task for the counselor the day after the event. Students who registered but did not attend get a different task than those who did, because the agent reads the outcome back before deciding.
Yield campaign built and reviewed before it sends
The enrollment team wants to reach admitted students who have not yet deposited. The agent calls List Segments to resolve the saved audience definition, calls Find People with the matching filter to preview who it captures, and calls Create Communication, which Element451 creates in a draft state so the content and audience can be configured before anything sends. The draft, the preview count, and a sample of matched records go to the enrollment manager together. Only after the manager confirms does the agent call Enroll Person in Journey for the approved list.
Human-in-Loop Highlight
The gate is on Enroll Person in Journey, and the reason is what the connector does not contain. There is an action to enroll a person into an automated journey and no action to take them out of one. Once enrollment starts, the journey's sequence begins running for that person, and unwinding it means a human working inside Element451 while messages are already in flight. That risk is not theoretical, because the audience comes from a filter definition, and a filter that is one operator wrong quietly resolves to the wrong cohort: last year's applicants instead of this year's, or every inquiry rather than only the admitted ones. So the agent uses Find People as the dry run the vendor provided. It runs the filter, reads the preview, and stops: "This filter matches 1,847 people for the deposit reminder journey. Expected range for admitted-not-deposited is 300 to 500. Sample of 5 matched records attached, and 2 of them are prior-cycle applicants. Enroll anyway, narrow the filter, or cancel?" Nothing is enrolled until that question is answered. Profile updates, notes, labels, and task creation keep running without it.
Agent Capabilities
22 actionsPeople
7- Find People Returns a preview list of people matching a filter definition, with pagination. Used as the dry run before any bulk action, and as the source list for batch processing.
- Get Person Profile Retrieves the general profile for one person by user ID, including name, contact details, and profile type.
- Update Person Updates profile fields identified by their Element451 slug. Only the supplied fields change, so an agent can write an inquiry source without disturbing anything a counselor entered.
- Delete Person Deletes a person record, soft by default, with an option for a hard delete that permanently removes the record and its data. The hard delete cannot be undone and should never run from an unattended sweep.
- List Person Notes Lists the notes on a person's timeline. Used to read prior staff observations before an agent adds its own or opens a task.
- Create Person Note Adds a note to a person's timeline, accepting HTML, optionally private and typed by a note taxonomy. Used to record what happened in another system so the counselor sees one history.
- Add Person Labels Applies one or more labels to a person by taxonomy GUID. Used for segmentation and routing across journeys, communications, and reporting.
Tasks
4- List Tasks Lists staff to-do items in the workspace, with pagination. Used to check for an open follow-up before creating a duplicate.
- Create Task Creates a task with a type, status, and due date, assigned to internal users or to teams, and optionally related to a person. Used to hand a judgment call to the counselor who owns the relationship.
- Update Task Updates fields on an existing task, commonly to change status, reassign, or shift the due date.
- Delete Task Permanently deletes a task by its GUID. Used for cleanup of tasks created in error.
Events
3- List Events Lists events such as open houses, tours, and information sessions, with pagination.
- Get Event Details Retrieves full configuration for one event, including scheduling, venue, and registration settings. Used to resolve the correct occurrence before registering someone.
- Register Attendee for Event Registers a person for an event as an administrator, creating or matching the person record from first name, last name, and email, with an optional guest count.
Journeys and Campaigns
4- List Journeys Lists the automated nurture and communication journeys configured in Element451. Used to resolve a journey by name before enrollment.
- Enroll Person in Journey Enrolls one person into a journey, starting its sequence of actions for them. This is the step that reaches an applicant, and it is where the approval sits.
- List Communications Lists campaign communications, email and SMS sends, with pagination.
- Create Communication Creates a campaign communication with a title and the selected channels. It is created in a draft state, so content and audience can be configured and reviewed before anything sends.
Data and Webhooks
4- List Segments Lists saved audience segments, the reusable filter definitions used to target people across journeys, communications, and reporting.
- List Webhook Configs Lists the outbound webhook configurations that push Element451 event data to external URLs.
- Create Webhook Config Creates an outbound webhook configuration with an HTTP method, optional static payload, request limit, and custom headers. Used to point Element451 activity at a FlowRunner endpoint.
- Delete Webhook Config Deletes a webhook configuration by GUID, stopping all future deliveries for it.
Frequently Asked Questions
What can FlowRunner do with Element451?
FlowRunner agents can run Find People, Get Person Profile, and Update Person in Element451, plus 19 more actions.
Does connecting Element451 to FlowRunner require OAuth?
No. Element451 connects to FlowRunner with an API key, no OAuth flow required.
Can Element451 trigger a FlowRunner workflow automatically?
Element451 doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Element451
$100 in credits. No card required. Connect in minutes.