Using an FTP (File Transfer Protocol) or SFTP (Secure File Transfer Protocol) server as a bridge between Gecko and your CRM or SIS is a powerful solution to automate data transfer. Using SFTP connections or webhooks are both popular ways of integrating with Tribal SITS.
You must host your own SFTP server to use this integration method, as Gecko does not provide this service.
Engage
Integrating Engage with your SFTP
Gecko can push data to your SFTP server hourly, daily, weekly, or monthly. Before setting up the integration, be sure you have access to an SFTP server. Additionally, you'll need the following information about your SFTP to hand:
Hostname - the hostname of your SFTP server
Port - the port Gecko should use to access your SFTP server
Username - the username of your SFTP user. This user should have sufficient permissions to create new files
Password - the password for your SFTP user
Destination path - the destination/path Gecko should write any CSV files to
Filename - What Gecko should call the CSV file that we write to the destination path
Integrating forms/scripts
💡 Note: though the video above references integrating with Slate, the same method applies when integrating with your SFTP server!
Form/response data is pushed from Gecko to your SFTP server via a recurring response export from Gecko → your SFTP server.
Gecko can push over:
Any details captured on the form
response meta information;
When the response was captured
UTM parameters
Student Geo-IP information
Capture app compatibility
who was logged in when the response was captured
which device was used
Integrating events
Gecko event attendee information can be pushed directly to your SFTP server.
Gecko can push attendee information for all events or hand-picked events as required. Additionally, you can filter the export data so that only certain attendee statuses (i.e., “Attended”) are pushed over.
Integrating emails/texts
💡 Note: though the video above references integrating with Slate, the same method applies when integrating with your SFTP server!
Texts or emails sent from Gecko can automatically create an interaction on the student’s activity timeline in Slate. This is done by sending a recurring Messages export from Gecko to your Slate SFTP server. This export is then imported into Slate using a Source Format. This can be a “set-and-forget” type of action!
The data sent over can include the following:
Any desired Student details
The sender of the text/email (e.g., “Admissions - admissions@gecko-university.edu”)
The subject line of the email
The time/date the email/text was sent
The status of the email/text (i.e., clicked, opened, delivered)
Integrating calls
💡 Note: though the video above references integrating with Slate, the same method applies when integrating with your SFTP server!
Calls exports can be configured to send calling data from Gecko to your SFTP server. Gecko can push over:
Call data (start time, end time, outcome, caller ID, caller number)
An .mp4 recording of the call
The campaign of the call
Any student details required
Associated script responses
Importing from your SFTP into Engage
Importing data from your SFTP into Gecko is easy to do:
Upload the data you'd like to pull into Gecko and to your SFTP server
In Gecko, go to Settings > Import Data and pick + New Import
Set up a File Import and tell Gecko that it's a Recurring Import
Enter your SFTP credentials and map your import
Imports into Gecko can be fully automated, with Gecko checking for new files/importing every hour, 3 hours, 12 hours, 24 hours, or seven days.
Chat
Integrating Chat with your SFTP
Gecko can be configured to push conversation data to your SFTP server daily, weekly, or monthly. Exports are managed by going to Settings > Exports and configuring a Recurring Export.
Integrating conversations
💡 Note: though the video above references integrating with Slate, the same method applies when integrating with your SFTP server!
Any contact information or metadata captured in Gecko can be sent to your SFTP server
via a recurring Conversations export. This can run as frequently as Daily, Weekly or Monthly.
Gecko can push over:
Student identifiers (Name, Email, and any other data you want to capture)
Conversation metadata;
When the conversation took place
The channel the conversation took place on
Which agents/bots (if any) were involved
If using live chat:
The device type the student was using
The webpage the conversation was started on
Where the student is located (Geo-IP)
Device type-information
A link to the conversation transcript
Any questions? Start a live chat with a support team member, or feel free to explore the rest of our academy. Spotted an error or want to suggest a future article for the academy? Let us know here.