Keep Jira follow-up tickets current with Cardly status
Notis checks delivery status on a schedule and updates the related Jira issue when Cardly has new information, keeping the next action in view.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Edit Issue
Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.
Why this helps
A Jira ticket can go stale while delivery status changes elsewhere, forcing teammates to switch apps to reconstruct the latest context.
- Refresh existing Jira work with delivery information Cardly provides.
- Reduce manual status checks across apps.
- Keep campaign follow-up context close to the team's active work.
Setup
Build it in a few focused steps.
- 1Connect Cardly and Jira once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to check Cardly delivery status and update the related Jira issue when it finds new status information.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real campaign and Jira issue, then review the updated issue.
Questions about this workflow
How does Notis find the Jira issue to update?
Describe the available campaign or customer identifiers in your instruction. If Cardly does not return a reliable identifier that matches a Jira issue, supply one in the workflow context.
What happens when Cardly has no new status?
The instruction can tell Notis to leave the Jira issue unchanged when the checked status has not changed.
Does this run each time Cardly changes a delivery status?
No. It runs on the recurring schedule you choose because Cardly trigger events are not available here.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cardly to Jira. A trigger fires from one place; an action lands in another.
Cardly triggers
Jira actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Attachment
Uploads and attaches a file to a jira issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Link Issues
Links two jira issues using a specified link type with optional comment.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Cardly and Jira, 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 Jira.