Skip to main content
The Tripletex integration syncs customers, products, invoices, payments, and supplier invoices with Pike, and sends invoices and customers from Pike to Tripletex. Projects live in Pike; Tripletex keeps the books.

Connect Tripletex

  1. Go to Workspace settings → Integrations → Tripletex.
  2. Click Add integration.
  3. Enter a Tripletex employee token and consumer token.
Only workspace admins can connect or disconnect Tripletex.

Import data

On the integration page, click Import data. The stepper runs entities in dependency order, so customers import before the invoices that reference them. It skips entities whose Read toggle is off, names them, and links to sync settings.

What syncs

Projects

Tripletex projects are not used: projects live in Pike.

Source of truth

Once a record is linked, Tripletex owns the linked fields and Pike reads them back. Pike-only fields, such as project links, internal notes, allocations, and cost profiles, stay in Pike and are never overwritten.

Schedule

Pike syncs with Tripletex every 24 hours by default. Change the schedule in the integration settings. Import data and Refresh always run on demand.

Sync settings

While Tripletex is connected, the What syncs with Tripletex card sits under the top button row on the integration page. Each entity has a Read toggle (Tripletex to Pike) and, where supported, a Send toggle (Pike to Tripletex) and a Send when option. Toggles save immediately. Admins and finance users can change these settings. New connections start with Read on for everything and Send on for invoices only.

Send when

Send when applies to customers only and needs Send on.
  • When you send it: you send each customer yourself.
  • With its first invoice: sending an invoice for an unlinked customer creates the customer in Tripletex first.

Invoices and payments

Invoices reach Tripletex only when someone sends them. Emailing an invoice from Pike does not send it to Tripletex. After an invoice is sent, make changes in Tripletex. Payments update Pike in real time where the accounting system offers webhooks, and on each scheduled sync where it does not.

Synced records

Every synced record shows the Tripletex marker, “Last synced ” or “Not synced yet”, and a Refresh action. Refresh shows only while Read is on for that entity.

Sync issues

Records that fail to sync appear in the Sync issues list on the integration page, with the record, the reason, and a Retry action. The integration never deletes Pike data on its own. A record removed in Tripletex is marked “Removed in Tripletex” in Pike, never deleted.

Disconnect

Disconnecting Tripletex stops syncing and keeps all imported data. Linked records keep their history.

Permissions

Synced data respects Pike roles and private projects. A private project’s tasks never sync out to anyone who cannot see the project in Pike.

Limits

  • Tripletex projects are not used.
  • Pike cannot create products in Tripletex.
  • After an invoice is sent to Tripletex, make changes in Tripletex.