Flag delivery exceptions
When a shipment status changes to exception in Terminal49, create a task in Asana.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Terminal49 Explore Terminal49 →
TriggersFires when a new order or shipment is created in Terminal49.
Fires when a shipment is picked up, in transit or delivered in Terminal49.
Fires when a shipping label is created in Terminal49.
Creates a shipping or delivery order in Terminal49.
Creates a shipment and books the carrier in Terminal49.
Looks up the tracking status of a shipment in Terminal49.
Asana Explore Asana →
TriggersFires when a new task, job or item is created in Asana.
Fires when a task in Asana is marked complete.
Fires when a task's due date in Asana is coming up.
Fires when a task, job or project changes status in Asana.
Creates a new task, job or item in Asana.
Updates a task's status or assignee in Asana.
Posts a comment on a task in Asana.
Assigns a task in Asana to a team member.
More Terminal49 + Asana workflows
See all Terminal49 + Asana integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Flag delivery exceptions” between Terminal49 and Asana?
Yes — describe it in the box above and Knit's Integrations Agent researches Terminal49 and Asana's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Can shipments create tasks?
Yes. When a shipment status changes in Terminal49, Asana can create or update a task.
Can a task create a shipment?
When a task is completed in Asana, Terminal49 can create the shipment.