Check delivery proof when a sensor records a handoff
When a connected device signals a handoff, bring the delivery status and available proof of delivery into the run report.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Job by DO and Date
Retrieves a delivery or collection job by its order number and date.
Why this helps
After a handoff signal, confirming the delivery record and finding its proof can require switching between tools and searching manually.
- Retrieve a specific Detrack job using its delivery order number and date.
- Bring available status, tracking, and proof details into the run report.
- Keep sensor handoff signals connected to the delivery record they concern.
Setup
Build it in a few focused steps.
- 1Connect Adafruit IO and Detrack once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for the handoff check.
- 3Tell Notis to retrieve the Detrack job using the delivery order number and date in the webhook, then report the status and any available proof of delivery information.
- 4Choose the webhook trigger and configure your existing bridge to send handoff signals with the required identifiers.
- 5Choose a report channel and test with one real handoff signal and its matching Detrack job.
Questions about this workflow
Which details are needed to retrieve a job?
Include the Detrack delivery order number and date in the webhook payload.
Does the sensor signal prove the delivery was completed?
No. The workflow retrieves Detrack's job record and reports the available status and proof details. The sensor signal itself is not proof of delivery.
What happens if Detrack has no proof attached?
The report can show the job details returned by Detrack. It cannot create proof that is not present in the job record.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Adafruit IO to Detrack. A trigger fires from one place; an action lands in another.
Adafruit IO triggers
Detrack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Collection
Add a pickup job.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete All Collections
Delete all collection jobs for a specific date.
Bulk Create Depots
Creates multiple depots, each with a name and geocodable address.
Delete All Deliveries
Delete all delivery jobs for a specific date.
Create Depot
Creates a depot as a starting or ending point for delivery routes.
Delete Delivery
Delete one or more delivery jobs.
Edit Delivery
Update details of existing delivery jobs.
Search
Find deliveries, collections, or vehicles matching your search.
Connect any two apps with Notis in the middle.
Adafruit IO and Detrack, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Detrack.