Magento 2 integration

Question

Accepted Answer

With our Magento integration, you can display customer information from your Magento store in the conversation view.Order information can be searched by entering the customer’s phone number or email address, depending on the contact channel.

If you are using Magento 1, please click here. 
Installation in Magento
This will guide you through the installation process of the Dixa SearchAPI extension for Magento 2. In order to install the extension, you will need SSH access to your Magento 2 instance.
Step 1: Download the search plugin here. If your customers check out as guests, try our beta plugin.
Upload the archive provided by Dixa to your Magento server. This can be accomplished with SCP, Finder, Explorer, or any other file manager or FTP client.
Now open up an SSH session on your Magento server.
We will start by turning on Magento’s maintenance mode during the installation process in order to prevent issues from occurring. In addition, we’re also going to back up both the codebase and the database of the instance.
We can now proceed to the installation of the extension’s files.

For the beta plugin, use the following:
The final installation step is to disable the maintenance mode on your instance. For this, run php bin/magento maintenance:disable
Configuration
Connect to the administration interface of your Magento 2 instance. Go to Stores > Configuration.

A new configuration section (Dixa) is now available.

In the SearchAPI configuration, click on Generate if no API key is defined. This will generate a new API key. This key is used to allow Dixa to securely access order information.Remember to save the new API key after generating it by pressing the button in the top-right corner.

In Dixa
Go to Settings.
Go to Integrations.
Click on Configure Integration under the Magento V1 icon
Click Add Magento.
Enter a title for the card (ie, Order History).
Insert the API Key from your Magento account.
Insert your Magento Subdomain URL.
Click Save.

Troubleshooting
"error_message": "Upstream not available: magento"
This error code has often been seen caused by the HTTP header value exceeding the configured limit of 8192 characters.
It means that the server is adding a header to the responses it sends back to Dixa, where the length exceeds 8192 characters. 
You should check your Magento instance configuration and see if there is such an offending header and either remove it or limit its length.
Furthermore, you need to invalidate the cloud instance (eg, Cloudflare), otherwise the calls might hit a cached one with a previous state
Template
You can edit the template if you want to display other information from Magento in Dixa.
The template can be written in HTML and supports Liquid, too.

You can always copy the default template if you want to go back to the first revision.