API sync to ticketing system
Jump to a specific section by clicking a link
Overview | Samples | Variables | Alert Functionality | Best Practices & Tips | Related Alerts
Overview
Overview
This process will allow your larger customers to sync their ticketing system with your eAutomate. You add API details to a custom property on the Parent (or Child) record and publish self documenting page to your customer. This will allow service calls to sync between both systems, the call can be entered in either system and will update as it is worked.
Run Schedule:
Type of Output: Data Push
* * *
Sample
Sample
See a sample here.
* * *
Variables
Variables
Variable W: Default technician number
Variable X: Call type to be used for calls created by the API
Variable Y: Name of Note Type in EA that the API will use to add notes to
Variable Z: Name of Customer Custom Property that will store the API keys
Variable 11: Use PO Number as reference for CallID
Variable 12: Default call priority
* * *
Alert Functionality
Alert Functionality
This process will allow your larger customers to sync their ticketing system with your eAutomate. You add API details to a custom property on the Parent (or Child) record and publish self documenting page to your customer. This will allow service calls to sync between both systems, the call can be entered in either system and will update as it is worked.
The process exposes the necessary eAutomate functions (Create Call, List Open Calls, Get a Specific Call, Add Notes to a Call, Cancel a Call) that are needed for ticketing system integrations. It does not implement any integrations into any specific ticketing systems, rather only exposes the needed endpoints as a REST API. See a sample here.
Please note, this process also works for ECi Hosted clients.
Add the API details to a test DB to start. Clients testing this say it takes less than a day to build the integration. Our 1st client's customer went live 5 days after starting testing. Note the client's customer had the inhouse skills needed.
Create a new site in IIS.
Have the binding set to clientapi.yourdealer name.com (or change that to whatever you like, it just needs to match the DNS entry)
You will need to make the DNS entries for it . You may also need to adjust the firewall, etc.
Add a second binding for https:// with the same URL, select an SSL cert (don't risk bringing your main site down by double-using a single-use cert). Have the site set to refuse non-https requests, for security purposes.
Install the ASPNET Core hosting bundle Download ASP.NET Core 8.0 Runtime (v8.0.6) - Windows Hosting Bundle Installer (microsoft.com) on the web server.
* * *
Best Practices & Tips
Best Practices & Tips
Coming soon
* * *
Related Alerts
Related Alerts
ID664 - Service Now Sync
* * *
0 Comments