Connect ActiveTrail to Detrack

When something happens in ActiveTrail, 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 ActiveTrail to Detrack

View example

Create a collection from a campaign response

Turn a campaign response containing collection details into a Detrack collection job.

View example

Review delivery proof for a customer follow-up

Look up a Detrack job and summarize its proof of delivery for a scheduled customer follow-up review.

View example

Find delivery exceptions for a campaign audience

Search Detrack jobs for delivery exceptions and prepare a report against the ActiveTrail audience you specify.

View example

Correct delivery details from a verified request

Use a verified webhook request to update a Detrack delivery after checking its date and DO number.

View example

Prepare a delivery status digest for a campaign audience

Review Detrack job statuses against an ActiveTrail audience and summarize completed, pending, and unclear matches.

View example

Look up a delivery before answering a request

Retrieve a Detrack job by DO number from an incoming request and prepare the details for a customer response.

View example

Reconcile a day's deliveries with campaign context

Review all Detrack deliveries for a specified date and report which ones match the ActiveTrail context you provide.

View example

Retrieve proof for a customer delivery request

Use an incoming webhook request to fetch delivery status and proof details for a specified Detrack job.

View example

Prepare a depot directory for campaign planning

Fetch Detrack depot locations and summarize them alongside the campaign context you specify in ActiveTrail.

Supported Triggers and Actions

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

ActiveTrail 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.