Integration availability depends on the features enabled for your organization. Managing the settings requires administrator permissions, and the settings are configured in Spotilla's browser service. During setup, check feature availability, saved credentials, connection functionality and the settings for the required transfer function separately.
Open the settings for the correct connection
- In the browser service navigation, select Settings → Integrations.
- Find the connection in the Integrations list. The name link in the Software column opens either the settings form for the old implementation or the dedicated tab for the new implementation.
- Check which implementation has been agreed for your organization before entering credentials. The old Lemonsoft and the new LemonERP are separate connections. Similarly, Procountor and Procountor (New) use different settings.
The LemonERP, Procountor (New), KIHO and GSFleet connections enabled for your organization are also available on their dedicated tabs in the Integrations section. These contain Authentication, Settings and Integration Logs. GSFleet may appear on its own tab even if it does not have a row in the integration list.
If the connection appears neither in the list nor on its own tab, discuss enabling it with your Spotilla contact. Credentials for another integration cannot replace a missing feature.
What does the integration status tell you?
The Integration status column in the list shows In use or Not in use. The basis for this status varies by connection:
- For older financial management and custom connections, the status is based on whether an integration account exists.
- For the new LemonERP, Procountor and KIHO connections, the status is based on whether a saved credential record exists.
- For Google SSO, the status is based on the login URL and certificate settings. For Zapier, it is based on whether an application configuration exists for the connection.
In use is therefore not a general indicator of functionality. On its own, it does not confirm that the credentials are valid, that a transfer is enabled or that an individual item of data has been transferred. Conversely, stopping a transfer function through its own setting may not change the status in the list.
Save the credentials and check the environment
Open the new connection's Authentication tab. Enter the credentials required by that integration and check Environment. The default for new credentials is Production; the other option is Sandbox.
The effect of the environment selection depends on the connection:
- Procountor (New): the selection switches between the production and test services. Use credentials for the selected environment.
- LemonERP: the connection uses the service URL saved in the credentials. Also check the URL and database; the environment selection alone does not change the service URL.
- KIHO: Production and Sandbox use the same default URL. If Base URL is specified, the connection uses it.
- GSFleet: both environment options use the same service.
Sandbox therefore does not mean a separate test environment for every connection, nor does it prevent changes made by an actual transfer. Verify the URL, the target system for the credentials and the transfer options before starting transfers.
Select Save, then Test Connection. The test uses saved credentials, so changes entered in the form but not saved are not included in the test. For LemonERP, Procountor and KIHO connections, saving and testing the connection are separate actions. For GSFleet, saving also checks the connection: if the check fails, the new credentials are not saved.
A successful test updates Last verified successfully. This shows the time of the latest successful connection test, rather than continuous connection monitoring. An earlier time may remain visible after credentials are changed or a test fails.
The LemonERP test checks login, the Procountor test checks that a new access token can be obtained, the KIHO test checks authentication and the connection, and the GSFleet test checks access to the device list. None of these proves that data for a particular invoice, customer or device has been transferred.
Enable the required transfer and verify the result
Open the connection's Settings tab or the settings form for an older connection. Select the intended transfer direction and the functions you need. Check their enable options, filters, destination folders, field mappings, required links between items and any billing and scheduling settings. Save the settings. Saved credentials or a successful connection test alone do not enable all transfers.
For example, Procountor customer transfers require a root folder in addition to enabling the transfer. KIHO requires links between Spots and KIHO items, as well as enabling telemetry synchronization. The prerequisites and effects of each transfer are described in the LemonERP, Procountor, KIHO and GSFleet instructions.
If a function has a preview, check its results before performing the actual transfer. A connection test and a transfer preview are separate checks. A notification that a transfer has been added to the queue does not yet mean that it has been processed successfully.
Check the first actual transfer in both systems: was the correct item processed, is the data correct, and was the intended link or update created? Open the new connection's Integration Logs; logs for older connections are on the Changelog tab in the Integrations section. Find the relevant processing event by time and item, and check its status and description. Correct the reported issue before starting another transfer. See investigating an integration error using the log.