Based in Groningen · Working internationally

Tinsights, websites, software en apps
Discuss a project

Integrations

Let systems work together instead of entering the same information twice.

If the same customer, invoice or order lives in three programmes, it needs a connection. It does not need another person in admin.

Tinsights connects websites, software and external platforms through APIs, webhooks and focused automation. We first settle which data is the source, and what is allowed to fail.

We translate the jargon into the work: an API is an agreed way for two programmes to exchange data. A webhook is a signal: ‘something happened, process it.’

What we do

Connect, sync, less retyping.

  • APIsConnect existing services or build an API for your own software.
  • CRM and accountingLeads, customers or invoices that do not need to be moved by hand.
  • PaymentsPayment status back to order, administration or mail.
  • WebhooksPass events on at the moment they happen.
  • Data syncWhich system leads, and how conflicts are handled.
  • WorkflowsA request that automatically opens a task, mail or file.

From practice

Recognised work, not abstract ‘integrations’.

  • Website to CRM

    A form creates a record, instead of a loose email.

  • Shop to administration

    Orders arrive as bookings, without export-import.

  • Planning to a message

    A status change mails or messages the right person.

  • Two systems, one customer view

    Support and sales look at the same data.

How we work

The source first, then the pipes.

  1. Map itWhich systems, which fields, who wins when they conflict.
  2. Name the failuresWhat if the API is down, or a record is missing.
  3. Build and logThe connection plus insight when something does not arrive.
  4. CareTokens, versions and changes on the vendor side.

Engineering

Without unnecessary jargon.

  • REST and webhooksThe most common way for systems to talk.
  • AuthenticationKeys and permissions, so not everything is open.
  • QueuesPeaks or outages do not drop work immediately.
  • LoggingFind out why a record did not come through.

Related work

All projects

Connections live in the systems behind the site, not in a public screenshot. We would rather walk through your current tools.

Questions

Can you connect Exact, Salesforce or another package?

If the package has an API or export, usually yes. We first look at documentation, permissions and whether the vendor needs to be involved.

Is Zapier not enough?

Sometimes, for simple hand-offs. If permissions, error handling or volume come into it, the connection belongs in real software.

What if a vendor changes the API?

That is a reason to agree management. We watch failing jobs and adjust the connection when the other side changes.

Which two systems should talk?

Name the tools and what you retype now. From that it follows whether a connection is worth it.