Connecting a data source

Use Data > Import Data to begin Perslace’s four-step data-source flow. After connecting, verify both the connection status and representative transaction records.

For: Admin and data or integration owner

Prerequisites

• An approved test data source
• Least-privilege, preferably read-only credentials
• The expected source schema and a representative sample
• An approved refresh requirement
• Authority to connect and validate the source

Protect credentials and customer data

Never add passwords, connection strings, API keys, or unrestricted client data to documentation, screenshots, chat messages, or support requests.

Connect and validate the source

1. Open Data, then select Import Data.

   

2. Start Data Source. The reviewed interface displayed Step 1 of 4.

3. Select the approved source type.

   The test connection was labelled External Database / Direct SQL. PostgreSQL and MySQL icons were visible, but this does not confirm that every connector is enabled for every organisation.

4. Complete Step 1 using approved test credentials.

5. Follow the current on-screen instructions for Steps 2 through 4.

   Verification required

   The fields, connection test, mapping, validation, and completion behaviour in Steps 2 through 4 were not opened during the review because the active connection could not be safely disconnected.

6. Return to the connection card and review the available controls and status information: Active, Last Sync, schedule, Manual Sync, Sync History, See Configuration, and Disconnect.

   

7. Open Sync History and confirm that a recent run completed successfully.

   The reviewed test workspace used a 10-minute schedule. This is not a universal default.

8. Open View Data and validate known records.

   Observed fields included transaction and employee identifiers, client, date, region, amount, first-deposit flag, status, type, and a custom user ID. Which fields are required or optional remains unverified.

9. Compare dates, identifiers, values, and visible employee attribution with the approved source sample.

Expected result

The source shows Active, a recent sync succeeds, and representative records contain the expected values and visible employee identifiers or attribution.

Important notes

• Manual Sync can change downstream calculations and reports. Use it only when authorised.
• Do not capture See Configuration unless you can guarantee that all secrets are excluded.
• Disconnect is high impact. Downstream effects and recovery behaviour remain unverified.
• Publish connector-specific instructions only after the connector has been enabled and safely tested.

Troubleshooting

The connection is not Active

Recheck the approved source type and connection details. Capture only the sanitised error message.

Recent data is missing

Review Last Sync, Sync History, the configured schedule, and whether a webhook was expected to send the update.

A known record is missing

Confirm that the record exists at the source, align the expected time zone, check its identifiers, and inspect the relevant sync run.

Values or fields are incomplete

Review source mapping only after Steps 2 through 4 have been safely verified. Do not change a production connection while investigating.

Related articles

• Initial organisation setup
• Creating a Metric Definition
• Creating a commission scheme
• Perslace overview

Last updated: August 2026