Skip to main content

Connect Tanda

Import your workers and their job history from Tanda, the workforce management and time-and-attendance platform. You authorise Oho to read from Tanda once, and Oho creates your workers and keeps them in step with Tanda on the schedule you choose — so people don't have to be added in two places.

Tanda is in Beta

This connector is still being rolled out. It imports workers and their job history, along with worker status and the organisation details Tanda holds such as location and role. If you hit something unexpected, contact support@weareoho.com.

What you'll end up with

Your Tanda people in Oho as workers — each ready for credentials to be added and checked — kept in step with Tanda, without maintaining two lists.

Before you start​

You'll need:

  • Your people already recorded in Tanda, with the details you want in Oho — their names, contact details, and job history.
  • A Tanda admin account, or someone who has one, to register an app and authorise the connection in Step 1. This is done inside Tanda, not in Oho.

Step 1: Get your auth details​

What you'll need for this step

An admin login to Tanda, and the callback URL Oho shows you on the connection screen. The app is registered inside Tanda, not in Oho — if you don't administer it yourself, loop in whoever does before you start.

Tanda uses the Authorise with OAuth pattern: rather than generating a single key, you register Oho as an application in Tanda and then grant it access. Before you authorise, Tanda needs to know where to send you back — so you register Oho's callback URL against the app first.

  1. In Tanda, open the API / developer area and create a new application.
  2. Register Oho's callback URL (redirect URI) against the app — Oho shows you the exact URL to paste on the connection screen in Step 2.
  3. Copy the app's Client ID and Client Secret.
  4. Make sure the app is allowed to read staff and their job history.
Technical detail: the OAuth exchange, scopes & callback

Hand these points to whoever administers Tanda — a non-technical admin can skip them.

  • Consent flow. Oho uses the OAuth authorization_code grant. Clicking Connect redirects the admin's browser to Tanda's consent screen; approving it returns an authorisation code to Oho, which Oho exchanges for an access token and a refresh token server-to-server. Oho refreshes its own access, so the admin never manages a token by hand.
  • Callback / redirect URI. The redirect URI registered on the Tanda app must exactly match the callback URL Oho presents on the connection screen, or the consent is rejected with a redirect-mismatch error.
  • Scopes. Grant the app read access to staff and job history. [Eng to confirm the exact Tanda OAuth scope names Oho requests.]
  • Where secrets live. Oho stores the Client Secret and refresh token encrypted, referenced by a stored secret ref; the browser never handles them.
Treat the Client Secret like a password

The Client Secret and the resulting tokens grant ongoing access to worker PII for as long as they're valid. Never post them in email, chat, or a ticket, and revoke the app in Tanda if the connection is removed or someone with access to the secret leaves.

Expected outcome: Oho's callback URL is registered on the Tanda app, and you have the Client ID and Client Secret copied, ready to paste into Oho.

Step 2: Connect it in Oho​

In the left menu under Admin, click Integrations, then start a new integration.

The Integrations page in Oho

Pick Tanda from the list of sources.

Choosing a source in Oho

Paste your Client ID and Client Secret, then click Connect. Oho sends you to Tanda's sign-in page — sign in and approve the access Oho asks for. You're returned to Oho and the connection shows as authorised.

Expected outcome: the Tanda connection shows as authorised in Oho, and it moves you on to field mapping.

Step 3: Map your fields​

Oho creates one worker per Tanda staff member. It recognises a returning worker by their Tanda staff ID, carried on source.externalId — so a re-sync updates the existing worker in place rather than creating a duplicate.

Tanda has its own names for things such as status, location, and role; the setup screen asks you to line each one up with its Oho value before your first sync. For what each field expects, which are required, and how re-syncs avoid duplicates, see the shared Map your fields reference, and the Tanda integration reference for what this connector imports at a glance.

Map every value, or those records won't land where you expect

A Tanda value you leave unmapped still imports, but Oho can't place it correctly until it's mapped. If a new value appears in Tanda later, Oho flags it so you can map it.

Expected outcome: every Tanda value the setup screen lists maps to its Oho equivalent, and each worker carries their Tanda staff ID as the match key.

Step 4: Set the schedule​

Choose how often the sync runs, then name it and save.

  • Once — a one-off load to get started. You can revoke Oho's access in Tanda afterwards if you don't intend to sync again.
  • Recurring — Oho re-reads Tanda on a schedule, so new starters, role changes, and terminations flow through automatically. The authorisation from Step 1 must stay in place for future runs — leave it authorised and Oho refreshes its own access.

Setting the sync schedule

Expected outcome: the connection is saved and scheduled, and appears in your Integrations list.

Step 5: Run & verify your first sync​

Run it now with Save & Run, or wait for the first scheduled run. Once it's run, confirm your people are in: they appear under All Workers, and each credential you later add is checked against its official source (see One-off verification).

The new connection in your Integrations list

If the run didn't bring everyone in, check the run history and the Common questions below.

Expected outcome: your people are in Oho under All Workers, ready for credentials to be added and checked.

What happens next​

  • Your people appear under All Workers, ready for checks.
  • To keep those checks current, add a verification source for the credential types you hold — synced credentials then verify at the register automatically.
  • If recurring, you don't re-import by hand — change it in Tanda and Oho picks it up on the next run.

Common questions​

The sync found nothing. Check the connection still shows as authorised — the most common cause is that Oho's access was revoked in Tanda, or the app lost read access to staff. Re-authorise from the integration's settings to fix it.

Consent failed with a redirect error. The redirect URI registered on the Tanda app must exactly match the callback URL Oho shows on the connection screen. Re-copy it from Oho into the Tanda app and try again.

Some workers didn't import. Oho matches returning workers on their Tanda staff ID (source.externalId). Check the match key and the values you mapped in Step 3.

I don't see Integrations. This is an admin area — if it's not in your menu, ask an admin in your organisation, or contact support@weareoho.com.