Keep Jira work aligned with Clay account tiers
When an account's tier changes in Clay, update its related Jira work with the new segmentation context.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 changed account tier can alter how work should be handled while the Jira issue still reflects the old segment.
- Keep account work consistent with current segmentation.
- Make tier changes visible where work is managed.
- Reduce manual correction of outdated account context.
Setup
Build it in a few focused steps.
- 1Connect Clay and Jira once in Notis.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to update the related Jira issue when a webhook request reports a changed Clay account tier, including the new tier and relevant context.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real tier change and verify the Jira issue.
Questions about this workflow
Can the automation compare old and new tiers?
Yes, if both values are included in the request or otherwise available. If only the current tier is available, Notis cannot infer the previous value.
What Jira fields should change?
Specify the fields and rules in your instruction, based on what your Jira project supports.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Clay to Jira. A trigger fires from one place; an action lands in another.
Clay 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.
Clay 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.