mirror of
https://git.yylx.win/https://github.com/sogjugz/freescout-remote-response.git
synced 2025-10-03 18:21:33 +08:00
Freescout module to process remote responses
Config | ||
Console | ||
Database | ||
Entities | ||
Http | ||
Providers | ||
Public | ||
Resources | ||
Tests | ||
vendor | ||
.gitignore | ||
composer.json | ||
composer.lock | ||
LICENSE | ||
module.json | ||
README.md | ||
RemoteLogo.png | ||
start.php |
FreeScout Remote Response
This repository contains a FreeScout module that allows processing responses via a remote server.
Features
- Automatically processes conversations through a remote service and injects responses effortlessly.
- Allows different remote servers for each Mailbox, enabling personalized responses for each one.
- Integrates with almost any remote service. Supports
GET
andPOST
requests with customizable headers for authentication or token usage. - Injects remote responses directly into the editor.
Requirements
- FreeScout version 1.8 or higher
Configuration and Usages
- Upload the SsRemoteResponse module (ZIP) to your FreeScout Modules folder. Ensure the folder is named
SsRemoteResponse
. - For each mailbox you want enabled, configure the necessary fields to connect with your remote service.
- If you want to use headers settings, ensure the headers are encoded in a valid JSON value. Example:
{"Authorization": "Bearer SomeTokenHere"}
- Toggle the Enable switch at the top of the mailbox settings page.
- On the conversation page, use the cloud button in the toolbar to inject the remote response while replying.
Important Notes
- This module only connects your FreeScout instance to a remote service. You are responsible for implementing the service, which must respond with the text to inject into the reply.
Data Sent to the Remote Service
{
"conversation_content": "Customer: \n Initial request: \n Agent: First response \n Customer: Customer response",
"customer_name": "John Doe",
"customer_email": "John.doe@domain.com",
"conversation_subject": "Test conversation"
}
The conversation content includes all conversation threads in a readable text format.
Your server must return a text response, which will be automatically injected into the reply editor.