Skip to content

Integration platform

Relaydesk

An integration desk that sits between scheduling, invoicing, and a technician app — with visible sync health instead of silent failures.

Arcadia Field Services · 2024

app.relaydesk.test

Relaydesk · connectors

3 healthy

Scheduling API

POST /jobs

200

2m ago

Invoicing

GET /invoices

200

6m ago

Technician app

WH /events

429

Retry 1

{
  "event": "job.completed",
  "job_id": "FS-9182",
  "attempt": 1
}

Problem

What was breaking

Arcadia’s tools were connected by a collection of scripts. Appointments duplicated. Invoices went out with yesterday’s hours. When a webhook failed, the first signal was a customer calling.

Solution

What we built

We replaced the scripts with Relaydesk: a small integration application that owns the mappings, retries, and dead letters. Each connected system has a contract. Operators can replay a failed event without engineering sitting on the call.

Outcome

Sync failures are a queue with reasons, not a surprise. The technician app, the scheduler, and billing now share identifiers instead of approximately matching names.

Functionality

What the product does

  • Connector status for each upstream and downstream system
  • Idempotent event processing with replay
  • Payload inspector for failed jobs
  • Mapping of jobs, technicians, and invoices across systems
  • Alerting when a connector goes quiet

Stack

Technologies

  • Laravel
  • Node.js
  • PostgreSQL
  • Redis
  • Docker

Related services

Next step

Have a system that needs to exist?

Tell us about the workflow, the constraint, and the people who will use the software. We will tell you whether a build is the right next step.