See available BigMailer brands when a Jira project starts
A new Jira project means setup work. Include the BigMailer brand list in the run report so the owner can see the available options.
Trigger
New Project
Triggered when a new project is added in Jira
Action
List All Brands
This tool retrieves a list of all brands associated with the authenticated bigmailer account. it allows users to view and manage their brands. the operation is executed via a simple get request to the /brands endpoint and requires proper authentication using the x-api-key header. the response is a json array containing information such as brand id, brand name, and other related details.
Why this helps
Project setup can involve a separate BigMailer check, making it easy to miss which brands are available to the team.
- See available BigMailer brands alongside a new project event.
- Reduce a separate manual lookup during project setup.
- Give the project owner a current reference from the connected account.
Setup
Build it in a few focused steps.
- 1Connect Jira and BigMailer once in the Notis portal.
- 2Create an automation and give it a clear name.
- 3Tell Notis to retrieve the available BigMailer brands when a new Jira project is added and include the results in the run report.
- 4Pick the Jira New Project trigger and choose where run reports go.
- 5Test with one real project event.
Questions about this workflow
Does this automatically choose a brand for the Jira project?
No. The action lists the brands in the connected BigMailer account. A team member can use the report to decide which brand applies.
What starts the lookup?
The workflow starts when a new project is added in Jira.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Bigmailer. A trigger fires from one place; an action lands in another.
Jira triggers
Bigmailer actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Transactional Campaign
This tool creates a new transactional campaign within a specified brand in bigmailer. it allows users to programmatically create new transactional campaigns by using the provided parameters (brandid, name, subject, fromname, fromemail, htmlcontent, etc.). the api endpoint returns details such as campaignid, name, status, and created at when a campaign is successfully created.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get User Information
This tool retrieves information about the authenticated user in bigmailer using the get /me endpoint. it requires only authentication and no additional parameters, making it ideal for verifying api connectivity and retrieving essential user details.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
List All Brands
This tool retrieves a list of all brands associated with the authenticated bigmailer account. it allows users to view and manage their brands. the operation is executed via a simple get request to the /brands endpoint and requires proper authentication using the x-api-key header. the response is a json array containing information such as brand id, brand name, and other related details.
New Project
Triggered when a new project is added in Jira
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.
Connect any two apps with Notis in the middle.
Jira and Bigmailer, 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 Bigmailer.