Truckstop integration: carrier vetting right on the contact card

Carrier data from the vetting service flows into the accounting system: invitation, attachment and expanded details update the contact card.

Context

The freight accounting system works with Truckstop directly.

What was built

Inviting a carrier to the vetting service from the system.

Attaching the carrier and pulling expanded details onto the contact card.

Change sync every 10 minutes; this workflow is currently switched off.

How it works

The integration is a set of YAML workflows in the accounting system, not code in its core, so a change ships without a system release.

Scale: 4 workflows.

What it looks like

A carrier card, the Truckstop tab: the carrier profile is pulled from the vetting service with Fetch Carrier. The screen is rebuilt from the app configuration, sample data

Truckstop integration workflows in the system editor: names, descriptions and status are real, the date is the last change in the repository history

Other case studies

Case studies and personal projects

An international parcel shipping website: a manager assembles any page without a developerThirty-four ready blocks and more than thirty country pages. A manager assembles any page from them and no developer is needed.A package forwarding website: a catalogue of a thousand products and a store directoryMore than a thousand products, categories, a store directory and a button that copies the American address — on the website for forwarding purchases from American stores.A corporate website: forty-four blocks, ten form scenarios and news from LinkedInForty-four ready blocks, ten form scenarios, and company posts from LinkedIn arrive in the news on their own. A manager assembles any page without a developer.