Skip to main content
GiniLytics IT Solutions logo—Matrix

Integrations

What Matrix connects to

Matrix connects to the infrastructure you already run — your mail server, your object storage, your attendance devices and your document library — so it fits into your estate instead of asking you to move to someone else's.

The connections

Each one does something specific for your team, listed alongside it.

Your SMTP server

Email

Every email Matrix sends goes through an SMTP server you configure, with templates you can edit and a log of every attempt.

Mail arrives from your own domain. Point Matrix at your SMTP host, port, credentials and from-address, and every notification reaches your people looking like it came from you — because it did.

The templates are editable in Settings, including the branding, so an invitation or a leave approval reads like it came from your company. Every send attempt — successful or not — is recorded in the Email Logs report.

Used for

  • User invitations and project invitations
  • Password reset links
  • Issue change notifications and @mention alerts
  • Daily digest of issues assigned to a person
  • Daily Status Report summaries
  • Leave application, approval, rejection and cancellation

S3-compatible object storage

Storage

Uploaded files are stored in AWS S3 or any S3-compatible endpoint you run yourself, as tenant-owned objects.

Bucket, region, credentials and endpoint are configuration, so the same product runs against AWS S3 or a self-hosted S3-compatible service without a code change.

Each file is a record owned by your company. Download and delete both confirm the caller belongs to it, so a document stays reachable only by the people you have given access to.

Used for

  • Company logo and profile pictures
  • Employee and HR documents
  • Applicant CVs and team resumes
  • Project and portfolio resources
  • Attendance spreadsheets
  • Attachments on comments and CRM records

Attendance machine exports

Devices

Upload the spreadsheet your attendance device produces and Matrix reads it — no template to fill in, no retyping.

Both legacy .xls and modern .xlsx workbooks are supported, and the importer works out which one it really is rather than trusting the file extension, because attendance-machine exports are notoriously unreliable about that.

It locates the attendance date and the header row, then reads every row beneath it whose employee-code column parses as a number, capturing in time, out time, work duration and total duration.

Used for

  • Bulk attendance import
  • Attendance corrections and reporting

Anthropic Claude

AIConfigurable per deployment

Powers the open-ended answers in Gini Assistant, so your team can ask questions in their own words.

Direct lookups and aggregations — your projects, your overdue tasks, counts and group-bys — are answered straight from your own database, so the questions asked most often never leave your workspace.

Open-ended questions such as compare, summarise and prioritise are handled by the model, inside the asker's own permissions and with every action recorded.

Used for

  • Open-ended questions in Gini Assistant

REST API with OpenAPI documentation

Developer

The product's own HTTP API, documented with Swagger, behind the same authentication and permission checks as the interface.

Anything the application does, it does by calling this API. It is documented with an OpenAPI specification, and every endpoint sits behind the same session, company scoping and named-permission checks as the screens.

That makes it a genuine extension point rather than a limited export: whatever your team can do in the interface, a script of yours can do too, with exactly the access of the account it runs as.

Used for

  • Custom reporting
  • Scripted administration
  • Internal integrations you build

Extending Matrix

Build on the same API the product runs on

Everything you see in Matrix is the documented HTTP API in action, and it is open to your own team.

Every board move, every report and every leave approval is a call to this API. It is documented with an OpenAPI specification, and every endpoint sits behind the same session, the same company scoping and the same named permission checks as the screens.

So a script your team writes gets exactly the access of the account it runs as, and the audit trail records what it did the same way it records a person. Custom reporting, scheduled administration and internal tooling all build on the same foundation the product itself is built on.

The access model that governs it is described on roles and permissions, and the surrounding controls on the security page.

Questions about integrations

How do people get their accounts?
An administrator invites them by email and they set their own password from the link. Adding someone to Matrix takes one action, and their access is decided by the role you give them.
Can we use our own S3-compatible storage instead of AWS?
Yes. The bucket, region, credentials and endpoint URL are all configuration, so Matrix runs against AWS S3 or a self-hosted S3-compatible service without a code change.
Do emails come from Matrix or from us?
From you. Matrix sends all product email through an SMTP server you configure, using templates you can edit — including the branding — and records every send attempt in the Email Logs report.
Is there an API we can build against?
Yes. The product's own HTTP API is documented with an OpenAPI specification and is the same API the application uses, behind the same session, tenant scoping and permission checks.

Tell us what you want to connect

Describe the system and how your team would use it, and we will walk you through the best way to wire it up with the API.

Create your workspaceAsk about an integration

Already using Matrix? Log in, or compare the plans.