Check your BigMailer connection when you need it
When you need a quick connection check, start this webhook workflow and see the authenticated BigMailer user information in the report.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Connection issues can interrupt campaign work, and it is hard to know whether the account connection still works without checking it.
- Run a BigMailer authentication check when needed.
- Return user information from the authenticated account.
- Keep connection checks in a repeatable workflow.
Setup
Build it in a few focused steps.
- 1Connect BigMailer once in the Notis portal.
- 2Create an automation and give it a clear name.
- 3Tell Notis to retrieve the authenticated BigMailer user's information and include the result in the run report.
- 4Pick a webhook trigger and choose where run reports go.
- 5Test with one real webhook request.
Questions about this workflow
What information does the action retrieve?
It calls BigMailer's authenticated user endpoint and returns the user information provided by BigMailer.
Does the workflow change campaigns or contacts?
No. This action retrieves user information and does not create or update campaigns or contacts.
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.