Connect Gmail to Bigmailer

When something happens in Gmail, Notis takes the next step in Bigmailer. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Gmail to Bigmailer

View example

Send an instant Bigmailer follow-up for inbound leads

Turn an incoming Gmail lead inquiry into a Bigmailer transactional campaign for a timely reply.

View example

Check Bigmailer brands when important email arrives

Use a new Gmail message to request the current Bigmailer brand list for review alongside the incoming request.

View example

Create a Bigmailer campaign record after a key email

After a Gmail message is sent, create a Bigmailer transactional campaign record based on the message context.

View example

Refresh Bigmailer brand context after campaign emails

After a campaign-related Gmail message is sent, fetch the Bigmailer brand list for a quick report.

View example

Check Bigmailer account access on a schedule

Run a scheduled Bigmailer user information lookup and route the result to a Notis report channel.

View example

Look up Bigmailer brands from an incoming request

Start from an HTTP request and return the Bigmailer brand list through Notis run reports.

Supported Triggers and Actions

Notis builds workflows that link Gmail to Bigmailer. A trigger fires from one place; an action lands in another.

Gmail triggers

Bigmailer actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

Email Sent

Triggers when a Gmail message is sent by the authenticated user. It polls the 'SENT' label and emits metadata including sender, recipients, subject, timestamp, and thread ID.

TriggerPolling

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.

ActionInstant

New Gmail Message Received Trigger

Triggers when a new message is received in Gmail.

TriggerPolling

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.