Keep Jira campaign briefs aligned with incoming changes
When campaign details change, send an HTTP request to Notis and have it update the matching Jira brief so the team works from current information.
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 revised campaign detail can reach one tool while the Jira brief still reflects an older plan.
- Bring supplied campaign changes into Jira
- Keep the brief useful for delivery teams
- Reduce manual restating of campaign updates
Setup
Build it in a few focused steps.
- 1Connect Benchmark email and Jira once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for campaign brief updates.
- 3Tell Notis to identify the matching Jira brief from each incoming request and update it with the supplied changed details.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test by sending one real campaign change request to the webhook.
Questions about this workflow
Does Benchmark email send the webhook automatically?
No. The webhook starts when an HTTP request is sent to Notis. Include the change details or ensure they are available for Notis to retrieve.
What if there is no matching Jira brief?
This action updates an existing issue. Specify how to identify it; unmatched cases may need a separate issue creation workflow.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Benchmark email to Jira. A trigger fires from one place; an action lands in another.
Benchmark email 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.
Benchmark email 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.