Building integrations

This section documents how SalesDash integrations work end-to-end: how data is fetched from external systems, how it's translated into SalesDash records, and how to build, configure, and debug that pipeline yourself.

It's written for anyone building or modifying a processor — whether you're authoring one from scratch or just adjusting a single setting on one that already exists. It's the most technical section of the docs, but you don't have to read all of it to make a small change. Use the section overview below to find the page you need.

Read Providers → General Principles first if you haven't — the concepts on that page apply to every integration and are not repeated here.

How SalesDash integrations are built

Most providers — and all new ones going forward — use a flexible architecture where sources fetch records and processors translate them into SalesDash data. This is the architecture every page in this section describes.

A handful of older providers (Aircall, Teamleader, Voys, Reuzenpanda) predate this architecture and work differently. Their setup is documented on their individual pages in the Providers section and is not covered here.

Within the modern architecture, the same pieces cover everything from a fully custom integration written from scratch to provider presets that ship with sensible defaults you can use as-is or adjust. The unit of logic is always a processor: a small program that takes one record from a source system and decides what to do with it — what to upsert, what to skip, which fields to map where.

Processors are configured visually in the Spec Builder, an interface modelled on no-code function-stack builders like Xano and Make. You don't write code; you compose instructions.

Section overview

Start with Getting started — it walks through building your first integration end to end. Everything below it is reference material you'll consult as you go.

Page	Read when
Getting started	Start here — walks through building your first integration end to end
Architecture	For context on the data flow and the vocabulary used everywhere else
The Spec Builder	For a tour of the UI you'll be working in
Variables and types	Reference — variable scope, types, and personal-data protection
Operations	Reference — what each instruction does
Expressions	Reference — what each expression does
Blocks	Reference — if_else and for_each
Trace viewer	When debugging a processor execution

The pages assume you have already read the public Core Concepts section.