Create Detrack collections from Jira requests
When a collection request lands in Jira, Notis can use its details to add the collection in Detrack.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
Add Collection
Tool to add a new collection in detrack. use after gathering all necessary collection details.
Why this helps
Collection requests often need to be copied across apps, and missing details can delay scheduling.
- Reduce retyping between Jira and Detrack.
- Use the request already captured in the Jira issue.
- Surface incomplete requests in the run report for follow-up.
Setup
Build it in a few focused steps.
- 1Connect Jira and Detrack once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Describe in one instruction how to add a Detrack collection from the issue when all necessary details are present, and report missing details.
- 4Pick Jira New Issue as the trigger and choose where run reports go.
- 5Test with one real issue containing complete collection details.
Questions about this workflow
What if the Jira issue is missing collection information?
Tell Notis in the instruction to report which details are missing instead of adding an incomplete collection.
Does the workflow create a delivery?
No. The available action adds a collection in Detrack.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Detrack. A trigger fires from one place; an action lands in another.
Jira triggers
Detrack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Collection
Tool to add a new collection in detrack. use after gathering all necessary collection details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete All Collections
Tool to delete all collections in the account. use when you need to purge every collection for a specific date after confirmation.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Delete All Deliveries
Tool to delete all deliveries for a specific date. use when you need to purge deliveries in bulk before scheduling new ones.
New Project
Triggered when a new project is added in Jira
Delete Delivery
Tool to delete one or more deliveries by date and d.o. number. use after confirming delivery entries to avoid accidental data loss (max 100 items per call).
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Edit Delivery
Tool to edit specific deliveries by date and d.o. number. use after confirming delivery identifiers to update their details (max 100 per call).
List Jobs
Tool to list all jobs with optional filters and pagination. use when you need to retrieve jobs by date, status, country, or other criteria.
Search
Tool to search for deliveries, collections, or vehicles. use after defining search criteria to retrieve matching jobs.
View All Collections
Tool to view all collection jobs in detrack. use when you need to retrieve every collection job currently stored.
Connect any two apps with Notis in the middle.
Jira 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.