Integration catalogue overview

Perslace provides an integration catalogue for communication, productivity, finance, payroll, and automation services.

For: Admins and data or integration owners

Integrations observed in the test environment

• Microsoft Teams
• Slack
• Zoho Books
• Zoho Payroll
• Google Mail
• Google Calendar
• Google Sheets
• Zapier
• Microsoft Outlook

Slack displayed a connected state in the reviewed test organisation. The connection and disconnection flows for the other services were not tested.

Transaction-data sources

The Data Management > Import Data wizard supports:

• CSV and Excel files
• Google Sheets
• Salesforce
• HubSpot
• Zoho CRM
• Microsoft Dynamics
• SharePoint lists
• PostgreSQL and MySQL tables, views, and materialised views
• Custom REST/JSON APIs, including an FXBO-ready template

These sources feed transaction data into Perslace and are configured through the import wizard rather than the general application-integration catalogue.

Before connecting an integration

1. Confirm that the integration is enabled for your Perslace plan, region, and organisation.
2. Nominate an owner for the external account and the data shared with Perslace.
3. Review the requested permissions and choose the least-privileged account that can perform the approved task.
4. Agree how you will test the connection with synthetic or approved test data.
5. Record who approved the connection and how it can be safely revoked.

Expected result

You have an approved connection plan and can identify the external owner, requested access, test method, and rollback route.

Important notes

Confirm organisation-specific access

Connector availability, OAuth scopes, refresh timing, and disconnection effects can vary by organisation and subscription. Review the current on-screen permissions before authorising a live account.

• The public Perslace website may describe a broader catalogue than the applications enabled in your workspace.
• Never place API keys, passwords, access tokens, or connection strings in screenshots or support requests.
• Disconnecting a source may affect future synchronisation. Data-retention and recalculation effects are not yet verified.

Troubleshooting

If a connector is missing, confirm your plan, region, role, and organisation before contacting Support. If a connection fails, record the connector name, time, connection state, and a sanitised error message.

Related articles

• Importing transaction data
• Common data and calculation issues
• Data protection and safe support sharing

Last updated: August 2026