We use cookies to allow the display of personalised content, statistics collecting and sharing on social media. You can review your consent by clicking on "Manage cookies" at the bottom of the web page. If you would like to know more then please read our confidentiality policy.
Cookie Preferences
We use these cookies to ensure the correct function of the site. Essential cookies allow you, for example, to sign in to and navigate our site securely. They also allow us to keep your account secure and prevent fraud.
These cookies allow us to detect problems with the experience on our site and improve our client relations. They are harmless to you and your data.
With the Quicktalk and Prestashop integration, your contacts are automatically synced and will appear on the dialer during incoming calls. You’ll instantly see the contact’s first name, last name, company,
and a direct link to their Prestashop profile. These details also appear in your call log for each inbound and outbound call.
Note : Your Prestashop contacts will not appear in the “Contacts” tab of your Quicktalk space. This does not mean the integration was unsuccessful.
How to set up the integration
From your prestashop dashboard, go to settings then select advanced settings, find the Webservice option and click on it:
Add a new key:
Click generate to get a code and fill out the necessary information, the permissions that you should give are: addresses, customers, suppliers:
Once you click save, copy the key, go to quicktalk app and start the activation:
Quicktalk will ask you for the following information, check the screenshots below to see how to get the correct urls):
Prestashop base admin url (https://mystore-domain.com/admin)
*no forward slashes at the end.
Prestashop base api Url (https://mystore-domain.com/api)
*no forward slashes at the end.
Api Key
If you ever receive a call and you click on the redirection link from the quicktalk dialer to view the contact in PrestaShop and it doesn't work,
it's because PrestaShop generates tokens when pages are visited in the dashboard. As a result, redirecting to the URL leads to an error: 'Invalid token',
even if you are authenticated. To fix the issue, you need to disable token protection in the back office.