Connect Trigon to Uku

Company Admin or Company Owner role on a Team or Elite Uku subscription. You also need access to your Trigon account API settings — typically an administrator account.

Trigon is the right integration for accounting firms in Estonia that manage payment files and transaction data for clients with Trigon Bank.

To connect Trigon to Uku you first need an ID token and API key issued by Trigon. Both are generated inside Trigon, not in Uku.

1. Sign in to Trigon with an administrator account.
2. Navigate to the API access section in your Trigon settings.
3. Generate or retrieve the two values you will need:
   • ID token (sometimes labelled identity token) — identifies the connecting account.
   • API key — the secret used to authenticate API calls.
4. Copy both values to a safe place.

Path: Settings & Apps → Trigon

The Trigon integration must be enabled at the company level before it can be used per client. Enabling does not yet pull data; it just makes the integration available.

1. Open Settings & Apps in Uku.
2. Find the Trigon card in the Integrations section.
3. Click the card to open the integration dialog.
4. On the Overview tab, click Enable to turn the integration on. Trigon now appears as an option in the Integration column of your client list.

After enabling Trigon, paste the ID token and API key into the integration dialog and pick the matching environment.

1. In the integration dialog, switch to the Connect (or Settings) tab.
2. Paste the ID token into the matching field.
3. Paste the API key into the matching field.
4. Choose the environment — production for live use, test/sandbox if you are connecting a Trigon test account.
5. Click Test connection. Trigon responds with account details if the credentials are valid.
6. Click Save.

If the test connection fails, see Troubleshooting below.

Trigon is one-way inbound — Uku reads data from Trigon. No data is written back to Trigon.

Data	Direction	Notes
Clients	Trigon → Uku	Imported into the Integration column of the client list.
Contacts	Trigon → Uku	Contact details associated with each client.
Addresses	Trigon → Uku	Mapped into Uku client address fields.
Transaction volumes	Trigon → Uku	Drives the monthly summary task fields (number and volume of transactions per period).

Once Trigon is connected, open the Settings tab in the integration dialog to configure how Uku creates monthly summary tasks for each connected client.

Setting	What it does
Task title	Name used for the auto-generated summary task each month.
Topic	Which topic the summary task is filed under.
Recurrence	Always monthly.
Import data	When in the month data is imported — last work day, last calendar day, or a specific day of the following month (1st–28th).

In the Configure data fields section, map each Trigon data field to a custom task field in Uku. Trigon exposes transaction-level statistics:

• Number of transactions in the period
• Transaction volumes by category
• New clients added in the period

For each field you want to track:

1. Pick the field in the left column.
2. Select the matching Uku custom task field from the dropdown on the right.
3. Fields left blank are not imported.
4. Click Show more to reveal additional less-common fields.
5. Use New custom field inside the dropdown to create a custom field on the spot if one does not yet exist.
6. Click Save when done.

Enabling the Trigon integration only registers it at the company level. Data flows once each Uku client is also linked to its matching Trigon client record. The full per-client connection workflow is covered in Connect a client to accounting software. The short version:

1. In the client list, click the Integration column on the client row.
2. Pick Trigon from the integration dropdown.
3. Uku reads the Trigon client list using your saved credentials and lets you pick the matching client.
4. Save. From the next scheduled import day onwards, Uku pulls data for that client.

To back-fill historical months immediately after connecting, use Reload data on the integration Settings tab.

Trigon caches transaction volumes per period for performance. If a client looks like it is missing entries, or you have changed mapping or settings, run Reload data:

1. Open Settings & Apps → Trigon → Settings.
2. Click Reload data at the bottom-left of the dialog.
3. Confirm. Uku re-imports the last 12 months and overwrites existing summary task field values, then notifies you when ready.

Reload data is the right action whenever you change the data field mapping, recover from a connection that was offline, or notice that the cached transaction volumes look out of date.

Test connection failures with Trigon are almost always one of these:

• The wrong environment (production vs. test/sandbox) is selected — test credentials will not work against production and vice versa.
• The ID token or API key has leading or trailing whitespace. Re-copy directly from Trigon.
• The token has expired. Trigon tokens have an expiration date; regenerate in Trigon and paste the new value.
• The credentials were revoked by a Trigon administrator.

If the Trigon connection passes the test but no statistics show up in summary tasks, enabling the integration is not enough on its own. You also need to:

• Connect each client to its Trigon record — set the Integration column to Trigon on the client row.
• Configure summary task settings on the integration Settings tab (task title, topic, import day, data field mapping).
• Wait for the next scheduled import day, or trigger Reload data to back-fill the last 12 months.

Trigon transaction volumes are cached in Uku for performance. If volumes look stale, run Reload data in the integration Settings tab to refresh the cache from Trigon for all connected clients.

A Trigon connection that was working but stopped is usually a token issue. Trigon tokens have an expiration date. Regenerate the ID token and API key in Trigon, paste the new values into Uku, and click Test connection to confirm. If errors persist, confirm the environment selector matches the credentials.

If a Trigon field consistently arrives empty in Uku summary tasks, it is most likely not mapped to a Uku custom task field. Open the integration Settings tab, find the field in Configure data fields, assign a custom field, then click Reload data to back-fill existing months.