Technolutions Slate
Institutions using Technolutions Slate can configure an automated data flow with Element451 using secure file transfers. This integration allows institutions to exchange prospect and engagement data between the two systems using scheduled CSV files delivered over SFTP.
The integration supports sending prospect data from Slate into Element451 and importing Element451 engagement data, such as chatbot conversation summaries, into Slate.
🔁 Supported Integration#
- Method: File-based transfers
- Format: CSV
- Direction: Bi-directional
- Delivery:
- Slate Query → Secure SFTP → Element451 import schedule
- Element Export → Secure SFTP → Slate Source Format
Integration Architecture#
Typical data flow:
- Slate exports a query of prospects or contacts.
- The file is delivered to the Element451 SFTP server.
- Element451 imports and updates person records.
- Element451 exports leads and conversation activity.
- Files are delivered to the Slate SFTP server.
- Slate imports the data using Source Formats and Import Automations.
Quick Start Implementation#
Follow these steps in order to configure the integration.
Required Slate Field#
Element ID#
Create a custom field in Slate called Element ID.
This field stores the unique identifier generated by Element451 and is used to:
- match conversation records to the correct person
- attach future interactions to the same record
- prevent duplicate person creation
Populate this field during the lead import. Conversation imports should reference the same value.
Optional: Flag the Field as “Unique for Merging”#
Institutions may optionally configure the Element ID field as Unique for Merging within Slate.
When a field is marked Unique for Merging, Slate can use that value as a secondary identifier when matching records during imports. This can help ensure that Element451 data continues to associate with the correct person record even if records are merged or internal identifiers change within Slate.
For example, if two person records are merged in Slate and the original Slate ID changes, the Element ID can still be used to match incoming data from Element451 to the correct record.
Slate supports multiple identifiers during matching. During imports, Slate will typically attempt matching in the following order:
- Slate ID
- Other configured matching criteria
- Fields marked as Unique for Merging
Using Element ID as a unique merge field can improve long-term synchronization reliability between Element451 and Slate.
For more information, see the Slate documentation:
- Unique for Merginghttps://knowledge.technolutions.net/docs/unique-for-merging (opens in a new tab)
- Matching Criteria for Person Recordshttps://knowledge.technolutions.net/v1/docs/matching-criteria-for-person-records (opens in a new tab)
2. Configure Slate → Element451 Export#
Create a Slate query for the population you want to send to Element451.
Typical examples include:
- prospective students from marketing campaigns
- event registrants
- inquiry populations
- outreach lists
Recommended Fields
The query should include fields that align with Element451’s Person schema.
Common fields include:
- First Name
- Last Name
- Mobile Phone
- Program of Interest (optional)
- Slate ID
Slate ID helps maintain a persistent identity between systems.
3. Prevent Duplicate Lead Creation (Important)#
To prevent duplicate records in Element451, include a stable unique identifier in the export.
Recommended identifiers:
- Email (most common)
- Slate ID
- External ID field
Avoid exporting populations where the same person may appear multiple times with different emails unless matching rules are defined.
Institutions may choose to configure Element451 matching rules using:
- Slate ID
- External ID
This ensures existing records are updated instead of duplicated.
4. Configure the Scheduled Export#
From the Slate query interface:
Select Schedule Export and configure the following settings.
| Setting | Row | Value |
|---|---|---|
| Status | 2 | Active |
| Destination | 3 | Custom File Transfer |
| Connection | 4 | Element451 SFTP server |
| Path | 5 | Provided SFTP folder |
| Format | 6 | CSV |
| Delimiter | 7 | Comma |
| Headers | 8 | Enabled |
| Text Qualifier | 9 | Double quotes |
Scheduling
Recommended export frequency:
- Daily
Coordinate export timing with Element451 to ensure imports run after the file arrives.
Mapping to Element451#
Once the Slate export arrives on the Element451 SFTP server:
- Configure an Element451 Import Task
- Map the incoming fields to Element451’s Person schema
- Configure matching rules
Common matching fields include:
- Slate ID
- external ID
For complex mapping scenarios, consult your Element451 Implementation Specialist.
Validation and Testing#
Before enabling the scheduled export:
- Send 2–3 test records.
- Confirm field mappings with Element451.
- Verify records appear correctly in the People module.
Element451 → Slate#
Element451 can export the following data into Slate:
- leads generated through chatbot interactions
- engagement data such as Element conversation activity
These files are imported into Slate using Source Formats.
1. Confirm Slate Import Requirements#
Work with your Slate administrator to confirm:
- accepted file format (CSV or tab-delimited)
- required column headers
- matching logic
- destination objects (Person and Interaction)
A Source Format must be created in Slate to process incoming files.
Required Slate Field#
Element ID
Create a custom field called Element ID.
This field stores the unique identifier generated by Element451 and is used to:
- match conversation records to the correct person
- attach future interactions to the same record
- prevent duplicate person creation
Populate this field during the lead import.
Conversation imports should reference the same value.
Recommended Tracking Field#
Element Created Date
This optional field records when the contact was first created in Element451.
It helps with:
- reporting
- understanding inquiry timing
- troubleshooting imports
2. Configure the Element451 Export#
Work with your Element451 team to configure the export.
Define:
- export segment logic
- fields included
- delivery schedule
Typical configuration:
| Setting | Row | Value |
|---|---|---|
| Delivery | 5 | SFTP |
| Format | 2 | CSV |
| Headers | 4 | Included |
| Encoding | 3 | UTF-8 |
Exports are typically scheduled daily.
Lead Export Behavior#
Element451 exports typically include all contacts within the selected segment during each run.
Slate determines whether a record should be:
- created
- updated
- ignored
based on its matching rules.
This allows updates to existing contacts to be transmitted automatically.
Import Order (Important)#
If multiple Element451 files are delivered to the same SFTP folder, configure Slate Import Automation so they run in this order:
- Lead import
- Conversation import
The lead import must run first so the person record exists before the conversation interaction is attached.
Importing Element Conversations#
Element451 conversations should typically be imported into Slate as Interactions.
Interactions represent engagement events and are the recommended destination for chatbot activity imported from external systems.
Typical Mapping
| Element Field | Row | Slate Field |
|---|---|---|
| Element ID | 2 | Person matching field |
| Conversation Topic | 3 | Interaction Subject |
| Conversation Date | 4 | Interaction Date |
| Conversation Type | 5 | Interaction Code |
| Conversation Summary | 6 | Interaction Comments |
The Interaction Subject provides a visible description of the conversation topic.
Displaying Conversation Summaries in the Interaction Timeline#
When conversation summaries are mapped only to Interaction Comments, they may not appear directly in the interaction list view on the person record.
A practical workaround is to map the summary to a field that is visible in the interaction timeline, such as Interaction Subject.
Recommended Workaround#
To display conversation summaries directly in the timeline:
- Map the conversation topic to Interaction Subject
- Optionally map the conversation summary to Interaction Comments
- If the institution prefers the full summary visible in the timeline, map the summary to Interaction Subject
Example interaction timeline entry:
Interaction: Element Conversation
Date: May 7, 2026
Subject: Student asked about FAFSA deadlines and scholarship eligibility.
Alternative Display Formats#
Institutions may choose to include both topic and summary.
Examples:
Financial Aid Question — Student asked about FAFSA deadlines and scholarship eligibility.
or
Element Chat: FAFSA and scholarship eligibility question.
Formatting can be adjusted during Source Format mapping depending on how the institution prefers the interaction to appear.
SFTP Setup#
Slate must provide the following connection details:
- SFTP hostname
- port
- username
- authentication method (password or SSH key)
- destination folder path
Example path: /incoming/element/
Additionally, reach out to your Account Manager or Implementation Lead to get the IP addresses you will need to whitelist in Slate to allow Element to put files on the SFTP.
Validation and Testing#
Before go-live:
- Send a test export from Element451 to the Slate SFTP server.
- Confirm the file structure matches the Source Format configuration.
- Run the import in Slate.
- Verify:
- person records are created correctly
- Element ID is populated
- interactions appear on the person record
Adjust mappings if necessary.
Go-Live Checklist#
Before enabling schedules:
- Element ID field created in Slate
- Source Format configured
- lead import configured
- conversation import configured
- lead import runs before conversation import
- SFTP connection verified
- test records validated successfully
Lead Capture in Element451#
For leads to be exported to Slate, the chatbot must collect identifying information from visitors.
This is typically done using the Inquiry Flow skill in the Element451 agent configuration.
Inquiry Flow allows the chatbot to request:
- first name
- last name
- academic interest
Once collected, Element451 creates a contact record that can be exported to Slate.
Visitors who do not provide identifying information may remain anonymous and will not appear in exports.
Best Practices#
- Use Element ID as the primary cross-system identifier
- Configure import order carefully
- Test with small batches before enabling schedules
- Coordinate export timing with Slate administrators
- Keep interaction subjects concise and readable