Connect Adrapid to Detrack

When something happens in Adrapid, Notis takes the next step in Detrack. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Adrapid to Detrack

View example

Turn Adrapid campaign updates into Detrack delivery edits

When an Adrapid webhook includes revised creative campaign delivery details, update the matching Detrack jobs after confirmation.

View example

Review Detrack jobs from an Adrapid campaign brief

Use an Adrapid webhook containing campaign logistics context to retrieve relevant Detrack jobs for review.

View example

Search Detrack deliveries from Adrapid output

Search Detrack for deliveries, collections, or vehicles using criteria included in an Adrapid webhook payload.

View example

Filter Detrack jobs with Adrapid campaign data

Use Adrapid webhook fields to run a paginated Detrack API v2 job listing with supported filters.

View example

Run an advanced Detrack search for Adrapid campaigns

Use an Adrapid webhook to search Detrack across supported date, status, group, vehicle, zone, or DO filters.

View example

Fetch proof of delivery for Adrapid campaign jobs

Retrieve detailed Detrack job status and proof of delivery when an Adrapid webhook supplies exact DO and date identifiers.

View example

Look up a Detrack job from an Adrapid DO number

Retrieve one Detrack job by query when Adrapid supplies the exact DO number and any required query parameters.

View example

Build a Detrack delivery snapshot from Adrapid dispatch data

Use an Adrapid webhook containing a specific date to retrieve every Detrack delivery scheduled for that date.

View example

Review collections linked to an Adrapid campaign on a schedule

On a schedule, inspect collection jobs whose campaign context is supplied in the run instruction or latest Adrapid export.

Supported Triggers and Actions

Notis builds workflows that link Adrapid to Detrack. A trigger fires from one place; an action lands in another.

Adrapid triggers

Detrack actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add Collection

Add a pickup job.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Delete All Collections

Delete all collection jobs for a specific date.

ActionInstant

Bulk Create Depots

Creates multiple depots, each with a name and geocodable address.

ActionInstant

Delete All Deliveries

Delete all delivery jobs for a specific date.

ActionInstant

Create Depot

Creates a depot as a starting or ending point for delivery routes.

ActionInstant

Delete Delivery

Delete one or more delivery jobs.

ActionInstant

Edit Delivery

Update details of existing delivery jobs.

ActionInstant

Search

Find deliveries, collections, or vehicles matching your search.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.